From 92d8be885a93dff9c8e9efe0307653c98fd5c682 Mon Sep 17 00:00:00 2001 From: Josh Cannon Date: Mon, 8 Jan 2024 16:50:11 -0600 Subject: [PATCH] Replace instances of `scie-pants-linux-x86_64` with `pants` (#74) Fixes https://github.com/pantsbuild/pantsbuild.org/issues/73 with a find-and-replace of "scie-pants-linux-x86_64" with "pants". Verified only reference directories have been modified (`git diff --stat | grep /docs/`) --- docs/reference/global-options.mdx | 6 +- docs/reference/goals/experimental-bsp.mdx | 2 +- docs/reference/goals/fix.mdx | 2 +- docs/reference/goals/generate-lockfiles.mdx | 4 +- docs/reference/goals/lint.mdx | 4 +- docs/reference/help-all.json | 764 +++++++++--------- .../subsystems/add-trailing-comma.mdx | 2 +- docs/reference/subsystems/autoflake.mdx | 2 +- docs/reference/subsystems/bandit.mdx | 2 +- docs/reference/subsystems/black.mdx | 2 +- docs/reference/subsystems/buf.mdx | 4 +- .../subsystems/build-deprecations-fixer.mdx | 2 +- docs/reference/subsystems/buildifier.mdx | 2 +- docs/reference/subsystems/cli.mdx | 2 +- docs/reference/subsystems/docformatter.mdx | 2 +- docs/reference/subsystems/docker.mdx | 2 +- docs/reference/subsystems/flake8.mdx | 2 +- docs/reference/subsystems/go-test.mdx | 2 +- docs/reference/subsystems/gofmt.mdx | 2 +- .../subsystems/google-java-format.mdx | 4 +- docs/reference/subsystems/hadolint.mdx | 2 +- docs/reference/subsystems/helm-unittest.mdx | 2 +- docs/reference/subsystems/isort.mdx | 2 +- docs/reference/subsystems/jarjar.mdx | 2 +- docs/reference/subsystems/junit.mdx | 4 +- docs/reference/subsystems/ktlint.mdx | 4 +- docs/reference/subsystems/mypy.mdx | 2 +- docs/reference/subsystems/nodejs.mdx | 2 +- docs/reference/subsystems/openapi-format.mdx | 2 +- docs/reference/subsystems/preamble.mdx | 2 +- .../subsystems/protobuf-java-grpc.mdx | 2 +- docs/reference/subsystems/pydocstyle.mdx | 2 +- docs/reference/subsystems/pylint.mdx | 2 +- docs/reference/subsystems/pytest.mdx | 2 +- docs/reference/subsystems/python-infer.mdx | 4 +- docs/reference/subsystems/python.mdx | 8 +- docs/reference/subsystems/pytype.mdx | 2 +- docs/reference/subsystems/pyupgrade.mdx | 2 +- docs/reference/subsystems/regex-lint.mdx | 2 +- docs/reference/subsystems/ruff.mdx | 2 +- docs/reference/subsystems/scalafmt.mdx | 4 +- docs/reference/subsystems/scalapb.mdx | 2 +- docs/reference/subsystems/scalatest.mdx | 4 +- docs/reference/subsystems/semgrep.mdx | 2 +- docs/reference/subsystems/shell-test.mdx | 2 +- docs/reference/subsystems/shellcheck.mdx | 2 +- docs/reference/subsystems/shfmt.mdx | 2 +- docs/reference/subsystems/shunit2.mdx | 2 +- docs/reference/subsystems/spectral.mdx | 2 +- docs/reference/subsystems/terraform-fmt.mdx | 2 +- .../subsystems/terraform-validate.mdx | 2 +- docs/reference/subsystems/twine.mdx | 2 +- docs/reference/subsystems/yamllint.mdx | 2 +- docs/reference/subsystems/yapf.mdx | 2 +- docs/reference/targets/adhoc_tool.mdx | 4 +- docs/reference/targets/archive.mdx | 12 +- docs/reference/targets/code_quality_tool.mdx | 4 +- docs/reference/targets/deploy_jar.mdx | 10 +- docs/reference/targets/docker_environment.mdx | 4 +- docs/reference/targets/docker_image.mdx | 12 +- .../experimental_test_shell_command.mdx | 4 +- ...xperimental_wrap_as_go_package_sources.mdx | 4 +- .../experimental_wrap_as_java_sources.mdx | 4 +- .../experimental_wrap_as_kotlin_sources.mdx | 4 +- .../experimental_wrap_as_python_sources.mdx | 4 +- .../experimental_wrap_as_resources.mdx | 4 +- .../experimental_wrap_as_scala_sources.mdx | 4 +- docs/reference/targets/file.mdx | 8 +- docs/reference/targets/files.mdx | 8 +- docs/reference/targets/go_binary.mdx | 6 +- docs/reference/targets/go_mod.mdx | 4 +- docs/reference/targets/go_package.mdx | 8 +- .../targets/go_third_party_package.mdx | 8 +- docs/reference/targets/helm_artifact.mdx | 4 +- docs/reference/targets/helm_chart.mdx | 14 +- docs/reference/targets/helm_deployment.mdx | 8 +- docs/reference/targets/helm_unittest_test.mdx | 8 +- .../reference/targets/helm_unittest_tests.mdx | 8 +- docs/reference/targets/java_source.mdx | 8 +- docs/reference/targets/java_sources.mdx | 8 +- docs/reference/targets/junit_test.mdx | 8 +- docs/reference/targets/junit_tests.mdx | 8 +- docs/reference/targets/jvm_artifact.mdx | 4 +- docs/reference/targets/jvm_war.mdx | 10 +- docs/reference/targets/kotlin_junit_test.mdx | 8 +- docs/reference/targets/kotlin_junit_tests.mdx | 8 +- docs/reference/targets/kotlin_source.mdx | 8 +- docs/reference/targets/kotlin_sources.mdx | 8 +- docs/reference/targets/kotlinc_plugin.mdx | 4 +- docs/reference/targets/local_environment.mdx | 4 +- docs/reference/targets/openapi_document.mdx | 8 +- docs/reference/targets/openapi_documents.mdx | 8 +- docs/reference/targets/openapi_source.mdx | 8 +- docs/reference/targets/openapi_sources.mdx | 8 +- docs/reference/targets/pants_requirements.mdx | 4 +- docs/reference/targets/pex_binaries.mdx | 8 +- docs/reference/targets/pex_binary.mdx | 10 +- .../reference/targets/pipenv_requirements.mdx | 4 +- .../reference/targets/poetry_requirements.mdx | 4 +- docs/reference/targets/protobuf_source.mdx | 8 +- docs/reference/targets/protobuf_sources.mdx | 8 +- docs/reference/targets/pyoxidizer_binary.mdx | 6 +- .../targets/python_aws_lambda_function.mdx | 10 +- .../targets/python_aws_lambda_layer.mdx | 10 +- .../reference/targets/python_distribution.mdx | 10 +- .../targets/python_google_cloud_function.mdx | 10 +- docs/reference/targets/python_requirement.mdx | 8 +- .../reference/targets/python_requirements.mdx | 4 +- docs/reference/targets/python_source.mdx | 8 +- docs/reference/targets/python_sources.mdx | 8 +- docs/reference/targets/python_test.mdx | 14 +- docs/reference/targets/python_test_utils.mdx | 8 +- docs/reference/targets/python_tests.mdx | 14 +- docs/reference/targets/relocated_files.mdx | 4 +- docs/reference/targets/remote_environment.mdx | 4 +- docs/reference/targets/resource.mdx | 8 +- docs/reference/targets/resources.mdx | 8 +- docs/reference/targets/run_shell_command.mdx | 4 +- docs/reference/targets/scala_artifact.mdx | 4 +- docs/reference/targets/scala_junit_test.mdx | 8 +- docs/reference/targets/scala_junit_tests.mdx | 8 +- docs/reference/targets/scala_source.mdx | 8 +- docs/reference/targets/scala_sources.mdx | 8 +- docs/reference/targets/scalac_plugin.mdx | 4 +- docs/reference/targets/scalatest_test.mdx | 8 +- docs/reference/targets/scalatest_tests.mdx | 8 +- docs/reference/targets/shell_command.mdx | 4 +- docs/reference/targets/shell_source.mdx | 8 +- docs/reference/targets/shell_sources.mdx | 8 +- docs/reference/targets/shunit2_test.mdx | 14 +- docs/reference/targets/shunit2_tests.mdx | 14 +- docs/reference/targets/system_binary.mdx | 4 +- docs/reference/targets/target.mdx | 8 +- .../targets/terraform_deployment.mdx | 8 +- docs/reference/targets/terraform_module.mdx | 8 +- docs/reference/targets/thrift_source.mdx | 8 +- docs/reference/targets/thrift_sources.mdx | 8 +- docs/reference/targets/vcs_version.mdx | 4 +- .../version-2.0/reference/help-all.json | 16 +- .../reference/subsystems/bandit.mdx | 2 +- .../reference/subsystems/black.mdx | 2 +- .../reference/subsystems/docformatter.mdx | 2 +- .../reference/subsystems/flake8.mdx | 2 +- .../reference/subsystems/isort.mdx | 2 +- .../version-2.0/reference/subsystems/mypy.mdx | 2 +- .../reference/subsystems/pylint.mdx | 2 +- .../version-2.1/reference/help-all.json | 16 +- .../reference/subsystems/bandit.mdx | 2 +- .../reference/subsystems/black.mdx | 2 +- .../reference/subsystems/docformatter.mdx | 2 +- .../reference/subsystems/flake8.mdx | 2 +- .../reference/subsystems/isort.mdx | 2 +- .../version-2.1/reference/subsystems/mypy.mdx | 2 +- .../reference/subsystems/pylint.mdx | 2 +- .../version-2.10/reference/help-all.json | 28 +- .../reference/subsystems/autoflake.mdx | 2 +- .../reference/subsystems/bandit.mdx | 2 +- .../reference/subsystems/black.mdx | 2 +- .../reference/subsystems/docformatter.mdx | 2 +- .../reference/subsystems/flake8.mdx | 2 +- .../reference/subsystems/gofmt.mdx | 2 +- .../subsystems/google-java-format.mdx | 2 +- .../reference/subsystems/isort.mdx | 2 +- .../reference/subsystems/mypy.mdx | 2 +- .../reference/subsystems/pylint.mdx | 2 +- .../reference/subsystems/pyupgrade.mdx | 2 +- .../reference/subsystems/scalafmt.mdx | 2 +- .../reference/subsystems/yapf.mdx | 2 +- .../version-2.11/reference/global-options.mdx | 6 +- .../reference/goals/experimental-bsp.mdx | 2 +- .../reference/goals/generate-lockfiles.mdx | 4 +- .../version-2.11/reference/help-all.json | 450 +++++------ .../reference/subsystems/autoflake.mdx | 4 +- .../reference/subsystems/bandit.mdx | 4 +- .../reference/subsystems/black.mdx | 4 +- .../version-2.11/reference/subsystems/buf.mdx | 4 +- .../version-2.11/reference/subsystems/cli.mdx | 2 +- .../reference/subsystems/coverage-py.mdx | 2 +- .../reference/subsystems/docformatter.mdx | 4 +- .../reference/subsystems/docker.mdx | 2 +- .../subsystems/dockerfile-parser.mdx | 2 +- .../reference/subsystems/flake8.mdx | 4 +- .../reference/subsystems/gofmt.mdx | 2 +- .../subsystems/google-java-format.mdx | 4 +- .../reference/subsystems/hadolint.mdx | 2 +- .../reference/subsystems/ipython.mdx | 2 +- .../reference/subsystems/isort.mdx | 4 +- .../reference/subsystems/junit.mdx | 2 +- .../reference/subsystems/lambdex.mdx | 2 +- .../reference/subsystems/mypy-protobuf.mdx | 2 +- .../reference/subsystems/mypy.mdx | 4 +- .../reference/subsystems/pylint.mdx | 4 +- .../reference/subsystems/pytest.mdx | 2 +- .../reference/subsystems/python-infer.mdx | 2 +- .../reference/subsystems/python.mdx | 6 +- .../reference/subsystems/pyupgrade.mdx | 4 +- .../reference/subsystems/scalafmt.mdx | 4 +- .../reference/subsystems/scalapb.mdx | 2 +- .../reference/subsystems/scalatest.mdx | 2 +- .../reference/subsystems/setuptools.mdx | 2 +- .../reference/subsystems/shellcheck.mdx | 2 +- .../reference/subsystems/shfmt.mdx | 2 +- .../reference/subsystems/terraform-fmt.mdx | 2 +- .../subsystems/terraform-hcl2-parser.mdx | 2 +- .../subsystems/terraform-validate.mdx | 2 +- .../reference/subsystems/twine.mdx | 4 +- .../reference/subsystems/yapf.mdx | 4 +- .../reference/targets/archive.mdx | 12 +- .../reference/targets/deploy_jar.mdx | 10 +- .../reference/targets/docker_image.mdx | 10 +- .../experimental_run_shell_command.mdx | 8 +- .../targets/experimental_shell_command.mdx | 8 +- .../version-2.11/reference/targets/file.mdx | 8 +- .../version-2.11/reference/targets/files.mdx | 8 +- .../reference/targets/go_binary.mdx | 6 +- .../version-2.11/reference/targets/go_mod.mdx | 4 +- .../reference/targets/go_package.mdx | 8 +- .../targets/go_third_party_package.mdx | 8 +- .../reference/targets/helm_chart.mdx | 12 +- .../reference/targets/java_source.mdx | 8 +- .../reference/targets/java_sources.mdx | 8 +- .../reference/targets/junit_test.mdx | 8 +- .../reference/targets/junit_tests.mdx | 8 +- .../reference/targets/jvm_artifact.mdx | 4 +- .../reference/targets/jvm_war.mdx | 10 +- .../reference/targets/pants_requirements.mdx | 4 +- .../reference/targets/pex_binaries.mdx | 8 +- .../reference/targets/pex_binary.mdx | 10 +- .../reference/targets/pipenv_requirements.mdx | 4 +- .../reference/targets/poetry_requirements.mdx | 4 +- .../reference/targets/protobuf_source.mdx | 8 +- .../reference/targets/protobuf_sources.mdx | 8 +- .../reference/targets/pyoxidizer_binary.mdx | 6 +- .../reference/targets/python_awslambda.mdx | 10 +- .../reference/targets/python_distribution.mdx | 10 +- .../targets/python_google_cloud_function.mdx | 10 +- .../reference/targets/python_requirement.mdx | 8 +- .../reference/targets/python_requirements.mdx | 4 +- .../reference/targets/python_source.mdx | 8 +- .../reference/targets/python_sources.mdx | 8 +- .../reference/targets/python_test.mdx | 18 +- .../reference/targets/python_test_utils.mdx | 8 +- .../reference/targets/python_tests.mdx | 14 +- .../reference/targets/relocated_files.mdx | 4 +- .../reference/targets/resource.mdx | 8 +- .../reference/targets/resources.mdx | 8 +- .../reference/targets/scala_junit_test.mdx | 8 +- .../reference/targets/scala_junit_tests.mdx | 8 +- .../reference/targets/scala_source.mdx | 8 +- .../reference/targets/scala_sources.mdx | 8 +- .../reference/targets/scalac_plugin.mdx | 4 +- .../reference/targets/scalatest_test.mdx | 8 +- .../reference/targets/scalatest_tests.mdx | 8 +- .../reference/targets/shell_source.mdx | 8 +- .../reference/targets/shell_sources.mdx | 8 +- .../reference/targets/shunit2_test.mdx | 14 +- .../reference/targets/shunit2_tests.mdx | 14 +- .../version-2.11/reference/targets/target.mdx | 8 +- .../reference/targets/terraform_module.mdx | 8 +- .../reference/targets/thrift_source.mdx | 8 +- .../reference/targets/thrift_sources.mdx | 8 +- .../version-2.12/reference/global-options.mdx | 6 +- .../reference/goals/experimental-bsp.mdx | 2 +- .../reference/goals/generate-lockfiles.mdx | 4 +- .../version-2.12/reference/help-all.json | 510 ++++++------ .../reference/subsystems/autoflake.mdx | 6 +- .../reference/subsystems/bandit.mdx | 6 +- .../reference/subsystems/black.mdx | 6 +- .../version-2.12/reference/subsystems/buf.mdx | 4 +- .../version-2.12/reference/subsystems/cli.mdx | 2 +- .../reference/subsystems/coverage-py.mdx | 2 +- .../reference/subsystems/docformatter.mdx | 6 +- .../reference/subsystems/docker.mdx | 2 +- .../subsystems/dockerfile-parser.mdx | 2 +- .../reference/subsystems/flake8.mdx | 6 +- .../reference/subsystems/gofmt.mdx | 2 +- .../subsystems/google-java-format.mdx | 4 +- .../reference/subsystems/hadolint.mdx | 2 +- .../reference/subsystems/ipython.mdx | 2 +- .../reference/subsystems/isort.mdx | 6 +- .../reference/subsystems/junit.mdx | 2 +- .../reference/subsystems/ktlint.mdx | 4 +- .../reference/subsystems/lambdex.mdx | 2 +- .../reference/subsystems/mypy-protobuf.mdx | 2 +- .../reference/subsystems/mypy.mdx | 6 +- .../reference/subsystems/pylint.mdx | 6 +- .../reference/subsystems/pytest.mdx | 4 +- .../reference/subsystems/python-infer.mdx | 2 +- .../reference/subsystems/python.mdx | 6 +- .../reference/subsystems/pyupgrade.mdx | 6 +- .../reference/subsystems/scalafmt.mdx | 4 +- .../reference/subsystems/scalapb.mdx | 2 +- .../reference/subsystems/scalatest.mdx | 2 +- .../reference/subsystems/setuptools.mdx | 2 +- .../reference/subsystems/shellcheck.mdx | 2 +- .../reference/subsystems/shfmt.mdx | 2 +- .../reference/subsystems/terraform-fmt.mdx | 2 +- .../subsystems/terraform-hcl2-parser.mdx | 2 +- .../subsystems/terraform-validate.mdx | 2 +- .../reference/subsystems/twine.mdx | 4 +- .../reference/subsystems/yapf.mdx | 6 +- .../reference/targets/archive.mdx | 12 +- .../reference/targets/deploy_jar.mdx | 10 +- .../reference/targets/docker_image.mdx | 10 +- .../experimental_run_shell_command.mdx | 8 +- .../targets/experimental_shell_command.mdx | 8 +- .../version-2.12/reference/targets/file.mdx | 8 +- .../version-2.12/reference/targets/files.mdx | 8 +- .../reference/targets/go_binary.mdx | 6 +- .../version-2.12/reference/targets/go_mod.mdx | 4 +- .../reference/targets/go_package.mdx | 8 +- .../targets/go_third_party_package.mdx | 8 +- .../reference/targets/helm_artifact.mdx | 4 +- .../reference/targets/helm_chart.mdx | 12 +- .../reference/targets/helm_unittest_test.mdx | 8 +- .../reference/targets/helm_unittest_tests.mdx | 12 +- .../reference/targets/java_source.mdx | 8 +- .../reference/targets/java_sources.mdx | 8 +- .../reference/targets/junit_test.mdx | 8 +- .../reference/targets/junit_tests.mdx | 8 +- .../reference/targets/jvm_artifact.mdx | 4 +- .../reference/targets/jvm_war.mdx | 10 +- .../reference/targets/kotlin_source.mdx | 8 +- .../reference/targets/kotlin_sources.mdx | 8 +- .../reference/targets/kotlinc_plugin.mdx | 4 +- .../reference/targets/pants_requirements.mdx | 4 +- .../reference/targets/pex_binaries.mdx | 8 +- .../reference/targets/pex_binary.mdx | 10 +- .../reference/targets/pipenv_requirements.mdx | 4 +- .../reference/targets/poetry_requirements.mdx | 4 +- .../reference/targets/protobuf_source.mdx | 8 +- .../reference/targets/protobuf_sources.mdx | 8 +- .../reference/targets/pyoxidizer_binary.mdx | 6 +- .../reference/targets/python_awslambda.mdx | 10 +- .../reference/targets/python_distribution.mdx | 10 +- .../targets/python_google_cloud_function.mdx | 10 +- .../reference/targets/python_requirement.mdx | 8 +- .../reference/targets/python_requirements.mdx | 4 +- .../reference/targets/python_source.mdx | 8 +- .../reference/targets/python_sources.mdx | 8 +- .../reference/targets/python_test.mdx | 18 +- .../reference/targets/python_test_utils.mdx | 8 +- .../reference/targets/python_tests.mdx | 14 +- .../reference/targets/relocated_files.mdx | 4 +- .../reference/targets/resource.mdx | 8 +- .../reference/targets/resources.mdx | 8 +- .../reference/targets/scala_junit_test.mdx | 8 +- .../reference/targets/scala_junit_tests.mdx | 8 +- .../reference/targets/scala_source.mdx | 8 +- .../reference/targets/scala_sources.mdx | 8 +- .../reference/targets/scalac_plugin.mdx | 4 +- .../reference/targets/scalatest_test.mdx | 8 +- .../reference/targets/scalatest_tests.mdx | 8 +- .../reference/targets/shell_source.mdx | 8 +- .../reference/targets/shell_sources.mdx | 8 +- .../reference/targets/shunit2_test.mdx | 14 +- .../reference/targets/shunit2_tests.mdx | 14 +- .../version-2.12/reference/targets/target.mdx | 8 +- .../reference/targets/terraform_module.mdx | 8 +- .../reference/targets/thrift_source.mdx | 8 +- .../reference/targets/thrift_sources.mdx | 8 +- .../version-2.13/reference/global-options.mdx | 12 +- .../reference/goals/experimental-bsp.mdx | 2 +- .../reference/goals/generate-lockfiles.mdx | 4 +- .../version-2.13/reference/goals/lint.mdx | 2 +- .../version-2.13/reference/help-all.json | 538 ++++++------ .../reference/subsystems/autoflake.mdx | 6 +- .../reference/subsystems/bandit.mdx | 6 +- .../reference/subsystems/black.mdx | 6 +- .../version-2.13/reference/subsystems/buf.mdx | 4 +- .../version-2.13/reference/subsystems/cli.mdx | 2 +- .../reference/subsystems/coverage-py.mdx | 2 +- .../reference/subsystems/debugpy.mdx | 2 +- .../reference/subsystems/docformatter.mdx | 6 +- .../reference/subsystems/docker.mdx | 2 +- .../subsystems/dockerfile-parser.mdx | 2 +- .../reference/subsystems/flake8.mdx | 6 +- .../reference/subsystems/gofmt.mdx | 2 +- .../subsystems/google-java-format.mdx | 4 +- .../reference/subsystems/hadolint.mdx | 2 +- .../reference/subsystems/ipython.mdx | 2 +- .../reference/subsystems/isort.mdx | 6 +- .../reference/subsystems/junit.mdx | 2 +- .../reference/subsystems/ktlint.mdx | 4 +- .../reference/subsystems/lambdex.mdx | 2 +- .../reference/subsystems/mypy-protobuf.mdx | 2 +- .../reference/subsystems/mypy.mdx | 6 +- .../reference/subsystems/pylint.mdx | 6 +- .../reference/subsystems/pytest.mdx | 4 +- .../reference/subsystems/python-infer.mdx | 4 +- .../reference/subsystems/python.mdx | 6 +- .../reference/subsystems/pyupgrade.mdx | 6 +- .../reference/subsystems/scalafmt.mdx | 4 +- .../reference/subsystems/scalapb.mdx | 2 +- .../reference/subsystems/scalatest.mdx | 2 +- .../reference/subsystems/setuptools-scm.mdx | 2 +- .../reference/subsystems/setuptools.mdx | 2 +- .../reference/subsystems/shellcheck.mdx | 2 +- .../reference/subsystems/shfmt.mdx | 2 +- .../reference/subsystems/terraform-fmt.mdx | 2 +- .../subsystems/terraform-hcl2-parser.mdx | 2 +- .../subsystems/terraform-validate.mdx | 2 +- .../reference/subsystems/twine.mdx | 4 +- .../reference/subsystems/yapf.mdx | 6 +- .../reference/targets/archive.mdx | 12 +- .../reference/targets/deploy_jar.mdx | 10 +- .../reference/targets/docker_image.mdx | 10 +- .../experimental_run_shell_command.mdx | 8 +- .../targets/experimental_shell_command.mdx | 8 +- .../version-2.13/reference/targets/file.mdx | 8 +- .../version-2.13/reference/targets/files.mdx | 8 +- .../reference/targets/go_binary.mdx | 6 +- .../version-2.13/reference/targets/go_mod.mdx | 4 +- .../reference/targets/go_package.mdx | 8 +- .../targets/go_third_party_package.mdx | 8 +- .../reference/targets/helm_artifact.mdx | 4 +- .../reference/targets/helm_chart.mdx | 14 +- .../reference/targets/helm_unittest_test.mdx | 8 +- .../reference/targets/helm_unittest_tests.mdx | 12 +- .../reference/targets/java_source.mdx | 8 +- .../reference/targets/java_sources.mdx | 8 +- .../reference/targets/junit_test.mdx | 8 +- .../reference/targets/junit_tests.mdx | 8 +- .../reference/targets/jvm_artifact.mdx | 4 +- .../reference/targets/jvm_war.mdx | 10 +- .../reference/targets/kotlin_junit_test.mdx | 8 +- .../reference/targets/kotlin_junit_tests.mdx | 8 +- .../reference/targets/kotlin_source.mdx | 8 +- .../reference/targets/kotlin_sources.mdx | 8 +- .../reference/targets/kotlinc_plugin.mdx | 4 +- .../reference/targets/pants_requirements.mdx | 4 +- .../reference/targets/pex_binaries.mdx | 8 +- .../reference/targets/pex_binary.mdx | 10 +- .../reference/targets/pipenv_requirements.mdx | 4 +- .../reference/targets/poetry_requirements.mdx | 4 +- .../reference/targets/protobuf_source.mdx | 8 +- .../reference/targets/protobuf_sources.mdx | 8 +- .../reference/targets/pyoxidizer_binary.mdx | 6 +- .../reference/targets/python_awslambda.mdx | 10 +- .../reference/targets/python_distribution.mdx | 10 +- .../targets/python_google_cloud_function.mdx | 10 +- .../reference/targets/python_requirement.mdx | 8 +- .../reference/targets/python_requirements.mdx | 4 +- .../reference/targets/python_source.mdx | 8 +- .../reference/targets/python_sources.mdx | 8 +- .../reference/targets/python_test.mdx | 18 +- .../reference/targets/python_test_utils.mdx | 8 +- .../reference/targets/python_tests.mdx | 14 +- .../reference/targets/relocated_files.mdx | 4 +- .../reference/targets/resource.mdx | 8 +- .../reference/targets/resources.mdx | 8 +- .../reference/targets/scala_junit_test.mdx | 8 +- .../reference/targets/scala_junit_tests.mdx | 8 +- .../reference/targets/scala_source.mdx | 8 +- .../reference/targets/scala_sources.mdx | 8 +- .../reference/targets/scalac_plugin.mdx | 4 +- .../reference/targets/scalatest_test.mdx | 8 +- .../reference/targets/scalatest_tests.mdx | 8 +- .../reference/targets/shell_source.mdx | 8 +- .../reference/targets/shell_sources.mdx | 8 +- .../reference/targets/shunit2_test.mdx | 14 +- .../reference/targets/shunit2_tests.mdx | 14 +- .../version-2.13/reference/targets/target.mdx | 8 +- .../reference/targets/terraform_module.mdx | 8 +- .../reference/targets/thrift_source.mdx | 8 +- .../reference/targets/thrift_sources.mdx | 8 +- .../reference/targets/vcs_version.mdx | 4 +- .../version-2.14/reference/global-options.mdx | 14 +- .../reference/goals/experimental-bsp.mdx | 2 +- .../reference/goals/generate-lockfiles.mdx | 4 +- .../version-2.14/reference/goals/lint.mdx | 2 +- .../version-2.14/reference/help-all.json | 564 ++++++------- .../reference/subsystems/autoflake.mdx | 6 +- .../reference/subsystems/bandit.mdx | 6 +- .../reference/subsystems/black.mdx | 6 +- .../version-2.14/reference/subsystems/buf.mdx | 4 +- .../reference/subsystems/buildifier.mdx | 2 +- .../version-2.14/reference/subsystems/cli.mdx | 2 +- .../reference/subsystems/coverage-py.mdx | 2 +- .../reference/subsystems/debugpy.mdx | 2 +- .../reference/subsystems/docformatter.mdx | 6 +- .../reference/subsystems/docker.mdx | 2 +- .../subsystems/dockerfile-parser.mdx | 2 +- .../reference/subsystems/flake8.mdx | 6 +- .../reference/subsystems/gofmt.mdx | 2 +- .../subsystems/google-java-format.mdx | 4 +- .../reference/subsystems/hadolint.mdx | 2 +- .../reference/subsystems/helm-k8s-parser.mdx | 2 +- .../subsystems/helm-post-renderer.mdx | 2 +- .../reference/subsystems/ipython.mdx | 2 +- .../reference/subsystems/isort.mdx | 6 +- .../reference/subsystems/junit.mdx | 2 +- .../reference/subsystems/ktlint.mdx | 4 +- .../reference/subsystems/lambdex.mdx | 2 +- .../reference/subsystems/mypy-protobuf.mdx | 2 +- .../reference/subsystems/mypy.mdx | 8 +- .../reference/subsystems/poetry.mdx | 2 +- .../subsystems/protobuf-java-grpc.mdx | 2 +- .../reference/subsystems/pylint.mdx | 6 +- .../reference/subsystems/pyoxidizer.mdx | 2 +- .../reference/subsystems/pytest.mdx | 4 +- .../reference/subsystems/python-infer.mdx | 2 +- .../reference/subsystems/python.mdx | 12 +- .../reference/subsystems/pyupgrade.mdx | 6 +- .../reference/subsystems/scalafmt.mdx | 4 +- .../reference/subsystems/scalapb.mdx | 2 +- .../reference/subsystems/scalatest.mdx | 2 +- .../reference/subsystems/setuptools-scm.mdx | 2 +- .../reference/subsystems/setuptools.mdx | 2 +- .../reference/subsystems/shellcheck.mdx | 2 +- .../reference/subsystems/shfmt.mdx | 2 +- .../reference/subsystems/terraform-fmt.mdx | 2 +- .../subsystems/terraform-hcl2-parser.mdx | 2 +- .../subsystems/terraform-validate.mdx | 2 +- .../reference/subsystems/twine.mdx | 4 +- .../reference/subsystems/yapf.mdx | 6 +- .../reference/targets/archive.mdx | 12 +- .../reference/targets/deploy_jar.mdx | 10 +- .../reference/targets/docker_image.mdx | 10 +- .../experimental_run_shell_command.mdx | 8 +- .../targets/experimental_shell_command.mdx | 8 +- .../version-2.14/reference/targets/file.mdx | 8 +- .../version-2.14/reference/targets/files.mdx | 8 +- .../reference/targets/go_binary.mdx | 6 +- .../version-2.14/reference/targets/go_mod.mdx | 4 +- .../reference/targets/go_package.mdx | 8 +- .../targets/go_third_party_package.mdx | 8 +- .../reference/targets/helm_artifact.mdx | 4 +- .../reference/targets/helm_chart.mdx | 14 +- .../reference/targets/helm_deployment.mdx | 8 +- .../reference/targets/helm_unittest_test.mdx | 8 +- .../reference/targets/helm_unittest_tests.mdx | 12 +- .../reference/targets/java_source.mdx | 8 +- .../reference/targets/java_sources.mdx | 8 +- .../reference/targets/junit_test.mdx | 8 +- .../reference/targets/junit_tests.mdx | 8 +- .../reference/targets/jvm_artifact.mdx | 4 +- .../reference/targets/jvm_war.mdx | 10 +- .../reference/targets/kotlin_junit_test.mdx | 8 +- .../reference/targets/kotlin_junit_tests.mdx | 8 +- .../reference/targets/kotlin_source.mdx | 8 +- .../reference/targets/kotlin_sources.mdx | 8 +- .../reference/targets/kotlinc_plugin.mdx | 4 +- .../reference/targets/pants_requirements.mdx | 4 +- .../reference/targets/pex_binaries.mdx | 8 +- .../reference/targets/pex_binary.mdx | 10 +- .../reference/targets/pipenv_requirements.mdx | 4 +- .../reference/targets/poetry_requirements.mdx | 4 +- .../reference/targets/protobuf_source.mdx | 8 +- .../reference/targets/protobuf_sources.mdx | 8 +- .../reference/targets/pyoxidizer_binary.mdx | 6 +- .../reference/targets/python_awslambda.mdx | 10 +- .../reference/targets/python_distribution.mdx | 10 +- .../targets/python_google_cloud_function.mdx | 10 +- .../reference/targets/python_requirement.mdx | 8 +- .../reference/targets/python_requirements.mdx | 4 +- .../reference/targets/python_source.mdx | 8 +- .../reference/targets/python_sources.mdx | 8 +- .../reference/targets/python_test.mdx | 18 +- .../reference/targets/python_test_utils.mdx | 8 +- .../reference/targets/python_tests.mdx | 14 +- .../reference/targets/relocated_files.mdx | 4 +- .../reference/targets/resource.mdx | 8 +- .../reference/targets/resources.mdx | 8 +- .../reference/targets/scala_junit_test.mdx | 8 +- .../reference/targets/scala_junit_tests.mdx | 8 +- .../reference/targets/scala_source.mdx | 8 +- .../reference/targets/scala_sources.mdx | 8 +- .../reference/targets/scalac_plugin.mdx | 4 +- .../reference/targets/scalatest_test.mdx | 8 +- .../reference/targets/scalatest_tests.mdx | 8 +- .../reference/targets/shell_source.mdx | 8 +- .../reference/targets/shell_sources.mdx | 8 +- .../reference/targets/shunit2_test.mdx | 14 +- .../reference/targets/shunit2_tests.mdx | 14 +- .../version-2.14/reference/targets/target.mdx | 8 +- .../reference/targets/terraform_module.mdx | 8 +- .../reference/targets/thrift_source.mdx | 8 +- .../reference/targets/thrift_sources.mdx | 8 +- .../reference/targets/vcs_version.mdx | 4 +- .../version-2.15/reference/global-options.mdx | 6 +- .../reference/goals/experimental-bsp.mdx | 2 +- .../version-2.15/reference/goals/fix.mdx | 2 +- .../reference/goals/generate-lockfiles.mdx | 4 +- .../version-2.15/reference/goals/lint.mdx | 4 +- .../version-2.15/reference/help-all.json | 632 +++++++-------- .../subsystems/add-trailing-comma.mdx | 6 +- .../reference/subsystems/autoflake.mdx | 6 +- .../reference/subsystems/bandit.mdx | 6 +- .../reference/subsystems/black.mdx | 6 +- .../version-2.15/reference/subsystems/buf.mdx | 4 +- .../subsystems/build-deprecations-fixer.mdx | 2 +- .../reference/subsystems/buildifier.mdx | 2 +- .../version-2.15/reference/subsystems/cli.mdx | 2 +- .../reference/subsystems/coverage-py.mdx | 2 +- .../reference/subsystems/debugpy.mdx | 2 +- .../reference/subsystems/docformatter.mdx | 6 +- .../reference/subsystems/docker.mdx | 2 +- .../subsystems/dockerfile-parser.mdx | 2 +- .../reference/subsystems/flake8.mdx | 6 +- .../reference/subsystems/go-test.mdx | 2 +- .../reference/subsystems/gofmt.mdx | 2 +- .../subsystems/google-java-format.mdx | 4 +- .../reference/subsystems/hadolint.mdx | 2 +- .../reference/subsystems/helm-k8s-parser.mdx | 2 +- .../subsystems/helm-post-renderer.mdx | 2 +- .../reference/subsystems/helm-unittest.mdx | 2 +- .../reference/subsystems/ipython.mdx | 2 +- .../reference/subsystems/isort.mdx | 6 +- .../reference/subsystems/junit.mdx | 4 +- .../reference/subsystems/ktlint.mdx | 4 +- .../reference/subsystems/lambdex.mdx | 2 +- .../reference/subsystems/mypy-protobuf.mdx | 2 +- .../reference/subsystems/mypy.mdx | 8 +- .../subsystems/protobuf-java-grpc.mdx | 2 +- .../reference/subsystems/pylint.mdx | 6 +- .../reference/subsystems/pyoxidizer.mdx | 2 +- .../reference/subsystems/pytest.mdx | 6 +- .../reference/subsystems/python-infer.mdx | 2 +- .../reference/subsystems/python.mdx | 8 +- .../reference/subsystems/pyupgrade.mdx | 6 +- .../reference/subsystems/regex-lint.mdx | 2 +- .../reference/subsystems/scalafmt.mdx | 4 +- .../reference/subsystems/scalapb.mdx | 2 +- .../reference/subsystems/scalatest.mdx | 4 +- .../reference/subsystems/setuptools-scm.mdx | 2 +- .../reference/subsystems/setuptools.mdx | 2 +- .../reference/subsystems/shellcheck.mdx | 2 +- .../reference/subsystems/shfmt.mdx | 2 +- .../reference/subsystems/shunit2.mdx | 2 +- .../reference/subsystems/spectral.mdx | 2 +- .../reference/subsystems/terraform-fmt.mdx | 2 +- .../subsystems/terraform-hcl2-parser.mdx | 2 +- .../subsystems/terraform-validate.mdx | 2 +- .../reference/subsystems/twine.mdx | 4 +- .../reference/subsystems/yapf.mdx | 6 +- .../reference/targets/archive.mdx | 12 +- .../reference/targets/deploy_jar.mdx | 10 +- .../reference/targets/docker_environment.mdx | 4 +- .../reference/targets/docker_image.mdx | 10 +- .../experimental_run_shell_command.mdx | 8 +- .../targets/experimental_shell_command.mdx | 8 +- .../version-2.15/reference/targets/file.mdx | 8 +- .../version-2.15/reference/targets/files.mdx | 8 +- .../reference/targets/go_binary.mdx | 6 +- .../version-2.15/reference/targets/go_mod.mdx | 4 +- .../reference/targets/go_package.mdx | 8 +- .../targets/go_third_party_package.mdx | 8 +- .../reference/targets/helm_artifact.mdx | 4 +- .../reference/targets/helm_chart.mdx | 14 +- .../reference/targets/helm_deployment.mdx | 8 +- .../reference/targets/helm_unittest_test.mdx | 8 +- .../reference/targets/helm_unittest_tests.mdx | 12 +- .../reference/targets/java_source.mdx | 8 +- .../reference/targets/java_sources.mdx | 8 +- .../reference/targets/junit_test.mdx | 8 +- .../reference/targets/junit_tests.mdx | 8 +- .../reference/targets/jvm_artifact.mdx | 4 +- .../reference/targets/jvm_war.mdx | 10 +- .../reference/targets/kotlin_junit_test.mdx | 8 +- .../reference/targets/kotlin_junit_tests.mdx | 8 +- .../reference/targets/kotlin_source.mdx | 8 +- .../reference/targets/kotlin_sources.mdx | 8 +- .../reference/targets/kotlinc_plugin.mdx | 4 +- .../reference/targets/local_environment.mdx | 4 +- .../reference/targets/openapi_document.mdx | 8 +- .../reference/targets/openapi_documents.mdx | 8 +- .../reference/targets/openapi_source.mdx | 8 +- .../reference/targets/openapi_sources.mdx | 8 +- .../reference/targets/pants_requirements.mdx | 4 +- .../reference/targets/pex_binaries.mdx | 8 +- .../reference/targets/pex_binary.mdx | 10 +- .../reference/targets/pipenv_requirements.mdx | 4 +- .../reference/targets/poetry_requirements.mdx | 4 +- .../reference/targets/protobuf_source.mdx | 8 +- .../reference/targets/protobuf_sources.mdx | 8 +- .../reference/targets/pyoxidizer_binary.mdx | 6 +- .../reference/targets/python_awslambda.mdx | 10 +- .../reference/targets/python_distribution.mdx | 10 +- .../targets/python_google_cloud_function.mdx | 10 +- .../reference/targets/python_requirement.mdx | 8 +- .../reference/targets/python_requirements.mdx | 4 +- .../reference/targets/python_source.mdx | 8 +- .../reference/targets/python_sources.mdx | 8 +- .../reference/targets/python_test.mdx | 14 +- .../reference/targets/python_test_utils.mdx | 8 +- .../reference/targets/python_tests.mdx | 14 +- .../reference/targets/relocated_files.mdx | 4 +- .../reference/targets/remote_environment.mdx | 4 +- .../reference/targets/resource.mdx | 8 +- .../reference/targets/resources.mdx | 8 +- .../reference/targets/scala_junit_test.mdx | 8 +- .../reference/targets/scala_junit_tests.mdx | 8 +- .../reference/targets/scala_source.mdx | 8 +- .../reference/targets/scala_sources.mdx | 8 +- .../reference/targets/scalac_plugin.mdx | 4 +- .../reference/targets/scalatest_test.mdx | 8 +- .../reference/targets/scalatest_tests.mdx | 8 +- .../reference/targets/shell_source.mdx | 8 +- .../reference/targets/shell_sources.mdx | 8 +- .../reference/targets/shunit2_test.mdx | 14 +- .../reference/targets/shunit2_tests.mdx | 14 +- .../version-2.15/reference/targets/target.mdx | 8 +- .../reference/targets/terraform_module.mdx | 8 +- .../reference/targets/thrift_source.mdx | 8 +- .../reference/targets/thrift_sources.mdx | 8 +- .../reference/targets/vcs_version.mdx | 4 +- .../version-2.16/reference/global-options.mdx | 6 +- .../reference/goals/experimental-bsp.mdx | 2 +- .../version-2.16/reference/goals/fix.mdx | 2 +- .../reference/goals/generate-lockfiles.mdx | 4 +- .../version-2.16/reference/goals/lint.mdx | 4 +- .../version-2.16/reference/help-all.json | 690 ++++++++-------- .../subsystems/add-trailing-comma.mdx | 6 +- .../reference/subsystems/autoflake.mdx | 6 +- .../reference/subsystems/bandit.mdx | 6 +- .../reference/subsystems/black.mdx | 6 +- .../version-2.16/reference/subsystems/buf.mdx | 4 +- .../subsystems/build-deprecations-fixer.mdx | 2 +- .../reference/subsystems/buildifier.mdx | 2 +- .../version-2.16/reference/subsystems/cli.mdx | 2 +- .../reference/subsystems/coverage-py.mdx | 2 +- .../reference/subsystems/debugpy.mdx | 2 +- .../reference/subsystems/docformatter.mdx | 6 +- .../reference/subsystems/docker.mdx | 2 +- .../subsystems/dockerfile-parser.mdx | 2 +- .../reference/subsystems/flake8.mdx | 6 +- .../reference/subsystems/go-test.mdx | 2 +- .../reference/subsystems/gofmt.mdx | 2 +- .../subsystems/google-java-format.mdx | 4 +- .../reference/subsystems/hadolint.mdx | 2 +- .../reference/subsystems/helm-k8s-parser.mdx | 2 +- .../subsystems/helm-post-renderer.mdx | 2 +- .../reference/subsystems/helm-unittest.mdx | 2 +- .../reference/subsystems/ipython.mdx | 2 +- .../reference/subsystems/isort.mdx | 6 +- .../reference/subsystems/jarjar.mdx | 2 +- .../reference/subsystems/junit.mdx | 4 +- .../reference/subsystems/ktlint.mdx | 4 +- .../reference/subsystems/lambdex.mdx | 2 +- .../reference/subsystems/mypy-protobuf.mdx | 2 +- .../reference/subsystems/mypy.mdx | 8 +- .../reference/subsystems/preamble.mdx | 2 +- .../subsystems/protobuf-java-grpc.mdx | 2 +- .../reference/subsystems/pydocstyle.mdx | 6 +- .../reference/subsystems/pylint.mdx | 6 +- .../reference/subsystems/pyoxidizer.mdx | 2 +- .../reference/subsystems/pytest.mdx | 6 +- .../reference/subsystems/python-infer.mdx | 2 +- .../reference/subsystems/python.mdx | 8 +- .../reference/subsystems/pyupgrade.mdx | 6 +- .../reference/subsystems/regex-lint.mdx | 2 +- .../reference/subsystems/ruff.mdx | 6 +- .../reference/subsystems/scalafmt.mdx | 4 +- .../reference/subsystems/scalapb.mdx | 2 +- .../reference/subsystems/scalatest.mdx | 4 +- .../reference/subsystems/setuptools-scm.mdx | 2 +- .../reference/subsystems/setuptools.mdx | 2 +- .../reference/subsystems/shell-test.mdx | 2 +- .../reference/subsystems/shellcheck.mdx | 2 +- .../reference/subsystems/shfmt.mdx | 2 +- .../reference/subsystems/shunit2.mdx | 2 +- .../reference/subsystems/spectral.mdx | 2 +- .../reference/subsystems/terraform-fmt.mdx | 2 +- .../subsystems/terraform-hcl2-parser.mdx | 2 +- .../subsystems/terraform-validate.mdx | 2 +- .../reference/subsystems/twine.mdx | 4 +- .../reference/subsystems/yamllint.mdx | 6 +- .../reference/subsystems/yapf.mdx | 6 +- .../reference/targets/adhoc_tool.mdx | 4 +- .../reference/targets/archive.mdx | 12 +- .../reference/targets/deploy_jar.mdx | 10 +- .../reference/targets/docker_environment.mdx | 4 +- .../reference/targets/docker_image.mdx | 12 +- .../experimental_test_shell_command.mdx | 4 +- ...xperimental_wrap_as_go_package_sources.mdx | 4 +- .../experimental_wrap_as_java_sources.mdx | 4 +- .../experimental_wrap_as_kotlin_sources.mdx | 4 +- .../experimental_wrap_as_python_sources.mdx | 4 +- .../experimental_wrap_as_resources.mdx | 4 +- .../experimental_wrap_as_scala_sources.mdx | 4 +- .../version-2.16/reference/targets/file.mdx | 8 +- .../version-2.16/reference/targets/files.mdx | 8 +- .../reference/targets/go_binary.mdx | 6 +- .../version-2.16/reference/targets/go_mod.mdx | 4 +- .../reference/targets/go_package.mdx | 8 +- .../targets/go_third_party_package.mdx | 8 +- .../reference/targets/helm_artifact.mdx | 4 +- .../reference/targets/helm_chart.mdx | 14 +- .../reference/targets/helm_deployment.mdx | 8 +- .../reference/targets/helm_unittest_test.mdx | 8 +- .../reference/targets/helm_unittest_tests.mdx | 12 +- .../reference/targets/java_source.mdx | 8 +- .../reference/targets/java_sources.mdx | 8 +- .../reference/targets/junit_test.mdx | 8 +- .../reference/targets/junit_tests.mdx | 8 +- .../reference/targets/jvm_artifact.mdx | 4 +- .../reference/targets/jvm_war.mdx | 10 +- .../reference/targets/kotlin_junit_test.mdx | 8 +- .../reference/targets/kotlin_junit_tests.mdx | 8 +- .../reference/targets/kotlin_source.mdx | 8 +- .../reference/targets/kotlin_sources.mdx | 8 +- .../reference/targets/kotlinc_plugin.mdx | 4 +- .../reference/targets/local_environment.mdx | 4 +- .../reference/targets/openapi_document.mdx | 8 +- .../reference/targets/openapi_documents.mdx | 8 +- .../reference/targets/openapi_source.mdx | 8 +- .../reference/targets/openapi_sources.mdx | 8 +- .../reference/targets/pants_requirements.mdx | 4 +- .../reference/targets/pex_binaries.mdx | 8 +- .../reference/targets/pex_binary.mdx | 10 +- .../reference/targets/pipenv_requirements.mdx | 4 +- .../reference/targets/poetry_requirements.mdx | 4 +- .../reference/targets/protobuf_source.mdx | 8 +- .../reference/targets/protobuf_sources.mdx | 8 +- .../reference/targets/pyoxidizer_binary.mdx | 6 +- .../reference/targets/python_awslambda.mdx | 10 +- .../reference/targets/python_distribution.mdx | 10 +- .../targets/python_google_cloud_function.mdx | 10 +- .../reference/targets/python_requirement.mdx | 8 +- .../reference/targets/python_requirements.mdx | 4 +- .../reference/targets/python_source.mdx | 8 +- .../reference/targets/python_sources.mdx | 8 +- .../reference/targets/python_test.mdx | 14 +- .../reference/targets/python_test_utils.mdx | 8 +- .../reference/targets/python_tests.mdx | 14 +- .../reference/targets/relocated_files.mdx | 4 +- .../reference/targets/remote_environment.mdx | 4 +- .../reference/targets/resource.mdx | 8 +- .../reference/targets/resources.mdx | 8 +- .../reference/targets/run_shell_command.mdx | 4 +- .../reference/targets/scala_junit_test.mdx | 8 +- .../reference/targets/scala_junit_tests.mdx | 8 +- .../reference/targets/scala_source.mdx | 8 +- .../reference/targets/scala_sources.mdx | 8 +- .../reference/targets/scalac_plugin.mdx | 4 +- .../reference/targets/scalatest_test.mdx | 8 +- .../reference/targets/scalatest_tests.mdx | 8 +- .../reference/targets/shell_command.mdx | 4 +- .../reference/targets/shell_source.mdx | 8 +- .../reference/targets/shell_sources.mdx | 8 +- .../reference/targets/shunit2_test.mdx | 14 +- .../reference/targets/shunit2_tests.mdx | 14 +- .../reference/targets/system_binary.mdx | 4 +- .../version-2.16/reference/targets/target.mdx | 8 +- .../reference/targets/terraform_module.mdx | 8 +- .../reference/targets/thrift_source.mdx | 8 +- .../reference/targets/thrift_sources.mdx | 8 +- .../reference/targets/vcs_version.mdx | 4 +- .../version-2.17/reference/global-options.mdx | 6 +- .../reference/goals/experimental-bsp.mdx | 2 +- .../version-2.17/reference/goals/fix.mdx | 2 +- .../reference/goals/generate-lockfiles.mdx | 4 +- .../version-2.17/reference/goals/lint.mdx | 4 +- .../version-2.17/reference/help-all.json | 692 ++++++++-------- .../subsystems/add-trailing-comma.mdx | 6 +- .../reference/subsystems/autoflake.mdx | 6 +- .../reference/subsystems/bandit.mdx | 6 +- .../reference/subsystems/black.mdx | 6 +- .../version-2.17/reference/subsystems/buf.mdx | 4 +- .../subsystems/build-deprecations-fixer.mdx | 2 +- .../reference/subsystems/buildifier.mdx | 2 +- .../version-2.17/reference/subsystems/cli.mdx | 2 +- .../reference/subsystems/coverage-py.mdx | 2 +- .../reference/subsystems/debugpy.mdx | 2 +- .../reference/subsystems/docformatter.mdx | 6 +- .../reference/subsystems/docker.mdx | 2 +- .../subsystems/dockerfile-parser.mdx | 2 +- .../reference/subsystems/flake8.mdx | 6 +- .../reference/subsystems/go-test.mdx | 2 +- .../reference/subsystems/gofmt.mdx | 2 +- .../subsystems/google-java-format.mdx | 4 +- .../reference/subsystems/hadolint.mdx | 2 +- .../reference/subsystems/helm-k8s-parser.mdx | 2 +- .../subsystems/helm-post-renderer.mdx | 2 +- .../reference/subsystems/helm-unittest.mdx | 2 +- .../reference/subsystems/ipython.mdx | 2 +- .../reference/subsystems/isort.mdx | 6 +- .../reference/subsystems/jarjar.mdx | 2 +- .../reference/subsystems/junit.mdx | 4 +- .../reference/subsystems/ktlint.mdx | 4 +- .../reference/subsystems/lambdex.mdx | 2 +- .../reference/subsystems/mypy-protobuf.mdx | 2 +- .../reference/subsystems/mypy.mdx | 8 +- .../reference/subsystems/nodejs.mdx | 2 +- .../reference/subsystems/preamble.mdx | 2 +- .../subsystems/protobuf-java-grpc.mdx | 2 +- .../reference/subsystems/pydocstyle.mdx | 6 +- .../reference/subsystems/pylint.mdx | 6 +- .../reference/subsystems/pyoxidizer.mdx | 2 +- .../reference/subsystems/pytest.mdx | 6 +- .../reference/subsystems/python-infer.mdx | 4 +- .../reference/subsystems/python.mdx | 8 +- .../reference/subsystems/pyupgrade.mdx | 6 +- .../reference/subsystems/regex-lint.mdx | 2 +- .../reference/subsystems/ruff.mdx | 6 +- .../reference/subsystems/scalafmt.mdx | 4 +- .../reference/subsystems/scalapb.mdx | 2 +- .../reference/subsystems/scalatest.mdx | 4 +- .../reference/subsystems/setuptools-scm.mdx | 2 +- .../reference/subsystems/setuptools.mdx | 2 +- .../reference/subsystems/shell-test.mdx | 2 +- .../reference/subsystems/shellcheck.mdx | 2 +- .../reference/subsystems/shfmt.mdx | 2 +- .../reference/subsystems/shunit2.mdx | 2 +- .../reference/subsystems/spectral.mdx | 2 +- .../reference/subsystems/terraform-fmt.mdx | 2 +- .../subsystems/terraform-hcl2-parser.mdx | 2 +- .../subsystems/terraform-validate.mdx | 2 +- .../reference/subsystems/twine.mdx | 4 +- .../reference/subsystems/yamllint.mdx | 6 +- .../reference/subsystems/yapf.mdx | 6 +- .../reference/targets/adhoc_tool.mdx | 4 +- .../reference/targets/archive.mdx | 12 +- .../reference/targets/deploy_jar.mdx | 10 +- .../reference/targets/docker_environment.mdx | 4 +- .../reference/targets/docker_image.mdx | 12 +- .../experimental_test_shell_command.mdx | 4 +- ...xperimental_wrap_as_go_package_sources.mdx | 4 +- .../experimental_wrap_as_java_sources.mdx | 4 +- .../experimental_wrap_as_kotlin_sources.mdx | 4 +- .../experimental_wrap_as_python_sources.mdx | 4 +- .../experimental_wrap_as_resources.mdx | 4 +- .../experimental_wrap_as_scala_sources.mdx | 4 +- .../version-2.17/reference/targets/file.mdx | 8 +- .../version-2.17/reference/targets/files.mdx | 8 +- .../reference/targets/go_binary.mdx | 6 +- .../version-2.17/reference/targets/go_mod.mdx | 4 +- .../reference/targets/go_package.mdx | 8 +- .../targets/go_third_party_package.mdx | 8 +- .../reference/targets/helm_artifact.mdx | 4 +- .../reference/targets/helm_chart.mdx | 14 +- .../reference/targets/helm_deployment.mdx | 8 +- .../reference/targets/helm_unittest_test.mdx | 8 +- .../reference/targets/helm_unittest_tests.mdx | 8 +- .../reference/targets/java_source.mdx | 8 +- .../reference/targets/java_sources.mdx | 8 +- .../reference/targets/junit_test.mdx | 8 +- .../reference/targets/junit_tests.mdx | 8 +- .../reference/targets/jvm_artifact.mdx | 4 +- .../reference/targets/jvm_war.mdx | 10 +- .../reference/targets/kotlin_junit_test.mdx | 8 +- .../reference/targets/kotlin_junit_tests.mdx | 8 +- .../reference/targets/kotlin_source.mdx | 8 +- .../reference/targets/kotlin_sources.mdx | 8 +- .../reference/targets/kotlinc_plugin.mdx | 4 +- .../reference/targets/local_environment.mdx | 4 +- .../reference/targets/openapi_document.mdx | 8 +- .../reference/targets/openapi_documents.mdx | 8 +- .../reference/targets/openapi_source.mdx | 8 +- .../reference/targets/openapi_sources.mdx | 8 +- .../reference/targets/pants_requirements.mdx | 4 +- .../reference/targets/pex_binaries.mdx | 8 +- .../reference/targets/pex_binary.mdx | 10 +- .../reference/targets/pipenv_requirements.mdx | 4 +- .../reference/targets/poetry_requirements.mdx | 4 +- .../reference/targets/protobuf_source.mdx | 8 +- .../reference/targets/protobuf_sources.mdx | 8 +- .../reference/targets/pyoxidizer_binary.mdx | 6 +- .../reference/targets/python_awslambda.mdx | 10 +- .../reference/targets/python_distribution.mdx | 10 +- .../targets/python_google_cloud_function.mdx | 10 +- .../reference/targets/python_requirement.mdx | 8 +- .../reference/targets/python_requirements.mdx | 4 +- .../reference/targets/python_source.mdx | 8 +- .../reference/targets/python_sources.mdx | 8 +- .../reference/targets/python_test.mdx | 14 +- .../reference/targets/python_test_utils.mdx | 8 +- .../reference/targets/python_tests.mdx | 14 +- .../reference/targets/relocated_files.mdx | 4 +- .../reference/targets/remote_environment.mdx | 4 +- .../reference/targets/resource.mdx | 8 +- .../reference/targets/resources.mdx | 8 +- .../reference/targets/run_shell_command.mdx | 4 +- .../reference/targets/scala_junit_test.mdx | 8 +- .../reference/targets/scala_junit_tests.mdx | 8 +- .../reference/targets/scala_source.mdx | 8 +- .../reference/targets/scala_sources.mdx | 8 +- .../reference/targets/scalac_plugin.mdx | 4 +- .../reference/targets/scalatest_test.mdx | 8 +- .../reference/targets/scalatest_tests.mdx | 8 +- .../reference/targets/shell_command.mdx | 4 +- .../reference/targets/shell_source.mdx | 8 +- .../reference/targets/shell_sources.mdx | 8 +- .../reference/targets/shunit2_test.mdx | 14 +- .../reference/targets/shunit2_tests.mdx | 14 +- .../reference/targets/system_binary.mdx | 4 +- .../version-2.17/reference/targets/target.mdx | 8 +- .../reference/targets/terraform_module.mdx | 8 +- .../reference/targets/thrift_source.mdx | 8 +- .../reference/targets/thrift_sources.mdx | 8 +- .../reference/targets/vcs_version.mdx | 4 +- .../version-2.18/reference/global-options.mdx | 6 +- .../reference/goals/experimental-bsp.mdx | 2 +- .../version-2.18/reference/goals/fix.mdx | 2 +- .../reference/goals/generate-lockfiles.mdx | 4 +- .../version-2.18/reference/goals/lint.mdx | 4 +- .../version-2.18/reference/help-all.json | 752 ++++++++--------- .../subsystems/add-trailing-comma.mdx | 2 +- .../reference/subsystems/autoflake.mdx | 2 +- .../reference/subsystems/bandit.mdx | 2 +- .../reference/subsystems/black.mdx | 2 +- .../version-2.18/reference/subsystems/buf.mdx | 4 +- .../subsystems/build-deprecations-fixer.mdx | 2 +- .../reference/subsystems/buildifier.mdx | 2 +- .../version-2.18/reference/subsystems/cli.mdx | 2 +- .../reference/subsystems/docformatter.mdx | 2 +- .../reference/subsystems/docker.mdx | 2 +- .../reference/subsystems/flake8.mdx | 2 +- .../reference/subsystems/go-test.mdx | 2 +- .../reference/subsystems/gofmt.mdx | 2 +- .../subsystems/google-java-format.mdx | 4 +- .../reference/subsystems/hadolint.mdx | 2 +- .../reference/subsystems/helm-unittest.mdx | 2 +- .../reference/subsystems/isort.mdx | 2 +- .../reference/subsystems/jarjar.mdx | 2 +- .../reference/subsystems/junit.mdx | 4 +- .../reference/subsystems/ktlint.mdx | 4 +- .../reference/subsystems/mypy.mdx | 2 +- .../reference/subsystems/nodejs.mdx | 2 +- .../reference/subsystems/preamble.mdx | 2 +- .../subsystems/protobuf-java-grpc.mdx | 2 +- .../reference/subsystems/pydocstyle.mdx | 2 +- .../reference/subsystems/pylint.mdx | 2 +- .../reference/subsystems/pytest.mdx | 2 +- .../reference/subsystems/python-infer.mdx | 4 +- .../reference/subsystems/python.mdx | 8 +- .../reference/subsystems/pytype.mdx | 2 +- .../reference/subsystems/pyupgrade.mdx | 2 +- .../reference/subsystems/regex-lint.mdx | 2 +- .../reference/subsystems/ruff.mdx | 2 +- .../reference/subsystems/scalafmt.mdx | 4 +- .../reference/subsystems/scalapb.mdx | 2 +- .../reference/subsystems/scalatest.mdx | 4 +- .../reference/subsystems/shell-test.mdx | 2 +- .../reference/subsystems/shellcheck.mdx | 2 +- .../reference/subsystems/shfmt.mdx | 2 +- .../reference/subsystems/shunit2.mdx | 2 +- .../reference/subsystems/spectral.mdx | 2 +- .../reference/subsystems/terraform-fmt.mdx | 2 +- .../subsystems/terraform-validate.mdx | 2 +- .../reference/subsystems/twine.mdx | 2 +- .../reference/subsystems/yamllint.mdx | 2 +- .../reference/subsystems/yapf.mdx | 2 +- .../reference/targets/adhoc_tool.mdx | 4 +- .../reference/targets/archive.mdx | 12 +- .../reference/targets/deploy_jar.mdx | 10 +- .../reference/targets/docker_environment.mdx | 4 +- .../reference/targets/docker_image.mdx | 12 +- .../experimental_test_shell_command.mdx | 4 +- ...xperimental_wrap_as_go_package_sources.mdx | 4 +- .../experimental_wrap_as_java_sources.mdx | 4 +- .../experimental_wrap_as_kotlin_sources.mdx | 4 +- .../experimental_wrap_as_python_sources.mdx | 4 +- .../experimental_wrap_as_resources.mdx | 4 +- .../experimental_wrap_as_scala_sources.mdx | 4 +- .../version-2.18/reference/targets/file.mdx | 8 +- .../version-2.18/reference/targets/files.mdx | 8 +- .../reference/targets/go_binary.mdx | 6 +- .../version-2.18/reference/targets/go_mod.mdx | 4 +- .../reference/targets/go_package.mdx | 8 +- .../targets/go_third_party_package.mdx | 8 +- .../reference/targets/helm_artifact.mdx | 4 +- .../reference/targets/helm_chart.mdx | 14 +- .../reference/targets/helm_deployment.mdx | 8 +- .../reference/targets/helm_unittest_test.mdx | 8 +- .../reference/targets/helm_unittest_tests.mdx | 8 +- .../reference/targets/java_source.mdx | 8 +- .../reference/targets/java_sources.mdx | 8 +- .../reference/targets/junit_test.mdx | 8 +- .../reference/targets/junit_tests.mdx | 8 +- .../reference/targets/jvm_artifact.mdx | 4 +- .../reference/targets/jvm_war.mdx | 10 +- .../reference/targets/kotlin_junit_test.mdx | 8 +- .../reference/targets/kotlin_junit_tests.mdx | 8 +- .../reference/targets/kotlin_source.mdx | 8 +- .../reference/targets/kotlin_sources.mdx | 8 +- .../reference/targets/kotlinc_plugin.mdx | 4 +- .../reference/targets/local_environment.mdx | 4 +- .../reference/targets/openapi_document.mdx | 8 +- .../reference/targets/openapi_documents.mdx | 8 +- .../reference/targets/openapi_source.mdx | 8 +- .../reference/targets/openapi_sources.mdx | 8 +- .../reference/targets/pants_requirements.mdx | 4 +- .../reference/targets/pex_binaries.mdx | 8 +- .../reference/targets/pex_binary.mdx | 10 +- .../reference/targets/pipenv_requirements.mdx | 4 +- .../reference/targets/poetry_requirements.mdx | 4 +- .../reference/targets/protobuf_source.mdx | 8 +- .../reference/targets/protobuf_sources.mdx | 8 +- .../reference/targets/pyoxidizer_binary.mdx | 6 +- .../targets/python_aws_lambda_function.mdx | 10 +- .../targets/python_aws_lambda_layer.mdx | 10 +- .../reference/targets/python_distribution.mdx | 10 +- .../targets/python_google_cloud_function.mdx | 10 +- .../reference/targets/python_requirement.mdx | 8 +- .../reference/targets/python_requirements.mdx | 4 +- .../reference/targets/python_source.mdx | 8 +- .../reference/targets/python_sources.mdx | 8 +- .../reference/targets/python_test.mdx | 14 +- .../reference/targets/python_test_utils.mdx | 8 +- .../reference/targets/python_tests.mdx | 14 +- .../reference/targets/relocated_files.mdx | 4 +- .../reference/targets/remote_environment.mdx | 4 +- .../reference/targets/resource.mdx | 8 +- .../reference/targets/resources.mdx | 8 +- .../reference/targets/run_shell_command.mdx | 4 +- .../reference/targets/scala_artifact.mdx | 4 +- .../reference/targets/scala_junit_test.mdx | 8 +- .../reference/targets/scala_junit_tests.mdx | 8 +- .../reference/targets/scala_source.mdx | 8 +- .../reference/targets/scala_sources.mdx | 8 +- .../reference/targets/scalac_plugin.mdx | 4 +- .../reference/targets/scalatest_test.mdx | 8 +- .../reference/targets/scalatest_tests.mdx | 8 +- .../reference/targets/shell_command.mdx | 4 +- .../reference/targets/shell_source.mdx | 8 +- .../reference/targets/shell_sources.mdx | 8 +- .../reference/targets/shunit2_test.mdx | 14 +- .../reference/targets/shunit2_tests.mdx | 14 +- .../reference/targets/system_binary.mdx | 4 +- .../version-2.18/reference/targets/target.mdx | 8 +- .../targets/terraform_deployment.mdx | 8 +- .../reference/targets/terraform_module.mdx | 8 +- .../reference/targets/thrift_source.mdx | 8 +- .../reference/targets/thrift_sources.mdx | 8 +- .../reference/targets/vcs_version.mdx | 4 +- .../version-2.19/reference/global-options.mdx | 6 +- .../reference/goals/experimental-bsp.mdx | 2 +- .../version-2.19/reference/goals/fix.mdx | 2 +- .../reference/goals/generate-lockfiles.mdx | 4 +- .../version-2.19/reference/goals/lint.mdx | 4 +- .../version-2.19/reference/help-all.json | 760 ++++++++--------- .../subsystems/add-trailing-comma.mdx | 2 +- .../reference/subsystems/autoflake.mdx | 2 +- .../reference/subsystems/bandit.mdx | 2 +- .../reference/subsystems/black.mdx | 2 +- .../version-2.19/reference/subsystems/buf.mdx | 4 +- .../subsystems/build-deprecations-fixer.mdx | 2 +- .../reference/subsystems/buildifier.mdx | 2 +- .../version-2.19/reference/subsystems/cli.mdx | 2 +- .../reference/subsystems/docformatter.mdx | 2 +- .../reference/subsystems/docker.mdx | 2 +- .../reference/subsystems/flake8.mdx | 2 +- .../reference/subsystems/go-test.mdx | 2 +- .../reference/subsystems/gofmt.mdx | 2 +- .../subsystems/google-java-format.mdx | 4 +- .../reference/subsystems/hadolint.mdx | 2 +- .../reference/subsystems/helm-unittest.mdx | 2 +- .../reference/subsystems/isort.mdx | 2 +- .../reference/subsystems/jarjar.mdx | 2 +- .../reference/subsystems/junit.mdx | 4 +- .../reference/subsystems/ktlint.mdx | 4 +- .../reference/subsystems/mypy.mdx | 2 +- .../reference/subsystems/nodejs.mdx | 2 +- .../reference/subsystems/openapi-format.mdx | 2 +- .../reference/subsystems/preamble.mdx | 2 +- .../subsystems/protobuf-java-grpc.mdx | 2 +- .../reference/subsystems/pydocstyle.mdx | 2 +- .../reference/subsystems/pylint.mdx | 2 +- .../reference/subsystems/pytest.mdx | 2 +- .../reference/subsystems/python-infer.mdx | 4 +- .../reference/subsystems/python.mdx | 8 +- .../reference/subsystems/pytype.mdx | 2 +- .../reference/subsystems/pyupgrade.mdx | 2 +- .../reference/subsystems/regex-lint.mdx | 2 +- .../reference/subsystems/ruff.mdx | 2 +- .../reference/subsystems/scalafmt.mdx | 4 +- .../reference/subsystems/scalapb.mdx | 2 +- .../reference/subsystems/scalatest.mdx | 4 +- .../reference/subsystems/semgrep.mdx | 2 +- .../reference/subsystems/shell-test.mdx | 2 +- .../reference/subsystems/shellcheck.mdx | 2 +- .../reference/subsystems/shfmt.mdx | 2 +- .../reference/subsystems/shunit2.mdx | 2 +- .../reference/subsystems/spectral.mdx | 2 +- .../reference/subsystems/terraform-fmt.mdx | 2 +- .../subsystems/terraform-validate.mdx | 2 +- .../reference/subsystems/twine.mdx | 2 +- .../reference/subsystems/yamllint.mdx | 2 +- .../reference/subsystems/yapf.mdx | 2 +- .../reference/targets/adhoc_tool.mdx | 4 +- .../reference/targets/archive.mdx | 12 +- .../reference/targets/deploy_jar.mdx | 10 +- .../reference/targets/docker_environment.mdx | 4 +- .../reference/targets/docker_image.mdx | 12 +- .../experimental_test_shell_command.mdx | 4 +- ...xperimental_wrap_as_go_package_sources.mdx | 4 +- .../experimental_wrap_as_java_sources.mdx | 4 +- .../experimental_wrap_as_kotlin_sources.mdx | 4 +- .../experimental_wrap_as_python_sources.mdx | 4 +- .../experimental_wrap_as_resources.mdx | 4 +- .../experimental_wrap_as_scala_sources.mdx | 4 +- .../version-2.19/reference/targets/file.mdx | 8 +- .../version-2.19/reference/targets/files.mdx | 8 +- .../reference/targets/go_binary.mdx | 6 +- .../version-2.19/reference/targets/go_mod.mdx | 4 +- .../reference/targets/go_package.mdx | 8 +- .../targets/go_third_party_package.mdx | 8 +- .../reference/targets/helm_artifact.mdx | 4 +- .../reference/targets/helm_chart.mdx | 14 +- .../reference/targets/helm_deployment.mdx | 8 +- .../reference/targets/helm_unittest_test.mdx | 8 +- .../reference/targets/helm_unittest_tests.mdx | 8 +- .../reference/targets/java_source.mdx | 8 +- .../reference/targets/java_sources.mdx | 8 +- .../reference/targets/junit_test.mdx | 8 +- .../reference/targets/junit_tests.mdx | 8 +- .../reference/targets/jvm_artifact.mdx | 4 +- .../reference/targets/jvm_war.mdx | 10 +- .../reference/targets/kotlin_junit_test.mdx | 8 +- .../reference/targets/kotlin_junit_tests.mdx | 8 +- .../reference/targets/kotlin_source.mdx | 8 +- .../reference/targets/kotlin_sources.mdx | 8 +- .../reference/targets/kotlinc_plugin.mdx | 4 +- .../reference/targets/local_environment.mdx | 4 +- .../reference/targets/openapi_document.mdx | 8 +- .../reference/targets/openapi_documents.mdx | 8 +- .../reference/targets/openapi_source.mdx | 8 +- .../reference/targets/openapi_sources.mdx | 8 +- .../reference/targets/pants_requirements.mdx | 4 +- .../reference/targets/pex_binaries.mdx | 8 +- .../reference/targets/pex_binary.mdx | 10 +- .../reference/targets/pipenv_requirements.mdx | 4 +- .../reference/targets/poetry_requirements.mdx | 4 +- .../reference/targets/protobuf_source.mdx | 8 +- .../reference/targets/protobuf_sources.mdx | 8 +- .../reference/targets/pyoxidizer_binary.mdx | 6 +- .../targets/python_aws_lambda_function.mdx | 10 +- .../targets/python_aws_lambda_layer.mdx | 10 +- .../reference/targets/python_distribution.mdx | 10 +- .../targets/python_google_cloud_function.mdx | 10 +- .../reference/targets/python_requirement.mdx | 8 +- .../reference/targets/python_requirements.mdx | 4 +- .../reference/targets/python_source.mdx | 8 +- .../reference/targets/python_sources.mdx | 8 +- .../reference/targets/python_test.mdx | 14 +- .../reference/targets/python_test_utils.mdx | 8 +- .../reference/targets/python_tests.mdx | 14 +- .../reference/targets/relocated_files.mdx | 4 +- .../reference/targets/remote_environment.mdx | 4 +- .../reference/targets/resource.mdx | 8 +- .../reference/targets/resources.mdx | 8 +- .../reference/targets/run_shell_command.mdx | 4 +- .../reference/targets/scala_artifact.mdx | 4 +- .../reference/targets/scala_junit_test.mdx | 8 +- .../reference/targets/scala_junit_tests.mdx | 8 +- .../reference/targets/scala_source.mdx | 8 +- .../reference/targets/scala_sources.mdx | 8 +- .../reference/targets/scalac_plugin.mdx | 4 +- .../reference/targets/scalatest_test.mdx | 8 +- .../reference/targets/scalatest_tests.mdx | 8 +- .../reference/targets/shell_command.mdx | 4 +- .../reference/targets/shell_source.mdx | 8 +- .../reference/targets/shell_sources.mdx | 8 +- .../reference/targets/shunit2_test.mdx | 14 +- .../reference/targets/shunit2_tests.mdx | 14 +- .../reference/targets/system_binary.mdx | 4 +- .../version-2.19/reference/targets/target.mdx | 8 +- .../targets/terraform_deployment.mdx | 8 +- .../reference/targets/terraform_module.mdx | 8 +- .../reference/targets/thrift_source.mdx | 8 +- .../reference/targets/thrift_sources.mdx | 8 +- .../reference/targets/vcs_version.mdx | 4 +- .../version-2.2/reference/help-all.json | 16 +- .../reference/subsystems/bandit.mdx | 2 +- .../reference/subsystems/black.mdx | 2 +- .../reference/subsystems/docformatter.mdx | 2 +- .../reference/subsystems/flake8.mdx | 2 +- .../reference/subsystems/isort.mdx | 2 +- .../version-2.2/reference/subsystems/mypy.mdx | 2 +- .../reference/subsystems/pylint.mdx | 2 +- .../version-2.3/reference/help-all.json | 16 +- .../reference/subsystems/bandit.mdx | 2 +- .../reference/subsystems/black.mdx | 2 +- .../reference/subsystems/docformatter.mdx | 2 +- .../reference/subsystems/flake8.mdx | 2 +- .../reference/subsystems/isort.mdx | 2 +- .../version-2.3/reference/subsystems/mypy.mdx | 2 +- .../reference/subsystems/pylint.mdx | 2 +- .../version-2.4/reference/help-all.json | 16 +- .../reference/subsystems/bandit.mdx | 2 +- .../reference/subsystems/black.mdx | 2 +- .../reference/subsystems/docformatter.mdx | 2 +- .../reference/subsystems/flake8.mdx | 2 +- .../reference/subsystems/isort.mdx | 2 +- .../version-2.4/reference/subsystems/mypy.mdx | 2 +- .../reference/subsystems/pylint.mdx | 2 +- .../version-2.5/reference/help-all.json | 16 +- .../reference/subsystems/bandit.mdx | 2 +- .../reference/subsystems/black.mdx | 2 +- .../reference/subsystems/docformatter.mdx | 2 +- .../reference/subsystems/flake8.mdx | 2 +- .../reference/subsystems/isort.mdx | 2 +- .../version-2.5/reference/subsystems/mypy.mdx | 2 +- .../reference/subsystems/pylint.mdx | 2 +- .../version-2.6/reference/help-all.json | 16 +- .../reference/subsystems/bandit.mdx | 2 +- .../reference/subsystems/black.mdx | 2 +- .../reference/subsystems/docformatter.mdx | 2 +- .../reference/subsystems/flake8.mdx | 2 +- .../reference/subsystems/isort.mdx | 2 +- .../version-2.6/reference/subsystems/mypy.mdx | 2 +- .../reference/subsystems/pylint.mdx | 2 +- .../version-2.7/reference/help-all.json | 18 +- .../reference/subsystems/bandit.mdx | 2 +- .../reference/subsystems/black.mdx | 2 +- .../reference/subsystems/docformatter.mdx | 2 +- .../reference/subsystems/flake8.mdx | 2 +- .../reference/subsystems/isort.mdx | 2 +- .../version-2.7/reference/subsystems/mypy.mdx | 2 +- .../reference/subsystems/pylint.mdx | 2 +- .../version-2.7/reference/subsystems/yapf.mdx | 2 +- .../version-2.8/reference/help-all.json | 24 +- .../reference/subsystems/autoflake.mdx | 2 +- .../reference/subsystems/bandit.mdx | 2 +- .../reference/subsystems/black.mdx | 2 +- .../reference/subsystems/docformatter.mdx | 2 +- .../reference/subsystems/flake8.mdx | 2 +- .../reference/subsystems/gofmt.mdx | 2 +- .../reference/subsystems/isort.mdx | 2 +- .../version-2.8/reference/subsystems/mypy.mdx | 2 +- .../reference/subsystems/pylint.mdx | 2 +- .../reference/subsystems/pyupgrade.mdx | 2 +- .../version-2.8/reference/subsystems/yapf.mdx | 2 +- .../version-2.9/reference/help-all.json | 28 +- .../reference/subsystems/autoflake.mdx | 2 +- .../reference/subsystems/bandit.mdx | 2 +- .../reference/subsystems/black.mdx | 2 +- .../reference/subsystems/docformatter.mdx | 2 +- .../reference/subsystems/flake8.mdx | 2 +- .../reference/subsystems/gofmt.mdx | 2 +- .../subsystems/google-java-format.mdx | 2 +- .../reference/subsystems/isort.mdx | 2 +- .../version-2.9/reference/subsystems/mypy.mdx | 2 +- .../reference/subsystems/pylint.mdx | 2 +- .../reference/subsystems/pyupgrade.mdx | 2 +- .../reference/subsystems/scalafmt.mdx | 2 +- .../version-2.9/reference/subsystems/yapf.mdx | 2 +- 1339 files changed, 6939 insertions(+), 6939 deletions(-) diff --git a/docs/reference/global-options.mdx b/docs/reference/global-options.mdx index 98885a77c..1c19e09c5 100644 --- a/docs/reference/global-options.mdx +++ b/docs/reference/global-options.mdx @@ -317,9 +317,9 @@ ignore_warnings = [ Use this Pants version. Note that Pants only uses this to verify that you are using the requested version, as Pants cannot dynamically change the version it is using once the program is already running. -If you use the `scie-pants-linux-x86_64` script from https://www.pantsbuild.org/v2.20/docs/installation, however, changing the value in your `pants.toml` will cause the new version to be installed and run automatically. +If you use the `pants` script from https://www.pantsbuild.org/v2.20/docs/installation, however, changing the value in your `pants.toml` will cause the new version to be installed and run automatically. -Run `scie-pants-linux-x86_64 --version` to check what is being used. +Run `pants --version` to check what is being used. @@ -832,7 +832,7 @@ Whether or not to use nailgun to run JVM requests that are marked as supporting default_repr={`3`} > -The time in seconds to wait when gracefully shutting down an interactive process (such as one opened using `scie-pants-linux-x86_64 run`) before killing it. +The time in seconds to wait when gracefully shutting down an interactive process (such as one opened using `pants run`) before killing it. diff --git a/docs/reference/goals/experimental-bsp.mdx b/docs/reference/goals/experimental-bsp.mdx index 5362d9e2f..501fe81ee 100644 --- a/docs/reference/goals/experimental-bsp.mdx +++ b/docs/reference/goals/experimental-bsp.mdx @@ -79,7 +79,7 @@ Run the Build Server Protocol server. Pants will receive BSP RPC requests via th Environment variables to set in the BSP runner script when setting up BSP in a repository. Entries are either strings in the form `ENV_VAR=value` to set an explicit value; or just `ENV_VAR` to copy the value from Pants' own environment when the experimental-bsp goal was run. -This option only takes effect when the BSP runner script is written. If the option changes, you must run `scie-pants-linux-x86_64 experimental-bsp` again to write a new copy of the BSP runner script. +This option only takes effect when the BSP runner script is written. If the option changes, you must run `pants experimental-bsp` again to write a new copy of the BSP runner script. Note: The environment variables passed to the Pants BSP server will be those set for your IDE and not your shell. For example, on macOS, the IDE is generally launched by `launchd` after clicking on a Dock icon, and not from the shell. Thus, any environment variables set for your shell will likely not be seen by the Pants BSP server. At the very least, on macOS consider writing an explicit PATH into the BSP runner script via this option. diff --git a/docs/reference/goals/fix.mdx b/docs/reference/goals/fix.mdx index 1f996ab0d..7c7407fae 100644 --- a/docs/reference/goals/fix.mdx +++ b/docs/reference/goals/fix.mdx @@ -47,7 +47,7 @@ You can repeat this option, e.g. `fix --only=autoflake --only=pyupgrade` or `fix If true, skip running all formatters. -FYI: when running `scie-pants-linux-x86_64 fix fmt ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `fix` where possible. +FYI: when running `pants fix fmt ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `fix` where possible. diff --git a/docs/reference/goals/generate-lockfiles.mdx b/docs/reference/goals/generate-lockfiles.mdx index 08231e6ad..2782ac00a 100644 --- a/docs/reference/goals/generate-lockfiles.mdx +++ b/docs/reference/goals/generate-lockfiles.mdx @@ -33,7 +33,7 @@ Only generate lockfiles for the specified resolve(s). Resolves are the logical names for the different lockfiles used in your project. For your own code's dependencies, these come from backend-specific configuration such as `[python].resolves`. For tool lockfiles, resolve names are the options scope for that tool such as `black`, `pytest`, and `mypy-protobuf`. -For example, you can run `scie-pants-linux-x86_64 generate-lockfiles --resolve=black --resolve=pytest --resolve=data-science` to only generate lockfiles for those two tools and your resolve named `data-science`. +For example, you can run `pants generate-lockfiles --resolve=black --resolve=pytest --resolve=data-science` to only generate lockfiles for those two tools and your resolve named `data-science`. If you specify an invalid resolve name, like 'fake', Pants will output all possible values. @@ -75,7 +75,7 @@ Include unchanged distributions in the diff summary output. Implies `diff=true`. default_repr={`None`} > -If set, lockfile headers will say to run this command to regenerate the lockfile, rather than running `scie-pants-linux-x86_64 generate-lockfiles --resolve=` like normal. +If set, lockfile headers will say to run this command to regenerate the lockfile, rather than running `pants generate-lockfiles --resolve=` like normal. diff --git a/docs/reference/goals/lint.mdx b/docs/reference/goals/lint.mdx index 9607a4b8b..3ab192176 100644 --- a/docs/reference/goals/lint.mdx +++ b/docs/reference/goals/lint.mdx @@ -47,7 +47,7 @@ You can repeat this option, e.g. `lint --only=flake8 --only=shellcheck` or `lint If true, skip running all formatters in check-only mode. -FYI: when running `scie-pants-linux-x86_64 fmt lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `lint` where possible. +FYI: when running `pants fmt lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `lint` where possible. @@ -61,7 +61,7 @@ FYI: when running `scie-pants-linux-x86_64 fmt lint ::`, there should be diminis If true, skip running all fixers in check-only mode. -FYI: when running `scie-pants-linux-x86_64 fix lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fix` when running `lint` where possible. +FYI: when running `pants fix lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fix` when running `lint` where possible. diff --git a/docs/reference/help-all.json b/docs/reference/help-all.json index 8a1b4ede3..71ebfb43b 100644 --- a/docs/reference/help-all.json +++ b/docs/reference/help-all.json @@ -205,7 +205,7 @@ "display_args": ["--[no-]add-trailing-comma-skip"], "env_var": "PANTS_ADD_TRAILING_COMMA_SKIP", "fromfile": false, - "help": "If true, don't use add-trailing-comma when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use add-trailing-comma when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -563,7 +563,7 @@ "display_args": ["--[no-]autoflake-skip"], "env_var": "PANTS_AUTOFLAKE_SKIP", "fromfile": false, - "help": "If true, don't use Autoflake when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Autoflake when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--autoflake-skip", "--no-autoflake-skip"], @@ -877,7 +877,7 @@ "display_args": ["--[no-]bandit-skip"], "env_var": "PANTS_BANDIT_SKIP", "fromfile": false, - "help": "If true, don't use Bandit when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Bandit when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--bandit-skip", "--no-bandit-skip"], @@ -932,7 +932,7 @@ { "details": "from env var PANTS_BIN_NAME", "rank": "ENVIRONMENT", - "value": "/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64" + "value": "/home/josh/work/scie-pants/dist/pants" } ] } @@ -1202,7 +1202,7 @@ "display_args": ["--[no-]black-skip"], "env_var": "PANTS_BLACK_SKIP", "fromfile": false, - "help": "If true, don't use Black when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Black when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--black-skip", "--no-black-skip"], @@ -1332,7 +1332,7 @@ "display_args": ["--[no-]buf-format-skip"], "env_var": "PANTS_BUF_FORMAT_SKIP", "fromfile": false, - "help": "If true, don't use Buf when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Buf when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--buf-format-skip", "--no-buf-format-skip"], @@ -1441,7 +1441,7 @@ "display_args": ["--[no-]buf-lint-skip"], "env_var": "PANTS_BUF_LINT_SKIP", "fromfile": false, - "help": "If true, don't use Buf when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Buf when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--buf-lint-skip", "--no-buf-lint-skip"], @@ -1698,7 +1698,7 @@ "display_args": ["--[no-]buildifier-skip"], "env_var": "PANTS_BUILDIFIER_SKIP", "fromfile": false, - "help": "If true, don't use Buildifier when running `scie-pants-linux-x86_64 fmt`.", + "help": "If true, don't use Buildifier when running `pants fmt`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--buildifier-skip", "--no-buildifier-skip"], @@ -1877,7 +1877,7 @@ "display_args": ["--[no-]build-deprecations-fixer-skip"], "env_var": "PANTS_BUILD_DEPRECATIONS_FIXER_SKIP", "fromfile": false, - "help": "If true, don't use BUILD Deprecations Fixer when running `scie-pants-linux-x86_64 fix`.", + "help": "If true, don't use BUILD Deprecations Fixer when running `pants fix`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -2230,7 +2230,7 @@ "display_args": ["--cli-alias=\"{'key1': val1, 'key2': val2, ...}\""], "env_var": "PANTS_CLI_ALIAS", "fromfile": false, - "help": "Register command line aliases.\n\nExample:\n\n [cli.alias]\n green = \"fmt lint check\"\n all-changed = \"--changed-since=HEAD --changed-dependents=transitive\"\n\nThis would allow you to run `scie-pants-linux-x86_64 green all-changed`, which is shorthand for `scie-pants-linux-x86_64 fmt lint check --changed-since=HEAD --changed-dependents=transitive`.\n\nNotice: this option must be placed in a config file (e.g. `pants.toml` or `pantsrc`) to have any effect.", + "help": "Register command line aliases.\n\nExample:\n\n [cli.alias]\n green = \"fmt lint check\"\n all-changed = \"--changed-since=HEAD --changed-dependents=transitive\"\n\nThis would allow you to run `pants green all-changed`, which is shorthand for `pants fmt lint check --changed-since=HEAD --changed-dependents=transitive`.\n\nNotice: this option must be placed in a config file (e.g. `pants.toml` or `pantsrc`) to have any effect.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--cli-alias"], @@ -3870,7 +3870,7 @@ "display_args": ["--[no-]docformatter-skip"], "env_var": "PANTS_DOCFORMATTER_SKIP", "fromfile": false, - "help": "If true, don't use docformatter when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use docformatter when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--docformatter-skip", "--no-docformatter-skip"], @@ -4373,7 +4373,7 @@ "display_args": ["--docker-run-args=\"[, , ...]\""], "env_var": "PANTS_DOCKER_RUN_ARGS", "fromfile": false, - "help": "Additional arguments to use for `docker run` invocations.\n\nExample:\n\n $ scie-pants-linux-x86_64 run --docker-run-args=\"-p 127.0.0.1:80:8080/tcp --name demo\" src/example:image -- [image entrypoint args]\n\nTo provide the top-level options to the `docker` client, use `[docker].env_vars` to configure the [Environment variables](https://docs.docker.com/engine/reference/commandline/cli/#environment-variables) as appropriate.\n\nThe arguments for the image entrypoint may be passed on the command line after a double dash (`--`), or using the `--run-args` option.\n\nDefaults to `--interactive --tty` when stdout is connected to a terminal.", + "help": "Additional arguments to use for `docker run` invocations.\n\nExample:\n\n $ pants run --docker-run-args=\"-p 127.0.0.1:80:8080/tcp --name demo\" src/example:image -- [image entrypoint args]\n\nTo provide the top-level options to the `docker` client, use `[docker].env_vars` to configure the [Environment variables](https://docs.docker.com/engine/reference/commandline/cli/#environment-variables) as appropriate.\n\nThe arguments for the image entrypoint may be passed on the command line after a double dash (`--`), or using the `--run-args` option.\n\nDefaults to `--interactive --tty` when stdout is connected to a terminal.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--docker-run-args"], @@ -5305,7 +5305,7 @@ ], "env_var": "PANTS_EXPERIMENTAL_BSP_RUNNER_ENV_VARS", "fromfile": false, - "help": "Environment variables to set in the BSP runner script when setting up BSP in a repository. Entries are either strings in the form `ENV_VAR=value` to set an explicit value; or just `ENV_VAR` to copy the value from Pants' own environment when the experimental-bsp goal was run.\n\nThis option only takes effect when the BSP runner script is written. If the option changes, you must run `scie-pants-linux-x86_64 experimental-bsp` again to write a new copy of the BSP runner script.\n\nNote: The environment variables passed to the Pants BSP server will be those set for your IDE and not your shell. For example, on macOS, the IDE is generally launched by `launchd` after clicking on a Dock icon, and not from the shell. Thus, any environment variables set for your shell will likely not be seen by the Pants BSP server. At the very least, on macOS consider writing an explicit PATH into the BSP runner script via this option.", + "help": "Environment variables to set in the BSP runner script when setting up BSP in a repository. Entries are either strings in the form `ENV_VAR=value` to set an explicit value; or just `ENV_VAR` to copy the value from Pants' own environment when the experimental-bsp goal was run.\n\nThis option only takes effect when the BSP runner script is written. If the option changes, you must run `pants experimental-bsp` again to write a new copy of the BSP runner script.\n\nNote: The environment variables passed to the Pants BSP server will be those set for your IDE and not your shell. For example, on macOS, the IDE is generally launched by `launchd` after clicking on a Dock icon, and not from the shell. Thus, any environment variables set for your shell will likely not be seen by the Pants BSP server. At the very least, on macOS consider writing an explicit PATH into the BSP runner script via this option.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--experimental-bsp-runner-env-vars"], @@ -5971,7 +5971,7 @@ "display_args": ["--[no-]fix-skip-formatters"], "env_var": "PANTS_FIX_SKIP_FORMATTERS", "fromfile": false, - "help": "If true, skip running all formatters.\n\nFYI: when running `scie-pants-linux-x86_64 fix fmt ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `fix` where possible.", + "help": "If true, skip running all formatters.\n\nFYI: when running `pants fix fmt ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `fix` where possible.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -6261,7 +6261,7 @@ "display_args": ["--[no-]flake8-skip"], "env_var": "PANTS_FLAKE8_SKIP", "fromfile": false, - "help": "If true, don't use Flake8 when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Flake8 when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--flake8-skip", "--no-flake8-skip"], @@ -6395,7 +6395,7 @@ "display_args": ["--generate-lockfiles-custom-command="], "env_var": "PANTS_GENERATE_LOCKFILES_CUSTOM_COMMAND", "fromfile": false, - "help": "If set, lockfile headers will say to run this command to regenerate the lockfile, rather than running `scie-pants-linux-x86_64 generate-lockfiles --resolve=` like normal.", + "help": "If set, lockfile headers will say to run this command to regenerate the lockfile, rather than running `pants generate-lockfiles --resolve=` like normal.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--generate-lockfiles-custom-command"], @@ -6500,7 +6500,7 @@ ], "env_var": "PANTS_GENERATE_LOCKFILES_RESOLVE", "fromfile": false, - "help": "Only generate lockfiles for the specified resolve(s).\n\nResolves are the logical names for the different lockfiles used in your project. For your own code's dependencies, these come from backend-specific configuration such as `[python].resolves`. For tool lockfiles, resolve names are the options scope for that tool such as `black`, `pytest`, and `mypy-protobuf`.\n\nFor example, you can run `scie-pants-linux-x86_64 generate-lockfiles --resolve=black --resolve=pytest --resolve=data-science` to only generate lockfiles for those two tools and your resolve named `data-science`.\n\nIf you specify an invalid resolve name, like 'fake', Pants will output all possible values.\n\nIf not specified, Pants will generate lockfiles for all resolves.", + "help": "Only generate lockfiles for the specified resolve(s).\n\nResolves are the logical names for the different lockfiles used in your project. For your own code's dependencies, these come from backend-specific configuration such as `[python].resolves`. For tool lockfiles, resolve names are the options scope for that tool such as `black`, `pytest`, and `mypy-protobuf`.\n\nFor example, you can run `pants generate-lockfiles --resolve=black --resolve=pytest --resolve=data-science` to only generate lockfiles for those two tools and your resolve named `data-science`.\n\nIf you specify an invalid resolve name, like 'fake', Pants will output all possible values.\n\nIf not specified, Pants will generate lockfiles for all resolves.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--generate-lockfiles-resolve"], @@ -6566,7 +6566,7 @@ "display_args": ["--[no-]gofmt-skip"], "env_var": "PANTS_GOFMT_SKIP", "fromfile": false, - "help": "If true, don't use gofmt when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use gofmt when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--gofmt-skip", "--no-gofmt-skip"], @@ -7328,7 +7328,7 @@ "display_args": ["--google-java-format-lockfile="], "env_var": "PANTS_GOOGLE_JAVA_FORMAT_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.20.0.dev2/src/python/pants/backend/java/lint/google_java_format/google_java_format.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=google-java-format`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.20.0.dev2/src/python/pants/backend/java/lint/google_java_format/google_java_format.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=google-java-format`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--google-java-format-lockfile"], @@ -7361,7 +7361,7 @@ "display_args": ["--[no-]google-java-format-skip"], "env_var": "PANTS_GOOGLE_JAVA_FORMAT_SKIP", "fromfile": false, - "help": "If true, don't use Google Java Format when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Google Java Format when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -7927,7 +7927,7 @@ "display_args": ["--[no-]go-test-skip"], "env_var": "PANTS_GO_TEST_SKIP", "fromfile": false, - "help": "If true, don't use Go test binary when running `scie-pants-linux-x86_64 test`.", + "help": "If true, don't use Go test binary when running `pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--go-test-skip", "--no-go-test-skip"], @@ -8324,7 +8324,7 @@ "display_args": ["--[no-]hadolint-skip"], "env_var": "PANTS_HADOLINT_SKIP", "fromfile": false, - "help": "If true, don't use Hadolint when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Hadolint when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--hadolint-skip", "--no-hadolint-skip"], @@ -9151,7 +9151,7 @@ "display_args": ["--[no-]helm-unittest-skip"], "env_var": "PANTS_HELM_UNITTEST_SKIP", "fromfile": false, - "help": "If true, don't use helmunittestsubsystem when running `scie-pants-linux-x86_64 test`.", + "help": "If true, don't use helmunittestsubsystem when running `pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -10003,7 +10003,7 @@ "display_args": ["--[no-]isort-skip"], "env_var": "PANTS_ISORT_SKIP", "fromfile": false, - "help": "If true, don't use isort when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use isort when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--isort-skip", "--no-isort-skip"], @@ -10102,7 +10102,7 @@ "display_args": ["--jarjar-lockfile="], "env_var": "PANTS_JARJAR_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.20.0.dev2/src/python/pants/jvm/shading/jarjar.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=jarjar`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.20.0.dev2/src/python/pants/jvm/shading/jarjar.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=jarjar`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--jarjar-lockfile"], @@ -10523,7 +10523,7 @@ "display_args": ["--junit-lockfile="], "env_var": "PANTS_JUNIT_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.20.0.dev2/src/python/pants/jvm/test/junit.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=junit`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.20.0.dev2/src/python/pants/jvm/test/junit.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=junit`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--junit-lockfile"], @@ -10556,7 +10556,7 @@ "display_args": ["--[no-]junit-skip"], "env_var": "PANTS_JUNIT_SKIP", "fromfile": false, - "help": "If true, don't use JUnit when running `scie-pants-linux-x86_64 test`.", + "help": "If true, don't use JUnit when running `pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--junit-skip", "--no-junit-skip"], @@ -11209,7 +11209,7 @@ "display_args": ["--ktlint-lockfile="], "env_var": "PANTS_KTLINT_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.20.0.dev2/src/python/pants/backend/kotlin/lint/ktlint/ktlint.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=ktlint`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.20.0.dev2/src/python/pants/backend/kotlin/lint/ktlint/ktlint.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=ktlint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--ktlint-lockfile"], @@ -11242,7 +11242,7 @@ "display_args": ["--[no-]ktlint-skip"], "env_var": "PANTS_KTLINT_SKIP", "fromfile": false, - "help": "If true, don't use Ktlint when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Ktlint when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--ktlint-skip", "--no-ktlint-skip"], @@ -11407,7 +11407,7 @@ "display_args": ["--[no-]lint-skip-fixers"], "env_var": "PANTS_LINT_SKIP_FIXERS", "fromfile": false, - "help": "If true, skip running all fixers in check-only mode.\n\nFYI: when running `scie-pants-linux-x86_64 fix lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fix` when running `lint` where possible.", + "help": "If true, skip running all fixers in check-only mode.\n\nFYI: when running `pants fix lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fix` when running `lint` where possible.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--lint-skip-fixers", "--no-lint-skip-fixers"], @@ -11440,7 +11440,7 @@ "display_args": ["--[no-]lint-skip-formatters"], "env_var": "PANTS_LINT_SKIP_FORMATTERS", "fromfile": false, - "help": "If true, skip running all formatters in check-only mode.\n\nFYI: when running `scie-pants-linux-x86_64 fmt lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `lint` where possible.", + "help": "If true, skip running all formatters in check-only mode.\n\nFYI: when running `pants fmt lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `lint` where possible.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -12321,7 +12321,7 @@ "display_args": ["--[no-]mypy-skip"], "env_var": "PANTS_MYPY_SKIP", "fromfile": false, - "help": "If true, don't use MyPy when running `scie-pants-linux-x86_64 check`.", + "help": "If true, don't use MyPy when running `pants check`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--mypy-skip", "--no-mypy-skip"], @@ -12684,7 +12684,7 @@ ], "env_var": "PANTS_NODEJS_RESOLVES", "fromfile": false, - "help": "A mapping of names to lockfile paths used in your project.\n\nSpecifying a resolve name is optional. If unspecified, the default resolve name is calculated by taking the path from the source root to the directory containing the lockfile and replacing '/' with '.' in that path.\n\nExample: An npm lockfile located at `src/js/package/package-lock.json' will result in a resolve named `js.package`, assuming src/ is a source root.\n\nRun `scie-pants-linux-x86_64 generate-lockfiles` to generate the lockfile(s).", + "help": "A mapping of names to lockfile paths used in your project.\n\nSpecifying a resolve name is optional. If unspecified, the default resolve name is calculated by taking the path from the source root to the directory containing the lockfile and replacing '/' with '.' in that path.\n\nExample: An npm lockfile located at `src/js/package/package-lock.json' will result in a resolve named `js.package`, assuming src/ is a source root.\n\nRun `pants generate-lockfiles` to generate the lockfile(s).", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--nodejs-resolves"], @@ -12926,7 +12926,7 @@ "display_args": ["--[no-]openapi-format-skip"], "env_var": "PANTS_OPENAPI_FORMAT_SKIP", "fromfile": false, - "help": "If true, don't use openapi-format when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use openapi-format when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -13907,7 +13907,7 @@ "display_args": ["--[no-]preamble-skip"], "env_var": "PANTS_PREAMBLE_SKIP", "fromfile": false, - "help": "If true, don't use preamble when running `scie-pants-linux-x86_64 fmt`.", + "help": "If true, don't use preamble when running `pants fmt`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--preamble-skip", "--no-preamble-skip"], @@ -14069,7 +14069,7 @@ "display_args": ["--process-execution-graceful-shutdown-timeout="], "env_var": "PANTS_PROCESS_EXECUTION_GRACEFUL_SHUTDOWN_TIMEOUT", "fromfile": false, - "help": "The time in seconds to wait when gracefully shutting down an interactive process (such as one opened using `scie-pants-linux-x86_64 run`) before killing it.", + "help": "The time in seconds to wait when gracefully shutting down an interactive process (such as one opened using `pants run`) before killing it.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--process-execution-graceful-shutdown-timeout"], @@ -14350,7 +14350,7 @@ "display_args": ["--protobuf-java-grpc-lockfile="], "env_var": "PANTS_PROTOBUF_JAVA_GRPC_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.20.0.dev2/src/python/pants/backend/codegen/protobuf/java/grpc-java.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=protobuf-java-grpc`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.20.0.dev2/src/python/pants/backend/codegen/protobuf/java/grpc-java.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=protobuf-java-grpc`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--protobuf-java-grpc-lockfile"], @@ -14967,7 +14967,7 @@ "display_args": ["--[no-]pydocstyle-skip"], "env_var": "PANTS_PYDOCSTYLE_SKIP", "fromfile": false, - "help": "If true, don't use Pydocstyle when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Pydocstyle when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pydocstyle-skip", "--no-pydocstyle-skip"], @@ -15219,7 +15219,7 @@ "display_args": ["--[no-]pylint-skip"], "env_var": "PANTS_PYLINT_SKIP", "fromfile": false, - "help": "If true, don't use Pylint when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Pylint when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pylint-skip", "--no-pylint-skip"], @@ -15760,7 +15760,7 @@ "display_args": ["--[no-]pytest-skip"], "env_var": "PANTS_PYTEST_SKIP", "fromfile": false, - "help": "If true, don't use Pytest when running `scie-pants-linux-x86_64 test`.", + "help": "If true, don't use Pytest when running `pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pytest-skip", "--no-pytest-skip"], @@ -16440,7 +16440,7 @@ "display_args": ["--python-infer-init-files="], "env_var": "PANTS_PYTHON_INFER_INIT_FILES", "fromfile": false, - "help": "Infer a target's dependencies on any `__init__.py` files in the packages it is located in (recursively upward in the directory structure).\n\nEven if this is set to `never` or `content_only`, Pants will still always include any ancestor `__init__.py` files in the sandbox. Only, they will not be \"proper\" dependencies, e.g. they will not show up in `scie-pants-linux-x86_64 dependencies` and their own dependencies will not be used.\n\nBy default, Pants only adds a \"proper\" dependency if there is content in the `__init__.py` file. This makes sure that dependencies are added when likely necessary to build, while also avoiding adding unnecessary dependencies. While accurate, those unnecessary dependencies can complicate setting metadata like the `interpreter_constraints` and `resolve` fields.", + "help": "Infer a target's dependencies on any `__init__.py` files in the packages it is located in (recursively upward in the directory structure).\n\nEven if this is set to `never` or `content_only`, Pants will still always include any ancestor `__init__.py` files in the sandbox. Only, they will not be \"proper\" dependencies, e.g. they will not show up in `pants dependencies` and their own dependencies will not be used.\n\nBy default, Pants only adds a \"proper\" dependency if there is content in the `__init__.py` file. This makes sure that dependencies are added when likely necessary to build, while also avoiding adding unnecessary dependencies. While accurate, those unnecessary dependencies can complicate setting metadata like the `interpreter_constraints` and `resolve` fields.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--python-infer-init-files"], @@ -16577,7 +16577,7 @@ "display_args": ["--[no-]python-infer-use-rust-parser"], "env_var": "PANTS_PYTHON_INFER_USE_RUST_PARSER", "fromfile": false, - "help": "Use the new Rust-based, multithreaded, in-process dependency parser.\n\nPants 2.17 introduced a new paradigm to dependency parsing for Python by leveraging a Rust-based parser that's called in the same process as Pants itself, instead of farming out to one-python-process-per-file.\n\nAs a result of the switch, cold-cache performance improved by a factor of about 12x, while hot-cache had no difference. Additionally, Pants can now infer dependencies from Python scripts with syntax errors.\n\nAfter leaving this defaulted to disabled for a release cycle, Pants 2.18 started defaulting to enabling this.\n\nIf you think the new behaviour is causing problems, it is recommended that you run `scie-pants-linux-x86_64 peek :: > before.json` and then `scie-pants-linux-x86_64 --python-infer-use-rust-parser=False peek :: > after.json` and compare the two results.\n\nIf you think there is a bug and need to disable it, please file an issue: https://github.com/pantsbuild/pants/issues/new/choose.", + "help": "Use the new Rust-based, multithreaded, in-process dependency parser.\n\nPants 2.17 introduced a new paradigm to dependency parsing for Python by leveraging a Rust-based parser that's called in the same process as Pants itself, instead of farming out to one-python-process-per-file.\n\nAs a result of the switch, cold-cache performance improved by a factor of about 12x, while hot-cache had no difference. Additionally, Pants can now infer dependencies from Python scripts with syntax errors.\n\nAfter leaving this defaulted to disabled for a release cycle, Pants 2.18 started defaulting to enabling this.\n\nIf you think the new behaviour is causing problems, it is recommended that you run `pants peek :: > before.json` and then `pants --python-infer-use-rust-parser=False peek :: > after.json` and compare the two results.\n\nIf you think there is a bug and need to disable it, please file an issue: https://github.com/pantsbuild/pants/issues/new/choose.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -17126,7 +17126,7 @@ "env_var": "PANTS_PYTHON_REQUIREMENT_CONSTRAINTS", "fromfile": false, "help": "When resolving third-party requirements for your own code (vs. tools you run), use this constraints file to determine which versions to use.\n\nMutually exclusive with `[python].enable_resolves`, which we generally recommend as an improvement over constraints file.\n\nSee https://pip.pypa.io/en/stable/user_guide/#constraints-files for more information on the format of constraint files and how constraints are applied in Pex and pip.\n\nThis only applies when resolving user requirements, rather than tools you run like Black and Pytest. To constrain tools, set `[tool].lockfile`, e.g. `[black].lockfile`.", - "removal_hint": "We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.\n\nTo migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `scie-pants-linux-x86_64 generate-lockfiles`.", + "removal_hint": "We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.\n\nTo migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `pants generate-lockfiles`.", "removal_version": "3.0.0.dev0", "scoped_cmd_line_args": ["--python-requirement-constraints"], "target_field_name": null, @@ -17190,7 +17190,7 @@ ], "env_var": "PANTS_PYTHON_RESOLVES", "fromfile": false, - "help": "A mapping of logical names to lockfile paths used in your project.\n\nMany organizations only need a single resolve for their whole project, which is a good default and often the simplest thing to do. However, you may need multiple resolves, such as if you use two conflicting versions of a requirement in your repository.\n\nIf you only need a single resolve, run `scie-pants-linux-x86_64 generate-lockfiles` to generate the lockfile.\n\nIf you need multiple resolves:\n\n 1. Via this option, define multiple resolve names and their lockfile paths. The names should be meaningful to your repository, such as `data-science` or `pants-plugins`.\n 2. Set the default with `[python].default_resolve`.\n 3. Update your `python_requirement` targets with the `resolve` field to declare which resolve they should be available in. They default to `[python].default_resolve`, so you only need to update targets that you want in non-default resolves. (Often you'll set this via the `python_requirements` or `poetry_requirements` target generators)\n 4. Run `scie-pants-linux-x86_64 generate-lockfiles` to generate the lockfiles. If the results aren't what you'd expect, adjust the prior step.\n 5. Update any targets like `python_source` / `python_sources`, `python_test` / `python_tests`, and `pex_binary` which need to set a non-default resolve with the `resolve` field.\n\nIf a target can work with multiple resolves, you can either use the `parametrize` mechanism or manually create a distinct target per resolve. See https://www.pantsbuild.org/v2.20/docs/targets for information about `parametrize`.\n\nFor example:\n\n python_sources(\n resolve=parametrize(\"data-science\", \"web-app\"),\n )\n\nYou can name the lockfile paths what you would like; Pants does not expect a certain file extension or location.\n\nOnly applies if `[python].enable_resolves` is true.", + "help": "A mapping of logical names to lockfile paths used in your project.\n\nMany organizations only need a single resolve for their whole project, which is a good default and often the simplest thing to do. However, you may need multiple resolves, such as if you use two conflicting versions of a requirement in your repository.\n\nIf you only need a single resolve, run `pants generate-lockfiles` to generate the lockfile.\n\nIf you need multiple resolves:\n\n 1. Via this option, define multiple resolve names and their lockfile paths. The names should be meaningful to your repository, such as `data-science` or `pants-plugins`.\n 2. Set the default with `[python].default_resolve`.\n 3. Update your `python_requirement` targets with the `resolve` field to declare which resolve they should be available in. They default to `[python].default_resolve`, so you only need to update targets that you want in non-default resolves. (Often you'll set this via the `python_requirements` or `poetry_requirements` target generators)\n 4. Run `pants generate-lockfiles` to generate the lockfiles. If the results aren't what you'd expect, adjust the prior step.\n 5. Update any targets like `python_source` / `python_sources`, `python_test` / `python_tests`, and `pex_binary` which need to set a non-default resolve with the `resolve` field.\n\nIf a target can work with multiple resolves, you can either use the `parametrize` mechanism or manually create a distinct target per resolve. See https://www.pantsbuild.org/v2.20/docs/targets for information about `parametrize`.\n\nFor example:\n\n python_sources(\n resolve=parametrize(\"data-science\", \"web-app\"),\n )\n\nYou can name the lockfile paths what you would like; Pants does not expect a certain file extension or location.\n\nOnly applies if `[python].enable_resolves` is true.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--python-resolves"], @@ -17405,7 +17405,7 @@ "env_var": "PANTS_PYTHON_RESOLVE_ALL_CONSTRAINTS", "fromfile": false, "help": "(Only relevant when using `[python].requirement_constraints.`) If enabled, when resolving requirements, Pants will first resolve your entire constraints file as a single global resolve. Then, if the code uses a subset of your constraints file, Pants will extract the relevant requirements from that global resolve so that only what's actually needed gets used. If disabled, Pants will not use a global resolve and will resolve each subset of your requirements independently.\n\nUsually this option should be enabled because it can result in far fewer resolves.", - "removal_hint": "We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.\n\nTo migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `scie-pants-linux-x86_64 generate-lockfiles`.", + "removal_hint": "We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.\n\nTo migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `pants generate-lockfiles`.", "removal_version": "3.0.0.dev0", "scoped_cmd_line_args": [ "--python-resolve-all-constraints", @@ -17967,7 +17967,7 @@ "display_args": ["--[no-]pytype-skip"], "env_var": "PANTS_PYTYPE_SKIP", "fromfile": false, - "help": "If true, don't use Pytype when running `scie-pants-linux-x86_64 check`.", + "help": "If true, don't use Pytype when running `pants check`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pytype-skip", "--no-pytype-skip"], @@ -18190,7 +18190,7 @@ "display_args": ["--[no-]pyupgrade-skip"], "env_var": "PANTS_PYUPGRADE_SKIP", "fromfile": false, - "help": "If true, don't use pyupgrade when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use pyupgrade when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pyupgrade-skip", "--no-pyupgrade-skip"], @@ -18355,7 +18355,7 @@ "display_args": ["--[no-]regex-lint-skip"], "env_var": "PANTS_REGEX_LINT_SKIP", "fromfile": false, - "help": "If true, don't use regex-lint when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use regex-lint when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--regex-lint-skip", "--no-regex-lint-skip"], @@ -19605,7 +19605,7 @@ "display_args": ["--[no-]ruff-skip"], "env_var": "PANTS_RUFF_SKIP", "fromfile": false, - "help": "If true, don't use Ruff when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 fix` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Ruff when running `pants fmt` and `pants fix` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--ruff-skip", "--no-ruff-skip"], @@ -19902,7 +19902,7 @@ "display_args": ["--scalafmt-lockfile="], "env_var": "PANTS_SCALAFMT_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.20.0.dev2/src/python/pants/backend/scala/lint/scalafmt/scalafmt.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalafmt`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.20.0.dev2/src/python/pants/backend/scala/lint/scalafmt/scalafmt.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=scalafmt`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalafmt-lockfile"], @@ -19935,7 +19935,7 @@ "display_args": ["--[no-]scalafmt-skip"], "env_var": "PANTS_SCALAFMT_SKIP", "fromfile": false, - "help": "If true, don't use scalafmt when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use scalafmt when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalafmt-skip", "--no-scalafmt-skip"], @@ -20100,7 +20100,7 @@ "display_args": ["--scalapb-lockfile="], "env_var": "PANTS_SCALAPB_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.20.0.dev2/src/python/pants/backend/codegen/protobuf/scala/scalapbc.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalapb`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.20.0.dev2/src/python/pants/backend/codegen/protobuf/scala/scalapbc.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=scalapb`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalapb-lockfile"], @@ -20268,7 +20268,7 @@ "display_args": ["--scalatest-lockfile="], "env_var": "PANTS_SCALATEST_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.20.0.dev2/src/python/pants/backend/scala/subsystems/scalatest.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalatest`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.20.0.dev2/src/python/pants/backend/scala/subsystems/scalatest.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=scalatest`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalatest-lockfile"], @@ -20301,7 +20301,7 @@ "display_args": ["--[no-]scalatest-skip"], "env_var": "PANTS_SCALATEST_SKIP", "fromfile": false, - "help": "If true, don't use Scalatest when running `scie-pants-linux-x86_64 test`.", + "help": "If true, don't use Scalatest when running `pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalatest-skip", "--no-scalatest-skip"], @@ -21036,7 +21036,7 @@ "display_args": ["--[no-]semgrep-skip"], "env_var": "PANTS_SEMGREP_SKIP", "fromfile": false, - "help": "If true, don't use Semgrep when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Semgrep when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--semgrep-skip", "--no-semgrep-skip"], @@ -21512,7 +21512,7 @@ "display_args": ["--[no-]shellcheck-skip"], "env_var": "PANTS_SHELLCHECK_SKIP", "fromfile": false, - "help": "If true, don't use Shellcheck when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Shellcheck when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--shellcheck-skip", "--no-shellcheck-skip"], @@ -21801,7 +21801,7 @@ "display_args": ["--[no-]shell-test-skip"], "env_var": "PANTS_SHELL_TEST_SKIP", "fromfile": false, - "help": "If true, don't use Test with shell scripts when running `scie-pants-linux-x86_64 test`.", + "help": "If true, don't use Test with shell scripts when running `pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--shell-test-skip", "--no-shell-test-skip"], @@ -21954,7 +21954,7 @@ "display_args": ["--[no-]shfmt-skip"], "env_var": "PANTS_SHFMT_SKIP", "fromfile": false, - "help": "If true, don't use shfmt when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use shfmt when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--shfmt-skip", "--no-shfmt-skip"], @@ -22209,7 +22209,7 @@ "display_args": ["--[no-]shunit2-skip"], "env_var": "PANTS_SHUNIT2_SKIP", "fromfile": false, - "help": "If true, don't use shunit2 when running `scie-pants-linux-x86_64 test`.", + "help": "If true, don't use shunit2 when running `pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--shunit2-skip", "--no-shunit2-skip"], @@ -22524,7 +22524,7 @@ "display_args": ["--[no-]spectral-skip"], "env_var": "PANTS_SPECTRAL_SKIP", "fromfile": false, - "help": "If true, don't use Spectral when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Spectral when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--spectral-skip", "--no-spectral-skip"], @@ -23243,7 +23243,7 @@ "display_args": ["--[no-]terraform-fmt-skip"], "env_var": "PANTS_TERRAFORM_FMT_SKIP", "fromfile": false, - "help": "If true, don't use `terraform fmt` when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use `terraform fmt` when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -23379,7 +23379,7 @@ "display_args": ["--[no-]terraform-validate-skip"], "env_var": "PANTS_TERRAFORM_VALIDATE_SKIP", "fromfile": false, - "help": "If true, don't use `terraform validate` when running `scie-pants-linux-x86_64 check`.", + "help": "If true, don't use `terraform validate` when running `pants check`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -24265,7 +24265,7 @@ "display_args": ["--[no-]twine-skip"], "env_var": "PANTS_TWINE_SKIP", "fromfile": false, - "help": "If true, don't use Twine when running `scie-pants-linux-x86_64 publish`.", + "help": "If true, don't use Twine when running `pants publish`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--twine-skip", "--no-twine-skip"], @@ -24541,7 +24541,7 @@ "display_args": ["--pants-version="], "env_var": "PANTS_VERSION", "fromfile": false, - "help": "Use this Pants version. Note that Pants only uses this to verify that you are using the requested version, as Pants cannot dynamically change the version it is using once the program is already running.\n\nIf you use the `scie-pants-linux-x86_64` script from https://www.pantsbuild.org/v2.20/docs/installation, however, changing the value in your `pants.toml` will cause the new version to be installed and run automatically.\n\nRun `scie-pants-linux-x86_64 --version` to check what is being used.", + "help": "Use this Pants version. Note that Pants only uses this to verify that you are using the requested version, as Pants cannot dynamically change the version it is using once the program is already running.\n\nIf you use the `pants` script from https://www.pantsbuild.org/v2.20/docs/installation, however, changing the value in your `pants.toml` will cause the new version to be installed and run automatically.\n\nRun `pants --version` to check what is being used.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pants-version"], @@ -25003,7 +25003,7 @@ "display_args": ["--[no-]yamllint-skip"], "env_var": "PANTS_YAMLLINT_SKIP", "fromfile": false, - "help": "If true, don't use Yamllint when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Yamllint when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--yamllint-skip", "--no-yamllint-skip"], @@ -25290,7 +25290,7 @@ "display_args": ["--[no-]yapf-skip"], "env_var": "PANTS_YAPF_SKIP", "fromfile": false, - "help": "If true, don't use yapf when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use yapf when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--yapf-skip", "--no-yapf-skip"], @@ -64420,7 +64420,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -64428,7 +64428,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -64452,7 +64452,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -64460,7 +64460,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -64476,7 +64476,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -64492,7 +64492,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -64500,7 +64500,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -64516,7 +64516,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -64532,7 +64532,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -64540,7 +64540,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -64676,7 +64676,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -64684,7 +64684,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -64692,7 +64692,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -64700,7 +64700,7 @@ { "alias": "packages", "default": null, - "description": "Addresses to any targets that can be built with `scie-pants-linux-x86_64 package`, e.g. `[\"project:app\"]`.\n\nPants will build the assets as if you had run `scie-pants-linux-x86_64 package`. It will include the results in your archive using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or even another `archive`.", + "description": "Addresses to any targets that can be built with `pants package`, e.g. `[\"project:app\"]`.\n\nPants will build the assets as if you had run `pants package`. It will include the results in your archive using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `pants package`, e.g. a `pex_binary`, `python_awslambda`, or even another `archive`.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -64732,7 +64732,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -64740,7 +64740,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -64804,7 +64804,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -64812,7 +64812,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -64828,7 +64828,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -64836,7 +64836,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -64900,7 +64900,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -64908,7 +64908,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -65172,7 +65172,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -65180,7 +65180,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -65196,7 +65196,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -65284,7 +65284,7 @@ { "alias": "skip_push", "default": "False", - "description": "If true, do not push this image to registries when running `scie-pants-linux-x86_64 publish`.", + "description": "If true, do not push this image to registries when running `pants publish`.", "provider": "", "required": false, "type_hint": "bool" @@ -65356,7 +65356,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -65388,7 +65388,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -65396,7 +65396,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -65484,7 +65484,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -65492,7 +65492,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -65524,7 +65524,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -65532,7 +65532,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -65564,7 +65564,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -65572,7 +65572,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -65604,7 +65604,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -65612,7 +65612,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -65644,7 +65644,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -65652,7 +65652,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -65684,7 +65684,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -65692,7 +65692,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -65724,7 +65724,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -65732,7 +65732,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -65740,7 +65740,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -65764,7 +65764,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -65772,7 +65772,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -65796,7 +65796,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -65812,7 +65812,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -65820,7 +65820,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -65828,7 +65828,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -65924,7 +65924,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -65932,7 +65932,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -66004,7 +66004,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66012,7 +66012,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -66020,7 +66020,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66116,7 +66116,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66124,7 +66124,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -66132,7 +66132,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66156,7 +66156,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66164,7 +66164,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -66212,7 +66212,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66220,7 +66220,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -66244,7 +66244,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66252,7 +66252,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built directory tree should be located.\n\nIf undefined, this will use the path to the BUILD file, For example, `src/charts/mychart:tgt_name` would be `src.charts.mychart/tgt_name/`.\n\nRegardless of whether you use the default or set this field, the path will end with Helms's file format of `-.tgz`, where `chart_name` and `chart_version` are the values extracted from the Chart.yaml file. So, using the default for this field, the target `src/charts/mychart:tgt_name` might have a final path like `src.charts.mychart/tgt_name/mychart-0.1.0.tgz`.\n\nWhen running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built directory tree should be located.\n\nIf undefined, this will use the path to the BUILD file, For example, `src/charts/mychart:tgt_name` would be `src.charts.mychart/tgt_name/`.\n\nRegardless of whether you use the default or set this field, the path will end with Helms's file format of `-.tgz`, where `chart_name` and `chart_version` are the values extracted from the Chart.yaml file. So, using the default for this field, the target `src/charts/mychart:tgt_name` might have a final path like `src.charts.mychart/tgt_name/mychart-0.1.0.tgz`.\n\nWhen running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -66292,7 +66292,7 @@ { "alias": "skip_push", "default": "False", - "description": "If set to true, do not push this Helm chart to registries when running `scie-pants-linux-x86_64 publish`.", + "description": "If set to true, do not push this Helm chart to registries when running `pants publish`.", "provider": "", "required": false, "type_hint": "bool" @@ -66300,7 +66300,7 @@ { "alias": "skip_lint", "default": "False", - "description": "If set to true, do not run any linting in this Helm chart when running `scie-pants-linux-x86_64 lint`.", + "description": "If set to true, do not run any linting in this Helm chart when running `pants lint`.", "provider": "", "required": false, "type_hint": "bool" @@ -66316,7 +66316,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66324,7 +66324,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -66348,7 +66348,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66428,7 +66428,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66436,7 +66436,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -66452,7 +66452,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66484,7 +66484,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66492,7 +66492,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -66508,7 +66508,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66548,7 +66548,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66556,7 +66556,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -66564,7 +66564,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66628,7 +66628,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66636,7 +66636,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -66660,7 +66660,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66708,7 +66708,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66716,7 +66716,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -66748,7 +66748,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66788,7 +66788,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66796,7 +66796,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -66828,7 +66828,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66868,7 +66868,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66876,7 +66876,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -66972,7 +66972,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66980,7 +66980,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -67004,7 +67004,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -67028,7 +67028,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -67044,7 +67044,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -67052,7 +67052,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -67060,7 +67060,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -67132,7 +67132,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -67140,7 +67140,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -67156,7 +67156,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -67220,7 +67220,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -67228,7 +67228,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -67236,7 +67236,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -67308,7 +67308,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -67316,7 +67316,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -67340,7 +67340,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -67396,7 +67396,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -67404,7 +67404,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -67444,7 +67444,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -67452,7 +67452,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -67708,7 +67708,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -67716,7 +67716,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -67724,7 +67724,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -67756,7 +67756,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -67764,7 +67764,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -67788,7 +67788,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -67804,7 +67804,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -67812,7 +67812,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -67820,7 +67820,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -67852,7 +67852,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -67860,7 +67860,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -67884,7 +67884,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -67900,7 +67900,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -67908,7 +67908,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -67948,7 +67948,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -67956,7 +67956,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -68004,7 +68004,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -68140,7 +68140,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -68148,7 +68148,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -68180,7 +68180,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -68340,7 +68340,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -68356,7 +68356,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -68364,7 +68364,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -68420,7 +68420,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -68428,7 +68428,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -68484,7 +68484,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -68492,7 +68492,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -68500,7 +68500,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -68596,7 +68596,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -68604,7 +68604,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -68700,7 +68700,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -68716,7 +68716,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -68724,7 +68724,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -68732,7 +68732,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built directory tree should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:bin` would be `src.python.project/bin/`.\n\nRegardless of whether you use the default or set this field, the path will end with PyOxidizer's file format of `/{debug,release}/install/`, where `platform` is a Rust platform triplet like `aarch-64-apple-darwin` and `binary_name` is the value of the `binary_name` field. So, using the default for this field, the target `src/python/project:bin` might have a final path like `src.python.project/bin/aarch-64-apple-darwin/release/bin`.\n\nWhen running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built directory tree should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:bin` would be `src.python.project/bin/`.\n\nRegardless of whether you use the default or set this field, the path will end with PyOxidizer's file format of `/{debug,release}/install/`, where `platform` is a Rust platform triplet like `aarch-64-apple-darwin` and `binary_name` is the value of the `binary_name` field. So, using the default for this field, the target `src/python/project:bin` might have a final path like `src.python.project/bin/aarch-64-apple-darwin/release/bin`.\n\nWhen running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -68796,7 +68796,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -68804,7 +68804,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -68812,7 +68812,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -68860,7 +68860,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -68884,7 +68884,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -68892,7 +68892,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -68900,7 +68900,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -68956,7 +68956,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": true, "type_hint": "Iterable[str]" @@ -68972,7 +68972,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -68980,7 +68980,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -68996,7 +68996,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -69004,7 +69004,7 @@ { "alias": "entry_points", "default": null, - "description": "Any entry points, such as `console_scripts` and `gui_scripts`.\n\nSpecify as a nested dictionary, with a dictionary for each type of entry point, e.g. `console_scripts` vs. `gui_scripts`. Each dictionary maps the entry point name to either a setuptools entry point (`\"path.to.module:func\"`) or a Pants target address to a `pex_binary` target.\n\nExample:\n\n entry_points={\n \"console_scripts\": {\n \"my-script\": \"project.app:main\",\n \"another-script\": \"project/subdir:pex_binary_tgt\"\n }\n }\n\nNote that Pants will assume that any value that either starts with `:` or has `/` in it, is a target address to a `pex_binary` target. Otherwise, it will assume it's a setuptools entry point as defined by https://packaging.python.org/specifications/entry-points/#entry-points-specification. Use `//` as a prefix for target addresses if you need to disambiguate.\n\nPants will attempt to infer dependencies, which you can confirm by running:\n\n scie-pants-linux-x86_64 dependencies ", + "description": "Any entry points, such as `console_scripts` and `gui_scripts`.\n\nSpecify as a nested dictionary, with a dictionary for each type of entry point, e.g. `console_scripts` vs. `gui_scripts`. Each dictionary maps the entry point name to either a setuptools entry point (`\"path.to.module:func\"`) or a Pants target address to a `pex_binary` target.\n\nExample:\n\n entry_points={\n \"console_scripts\": {\n \"my-script\": \"project.app:main\",\n \"another-script\": \"project/subdir:pex_binary_tgt\"\n }\n }\n\nNote that Pants will assume that any value that either starts with `:` or has `/` in it, is a target address to a `pex_binary` target. Otherwise, it will assume it's a setuptools entry point as defined by https://packaging.python.org/specifications/entry-points/#entry-points-specification. Use `//` as a prefix for target addresses if you need to disambiguate.\n\nPants will attempt to infer dependencies, which you can confirm by running:\n\n pants dependencies ", "provider": "", "required": false, "type_hint": "Dict[str, Dict[str, str]] | None" @@ -69116,7 +69116,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -69124,7 +69124,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -69132,7 +69132,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -69140,7 +69140,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -69204,7 +69204,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -69212,7 +69212,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -69228,7 +69228,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -69276,7 +69276,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -69284,7 +69284,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -69340,7 +69340,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -69348,7 +69348,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -69364,7 +69364,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -69524,7 +69524,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -69532,7 +69532,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -69684,7 +69684,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -69716,7 +69716,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -69724,7 +69724,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -69732,7 +69732,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -69780,7 +69780,7 @@ { "alias": "runtime_package_dependencies", "default": null, - "description": "Addresses to targets that can be built with the `scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_aws_lambda_function`, or an `archive`.", + "description": "Addresses to targets that can be built with the `pants package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `pants package`, e.g. a `pex_binary`, `python_aws_lambda_function`, or an `archive`.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -69956,7 +69956,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -69964,7 +69964,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -70116,7 +70116,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -70140,7 +70140,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -70148,7 +70148,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -70292,7 +70292,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -70340,7 +70340,7 @@ { "alias": "runtime_package_dependencies", "default": null, - "description": "Addresses to targets that can be built with the `scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_aws_lambda_function`, or an `archive`.", + "description": "Addresses to targets that can be built with the `pants package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `pants package`, e.g. a `pex_binary`, `python_aws_lambda_function`, or an `archive`.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -70388,7 +70388,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -70396,7 +70396,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -70436,7 +70436,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -70444,7 +70444,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -70716,7 +70716,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -70724,7 +70724,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -70732,7 +70732,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -70756,7 +70756,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -70764,7 +70764,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -70788,7 +70788,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -70804,7 +70804,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -70812,7 +70812,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -70860,7 +70860,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -70868,7 +70868,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -70972,7 +70972,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -70980,7 +70980,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -70988,7 +70988,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -71060,7 +71060,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -71068,7 +71068,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -71100,7 +71100,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -71164,7 +71164,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -71172,7 +71172,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -71180,7 +71180,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -71252,7 +71252,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -71260,7 +71260,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -71292,7 +71292,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -71348,7 +71348,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -71356,7 +71356,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -71388,7 +71388,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -71396,7 +71396,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -71404,7 +71404,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -71476,7 +71476,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -71484,7 +71484,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -71508,7 +71508,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -71572,7 +71572,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -71580,7 +71580,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -71708,7 +71708,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -71716,7 +71716,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -71724,7 +71724,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -71764,7 +71764,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -71772,7 +71772,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -71812,7 +71812,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -71828,7 +71828,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -71836,7 +71836,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -71852,7 +71852,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -71884,7 +71884,7 @@ { "alias": "runtime_package_dependencies", "default": null, - "description": "Addresses to targets that can be built with the `scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_aws_lambda_function`, or an `archive`.", + "description": "Addresses to targets that can be built with the `pants package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `pants package`, e.g. a `pex_binary`, `python_aws_lambda_function`, or an `archive`.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -71916,7 +71916,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -71924,7 +71924,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -71964,7 +71964,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -71996,7 +71996,7 @@ { "alias": "runtime_package_dependencies", "default": null, - "description": "Addresses to targets that can be built with the `scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_aws_lambda_function`, or an `archive`.", + "description": "Addresses to targets that can be built with the `pants package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `pants package`, e.g. a `pex_binary`, `python_aws_lambda_function`, or an `archive`.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -72012,7 +72012,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -72020,7 +72020,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -72076,7 +72076,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -72084,7 +72084,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -72092,7 +72092,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -72108,7 +72108,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -72116,7 +72116,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -72124,7 +72124,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -72164,7 +72164,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -72172,7 +72172,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -72180,7 +72180,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -72204,7 +72204,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -72212,7 +72212,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -72220,7 +72220,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -72252,7 +72252,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -72260,7 +72260,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -72292,7 +72292,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -72308,7 +72308,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -72316,7 +72316,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -72685,7 +72685,7 @@ "display_args": ["--pants-version="], "env_var": "PANTS_VERSION", "fromfile": false, - "help": "Use this Pants version. Note that Pants only uses this to verify that you are using the requested version, as Pants cannot dynamically change the version it is using once the program is already running.\n\nIf you use the `scie-pants-linux-x86_64` script from https://www.pantsbuild.org/v2.20/docs/installation, however, changing the value in your `pants.toml` will cause the new version to be installed and run automatically.\n\nRun `scie-pants-linux-x86_64 --version` to check what is being used.", + "help": "Use this Pants version. Note that Pants only uses this to verify that you are using the requested version, as Pants cannot dynamically change the version it is using once the program is already running.\n\nIf you use the `pants` script from https://www.pantsbuild.org/v2.20/docs/installation, however, changing the value in your `pants.toml` will cause the new version to be installed and run automatically.\n\nRun `pants --version` to check what is being used.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pants-version"], @@ -72745,7 +72745,7 @@ { "details": "from env var PANTS_BIN_NAME", "rank": "ENVIRONMENT", - "value": "/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64" + "value": "/home/josh/work/scie-pants/dist/pants" } ] } @@ -73946,7 +73946,7 @@ ], "env_var": "PANTS_PROCESS_EXECUTION_GRACEFUL_SHUTDOWN_TIMEOUT", "fromfile": false, - "help": "The time in seconds to wait when gracefully shutting down an interactive process (such as one opened using `scie-pants-linux-x86_64 run`) before killing it.", + "help": "The time in seconds to wait when gracefully shutting down an interactive process (such as one opened using `pants run`) before killing it.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -75833,7 +75833,7 @@ "display_args": ["--[no-]add-trailing-comma-skip"], "env_var": "PANTS_ADD_TRAILING_COMMA_SKIP", "fromfile": false, - "help": "If true, don't use add-trailing-comma when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use add-trailing-comma when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -76229,7 +76229,7 @@ "display_args": ["--[no-]autoflake-skip"], "env_var": "PANTS_AUTOFLAKE_SKIP", "fromfile": false, - "help": "If true, don't use Autoflake when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Autoflake when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--autoflake-skip", "--no-autoflake-skip"], @@ -76459,7 +76459,7 @@ "display_args": ["--[no-]bandit-skip"], "env_var": "PANTS_BANDIT_SKIP", "fromfile": false, - "help": "If true, don't use Bandit when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Bandit when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--bandit-skip", "--no-bandit-skip"], @@ -76761,7 +76761,7 @@ "display_args": ["--[no-]black-skip"], "env_var": "PANTS_BLACK_SKIP", "fromfile": false, - "help": "If true, don't use Black when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Black when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--black-skip", "--no-black-skip"], @@ -77095,7 +77095,7 @@ "display_args": ["--[no-]buf-format-skip"], "env_var": "PANTS_BUF_FORMAT_SKIP", "fromfile": false, - "help": "If true, don't use Buf when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Buf when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--buf-format-skip", "--no-buf-format-skip"], @@ -77128,7 +77128,7 @@ "display_args": ["--[no-]buf-lint-skip"], "env_var": "PANTS_BUF_LINT_SKIP", "fromfile": false, - "help": "If true, don't use Buf when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Buf when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--buf-lint-skip", "--no-buf-lint-skip"], @@ -77242,7 +77242,7 @@ "display_args": ["--[no-]build-deprecations-fixer-skip"], "env_var": "PANTS_BUILD_DEPRECATIONS_FIXER_SKIP", "fromfile": false, - "help": "If true, don't use BUILD Deprecations Fixer when running `scie-pants-linux-x86_64 fix`.", + "help": "If true, don't use BUILD Deprecations Fixer when running `pants fix`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -77481,7 +77481,7 @@ "display_args": ["--[no-]buildifier-skip"], "env_var": "PANTS_BUILDIFIER_SKIP", "fromfile": false, - "help": "If true, don't use Buildifier when running `scie-pants-linux-x86_64 fmt`.", + "help": "If true, don't use Buildifier when running `pants fmt`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--buildifier-skip", "--no-buildifier-skip"], @@ -77738,7 +77738,7 @@ "display_args": ["--cli-alias=\"{'key1': val1, 'key2': val2, ...}\""], "env_var": "PANTS_CLI_ALIAS", "fromfile": false, - "help": "Register command line aliases.\n\nExample:\n\n [cli.alias]\n green = \"fmt lint check\"\n all-changed = \"--changed-since=HEAD --changed-dependents=transitive\"\n\nThis would allow you to run `scie-pants-linux-x86_64 green all-changed`, which is shorthand for `scie-pants-linux-x86_64 fmt lint check --changed-since=HEAD --changed-dependents=transitive`.\n\nNotice: this option must be placed in a config file (e.g. `pants.toml` or `pantsrc`) to have any effect.", + "help": "Register command line aliases.\n\nExample:\n\n [cli.alias]\n green = \"fmt lint check\"\n all-changed = \"--changed-since=HEAD --changed-dependents=transitive\"\n\nThis would allow you to run `pants green all-changed`, which is shorthand for `pants fmt lint check --changed-since=HEAD --changed-dependents=transitive`.\n\nNotice: this option must be placed in a config file (e.g. `pants.toml` or `pantsrc`) to have any effect.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--cli-alias"], @@ -79328,7 +79328,7 @@ "display_args": ["--[no-]docformatter-skip"], "env_var": "PANTS_DOCFORMATTER_SKIP", "fromfile": false, - "help": "If true, don't use docformatter when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use docformatter when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -79856,7 +79856,7 @@ ], "env_var": "PANTS_DOCKER_RUN_ARGS", "fromfile": false, - "help": "Additional arguments to use for `docker run` invocations.\n\nExample:\n\n $ scie-pants-linux-x86_64 run --docker-run-args=\"-p 127.0.0.1:80:8080/tcp --name demo\" src/example:image -- [image entrypoint args]\n\nTo provide the top-level options to the `docker` client, use `[docker].env_vars` to configure the [Environment variables](https://docs.docker.com/engine/reference/commandline/cli/#environment-variables) as appropriate.\n\nThe arguments for the image entrypoint may be passed on the command line after a double dash (`--`), or using the `--run-args` option.\n\nDefaults to `--interactive --tty` when stdout is connected to a terminal.", + "help": "Additional arguments to use for `docker run` invocations.\n\nExample:\n\n $ pants run --docker-run-args=\"-p 127.0.0.1:80:8080/tcp --name demo\" src/example:image -- [image entrypoint args]\n\nTo provide the top-level options to the `docker` client, use `[docker].env_vars` to configure the [Environment variables](https://docs.docker.com/engine/reference/commandline/cli/#environment-variables) as appropriate.\n\nThe arguments for the image entrypoint may be passed on the command line after a double dash (`--`), or using the `--run-args` option.\n\nDefaults to `--interactive --tty` when stdout is connected to a terminal.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--docker-run-args"], @@ -80742,7 +80742,7 @@ ], "env_var": "PANTS_EXPERIMENTAL_BSP_RUNNER_ENV_VARS", "fromfile": false, - "help": "Environment variables to set in the BSP runner script when setting up BSP in a repository. Entries are either strings in the form `ENV_VAR=value` to set an explicit value; or just `ENV_VAR` to copy the value from Pants' own environment when the experimental-bsp goal was run.\n\nThis option only takes effect when the BSP runner script is written. If the option changes, you must run `scie-pants-linux-x86_64 experimental-bsp` again to write a new copy of the BSP runner script.\n\nNote: The environment variables passed to the Pants BSP server will be those set for your IDE and not your shell. For example, on macOS, the IDE is generally launched by `launchd` after clicking on a Dock icon, and not from the shell. Thus, any environment variables set for your shell will likely not be seen by the Pants BSP server. At the very least, on macOS consider writing an explicit PATH into the BSP runner script via this option.", + "help": "Environment variables to set in the BSP runner script when setting up BSP in a repository. Entries are either strings in the form `ENV_VAR=value` to set an explicit value; or just `ENV_VAR` to copy the value from Pants' own environment when the experimental-bsp goal was run.\n\nThis option only takes effect when the BSP runner script is written. If the option changes, you must run `pants experimental-bsp` again to write a new copy of the BSP runner script.\n\nNote: The environment variables passed to the Pants BSP server will be those set for your IDE and not your shell. For example, on macOS, the IDE is generally launched by `launchd` after clicking on a Dock icon, and not from the shell. Thus, any environment variables set for your shell will likely not be seen by the Pants BSP server. At the very least, on macOS consider writing an explicit PATH into the BSP runner script via this option.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--experimental-bsp-runner-env-vars"], @@ -81489,7 +81489,7 @@ "display_args": ["--[no-]fix-skip-formatters"], "env_var": "PANTS_FIX_SKIP_FORMATTERS", "fromfile": false, - "help": "If true, skip running all formatters.\n\nFYI: when running `scie-pants-linux-x86_64 fix fmt ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `fix` where possible.", + "help": "If true, skip running all formatters.\n\nFYI: when running `pants fix fmt ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `fix` where possible.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -81799,7 +81799,7 @@ "display_args": ["--[no-]flake8-skip"], "env_var": "PANTS_FLAKE8_SKIP", "fromfile": false, - "help": "If true, don't use Flake8 when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Flake8 when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--flake8-skip", "--no-flake8-skip"], @@ -81953,7 +81953,7 @@ "display_args": ["--generate-lockfiles-custom-command="], "env_var": "PANTS_GENERATE_LOCKFILES_CUSTOM_COMMAND", "fromfile": false, - "help": "If set, lockfile headers will say to run this command to regenerate the lockfile, rather than running `scie-pants-linux-x86_64 generate-lockfiles --resolve=` like normal.", + "help": "If set, lockfile headers will say to run this command to regenerate the lockfile, rather than running `pants generate-lockfiles --resolve=` like normal.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--generate-lockfiles-custom-command"], @@ -81985,7 +81985,7 @@ ], "env_var": "PANTS_GENERATE_LOCKFILES_RESOLVE", "fromfile": false, - "help": "Only generate lockfiles for the specified resolve(s).\n\nResolves are the logical names for the different lockfiles used in your project. For your own code's dependencies, these come from backend-specific configuration such as `[python].resolves`. For tool lockfiles, resolve names are the options scope for that tool such as `black`, `pytest`, and `mypy-protobuf`.\n\nFor example, you can run `scie-pants-linux-x86_64 generate-lockfiles --resolve=black --resolve=pytest --resolve=data-science` to only generate lockfiles for those two tools and your resolve named `data-science`.\n\nIf you specify an invalid resolve name, like 'fake', Pants will output all possible values.\n\nIf not specified, Pants will generate lockfiles for all resolves.", + "help": "Only generate lockfiles for the specified resolve(s).\n\nResolves are the logical names for the different lockfiles used in your project. For your own code's dependencies, these come from backend-specific configuration such as `[python].resolves`. For tool lockfiles, resolve names are the options scope for that tool such as `black`, `pytest`, and `mypy-protobuf`.\n\nFor example, you can run `pants generate-lockfiles --resolve=black --resolve=pytest --resolve=data-science` to only generate lockfiles for those two tools and your resolve named `data-science`.\n\nIf you specify an invalid resolve name, like 'fake', Pants will output all possible values.\n\nIf not specified, Pants will generate lockfiles for all resolves.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--generate-lockfiles-resolve"], @@ -82373,7 +82373,7 @@ "display_args": ["--[no-]go-test-skip"], "env_var": "PANTS_GO_TEST_SKIP", "fromfile": false, - "help": "If true, don't use Go test binary when running `scie-pants-linux-x86_64 test`.", + "help": "If true, don't use Go test binary when running `pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--go-test-skip", "--no-go-test-skip"], @@ -82702,7 +82702,7 @@ "display_args": ["--[no-]gofmt-skip"], "env_var": "PANTS_GOFMT_SKIP", "fromfile": false, - "help": "If true, don't use gofmt when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use gofmt when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--gofmt-skip", "--no-gofmt-skip"], @@ -83489,7 +83489,7 @@ "display_args": ["--google-java-format-lockfile="], "env_var": "PANTS_GOOGLE_JAVA_FORMAT_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.20.0.dev2/src/python/pants/backend/java/lint/google_java_format/google_java_format.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=google-java-format`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.20.0.dev2/src/python/pants/backend/java/lint/google_java_format/google_java_format.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=google-java-format`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--google-java-format-lockfile"], @@ -83559,7 +83559,7 @@ "display_args": ["--[no-]google-java-format-skip"], "env_var": "PANTS_GOOGLE_JAVA_FORMAT_SKIP", "fromfile": false, - "help": "If true, don't use Google Java Format when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Google Java Format when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -84105,7 +84105,7 @@ "display_args": ["--[no-]hadolint-skip"], "env_var": "PANTS_HADOLINT_SKIP", "fromfile": false, - "help": "If true, don't use Hadolint when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Hadolint when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--hadolint-skip", "--no-hadolint-skip"], @@ -85167,7 +85167,7 @@ "display_args": ["--[no-]helm-unittest-skip"], "env_var": "PANTS_HELM_UNITTEST_SKIP", "fromfile": false, - "help": "If true, don't use helmunittestsubsystem when running `scie-pants-linux-x86_64 test`.", + "help": "If true, don't use helmunittestsubsystem when running `pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -85647,7 +85647,7 @@ "display_args": ["--[no-]isort-skip"], "env_var": "PANTS_ISORT_SKIP", "fromfile": false, - "help": "If true, don't use isort when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use isort when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--isort-skip", "--no-isort-skip"], @@ -85789,7 +85789,7 @@ "display_args": ["--jarjar-lockfile="], "env_var": "PANTS_JARJAR_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.20.0.dev2/src/python/pants/jvm/shading/jarjar.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=jarjar`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.20.0.dev2/src/python/pants/jvm/shading/jarjar.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=jarjar`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--jarjar-lockfile"], @@ -86209,7 +86209,7 @@ "display_args": ["--junit-lockfile="], "env_var": "PANTS_JUNIT_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.20.0.dev2/src/python/pants/jvm/test/junit.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=junit`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.20.0.dev2/src/python/pants/jvm/test/junit.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=junit`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--junit-lockfile"], @@ -86313,7 +86313,7 @@ "display_args": ["--[no-]junit-skip"], "env_var": "PANTS_JUNIT_SKIP", "fromfile": false, - "help": "If true, don't use JUnit when running `scie-pants-linux-x86_64 test`.", + "help": "If true, don't use JUnit when running `pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--junit-skip", "--no-junit-skip"], @@ -86966,7 +86966,7 @@ "display_args": ["--ktlint-lockfile="], "env_var": "PANTS_KTLINT_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.20.0.dev2/src/python/pants/backend/kotlin/lint/ktlint/ktlint.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=ktlint`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.20.0.dev2/src/python/pants/backend/kotlin/lint/ktlint/ktlint.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=ktlint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--ktlint-lockfile"], @@ -87034,7 +87034,7 @@ "display_args": ["--[no-]ktlint-skip"], "env_var": "PANTS_KTLINT_SKIP", "fromfile": false, - "help": "If true, don't use Ktlint when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Ktlint when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--ktlint-skip", "--no-ktlint-skip"], @@ -87145,7 +87145,7 @@ "display_args": ["--[no-]lint-skip-formatters"], "env_var": "PANTS_LINT_SKIP_FORMATTERS", "fromfile": false, - "help": "If true, skip running all formatters in check-only mode.\n\nFYI: when running `scie-pants-linux-x86_64 fmt lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `lint` where possible.", + "help": "If true, skip running all formatters in check-only mode.\n\nFYI: when running `pants fmt lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `lint` where possible.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -87184,7 +87184,7 @@ "display_args": ["--[no-]lint-skip-fixers"], "env_var": "PANTS_LINT_SKIP_FIXERS", "fromfile": false, - "help": "If true, skip running all fixers in check-only mode.\n\nFYI: when running `scie-pants-linux-x86_64 fix lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fix` when running `lint` where possible.", + "help": "If true, skip running all fixers in check-only mode.\n\nFYI: when running `pants fix lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fix` when running `lint` where possible.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -87596,7 +87596,7 @@ "display_args": ["--[no-]mypy-skip"], "env_var": "PANTS_MYPY_SKIP", "fromfile": false, - "help": "If true, don't use MyPy when running `scie-pants-linux-x86_64 check`.", + "help": "If true, don't use MyPy when running `pants check`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--mypy-skip", "--no-mypy-skip"], @@ -87939,7 +87939,7 @@ ], "env_var": "PANTS_NODEJS_RESOLVES", "fromfile": false, - "help": "A mapping of names to lockfile paths used in your project.\n\nSpecifying a resolve name is optional. If unspecified, the default resolve name is calculated by taking the path from the source root to the directory containing the lockfile and replacing '/' with '.' in that path.\n\nExample: An npm lockfile located at `src/js/package/package-lock.json' will result in a resolve named `js.package`, assuming src/ is a source root.\n\nRun `scie-pants-linux-x86_64 generate-lockfiles` to generate the lockfile(s).", + "help": "A mapping of names to lockfile paths used in your project.\n\nSpecifying a resolve name is optional. If unspecified, the default resolve name is calculated by taking the path from the source root to the directory containing the lockfile and replacing '/' with '.' in that path.\n\nExample: An npm lockfile located at `src/js/package/package-lock.json' will result in a resolve named `js.package`, assuming src/ is a source root.\n\nRun `pants generate-lockfiles` to generate the lockfile(s).", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--nodejs-resolves"], @@ -88357,7 +88357,7 @@ "display_args": ["--[no-]openapi-format-skip"], "env_var": "PANTS_OPENAPI_FORMAT_SKIP", "fromfile": false, - "help": "If true, don't use openapi-format when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use openapi-format when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -89054,7 +89054,7 @@ "display_args": ["--[no-]preamble-skip"], "env_var": "PANTS_PREAMBLE_SKIP", "fromfile": false, - "help": "If true, don't use preamble when running `scie-pants-linux-x86_64 fmt`.", + "help": "If true, don't use preamble when running `pants fmt`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--preamble-skip", "--no-preamble-skip"], @@ -89210,7 +89210,7 @@ "display_args": ["--protobuf-java-grpc-lockfile="], "env_var": "PANTS_PROTOBUF_JAVA_GRPC_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.20.0.dev2/src/python/pants/backend/codegen/protobuf/java/grpc-java.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=protobuf-java-grpc`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.20.0.dev2/src/python/pants/backend/codegen/protobuf/java/grpc-java.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=protobuf-java-grpc`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--protobuf-java-grpc-lockfile"], @@ -89914,7 +89914,7 @@ "display_args": ["--[no-]pydocstyle-skip"], "env_var": "PANTS_PYDOCSTYLE_SKIP", "fromfile": false, - "help": "If true, don't use Pydocstyle when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Pydocstyle when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pydocstyle-skip", "--no-pydocstyle-skip"], @@ -90218,7 +90218,7 @@ "display_args": ["--[no-]pylint-skip"], "env_var": "PANTS_PYLINT_SKIP", "fromfile": false, - "help": "If true, don't use Pylint when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Pylint when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pylint-skip", "--no-pylint-skip"], @@ -90824,7 +90824,7 @@ "display_args": ["--[no-]pytest-skip"], "env_var": "PANTS_PYTEST_SKIP", "fromfile": false, - "help": "If true, don't use Pytest when running `scie-pants-linux-x86_64 test`.", + "help": "If true, don't use Pytest when running `pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pytest-skip", "--no-pytest-skip"], @@ -91000,7 +91000,7 @@ ], "env_var": "PANTS_PYTHON_RESOLVES", "fromfile": false, - "help": "A mapping of logical names to lockfile paths used in your project.\n\nMany organizations only need a single resolve for their whole project, which is a good default and often the simplest thing to do. However, you may need multiple resolves, such as if you use two conflicting versions of a requirement in your repository.\n\nIf you only need a single resolve, run `scie-pants-linux-x86_64 generate-lockfiles` to generate the lockfile.\n\nIf you need multiple resolves:\n\n 1. Via this option, define multiple resolve names and their lockfile paths. The names should be meaningful to your repository, such as `data-science` or `pants-plugins`.\n 2. Set the default with `[python].default_resolve`.\n 3. Update your `python_requirement` targets with the `resolve` field to declare which resolve they should be available in. They default to `[python].default_resolve`, so you only need to update targets that you want in non-default resolves. (Often you'll set this via the `python_requirements` or `poetry_requirements` target generators)\n 4. Run `scie-pants-linux-x86_64 generate-lockfiles` to generate the lockfiles. If the results aren't what you'd expect, adjust the prior step.\n 5. Update any targets like `python_source` / `python_sources`, `python_test` / `python_tests`, and `pex_binary` which need to set a non-default resolve with the `resolve` field.\n\nIf a target can work with multiple resolves, you can either use the `parametrize` mechanism or manually create a distinct target per resolve. See https://www.pantsbuild.org/v2.20/docs/targets for information about `parametrize`.\n\nFor example:\n\n python_sources(\n resolve=parametrize(\"data-science\", \"web-app\"),\n )\n\nYou can name the lockfile paths what you would like; Pants does not expect a certain file extension or location.\n\nOnly applies if `[python].enable_resolves` is true.", + "help": "A mapping of logical names to lockfile paths used in your project.\n\nMany organizations only need a single resolve for their whole project, which is a good default and often the simplest thing to do. However, you may need multiple resolves, such as if you use two conflicting versions of a requirement in your repository.\n\nIf you only need a single resolve, run `pants generate-lockfiles` to generate the lockfile.\n\nIf you need multiple resolves:\n\n 1. Via this option, define multiple resolve names and their lockfile paths. The names should be meaningful to your repository, such as `data-science` or `pants-plugins`.\n 2. Set the default with `[python].default_resolve`.\n 3. Update your `python_requirement` targets with the `resolve` field to declare which resolve they should be available in. They default to `[python].default_resolve`, so you only need to update targets that you want in non-default resolves. (Often you'll set this via the `python_requirements` or `poetry_requirements` target generators)\n 4. Run `pants generate-lockfiles` to generate the lockfiles. If the results aren't what you'd expect, adjust the prior step.\n 5. Update any targets like `python_source` / `python_sources`, `python_test` / `python_tests`, and `pex_binary` which need to set a non-default resolve with the `resolve` field.\n\nIf a target can work with multiple resolves, you can either use the `parametrize` mechanism or manually create a distinct target per resolve. See https://www.pantsbuild.org/v2.20/docs/targets for information about `parametrize`.\n\nFor example:\n\n python_sources(\n resolve=parametrize(\"data-science\", \"web-app\"),\n )\n\nYou can name the lockfile paths what you would like; Pants does not expect a certain file extension or location.\n\nOnly applies if `[python].enable_resolves` is true.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--python-resolves"], @@ -91742,7 +91742,7 @@ "env_var": "PANTS_PYTHON_REQUIREMENT_CONSTRAINTS", "fromfile": false, "help": "When resolving third-party requirements for your own code (vs. tools you run), use this constraints file to determine which versions to use.\n\nMutually exclusive with `[python].enable_resolves`, which we generally recommend as an improvement over constraints file.\n\nSee https://pip.pypa.io/en/stable/user_guide/#constraints-files for more information on the format of constraint files and how constraints are applied in Pex and pip.\n\nThis only applies when resolving user requirements, rather than tools you run like Black and Pytest. To constrain tools, set `[tool].lockfile`, e.g. `[black].lockfile`.", - "removal_hint": "We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.\n\nTo migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `scie-pants-linux-x86_64 generate-lockfiles`.", + "removal_hint": "We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.\n\nTo migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `pants generate-lockfiles`.", "removal_version": "3.0.0.dev0", "scoped_cmd_line_args": ["--python-requirement-constraints"], "target_field_name": null, @@ -91770,7 +91770,7 @@ "env_var": "PANTS_PYTHON_RESOLVE_ALL_CONSTRAINTS", "fromfile": false, "help": "(Only relevant when using `[python].requirement_constraints.`) If enabled, when resolving requirements, Pants will first resolve your entire constraints file as a single global resolve. Then, if the code uses a subset of your constraints file, Pants will extract the relevant requirements from that global resolve so that only what's actually needed gets used. If disabled, Pants will not use a global resolve and will resolve each subset of your requirements independently.\n\nUsually this option should be enabled because it can result in far fewer resolves.", - "removal_hint": "We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.\n\nTo migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `scie-pants-linux-x86_64 generate-lockfiles`.", + "removal_hint": "We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.\n\nTo migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `pants generate-lockfiles`.", "removal_version": "3.0.0.dev0", "scoped_cmd_line_args": [ "--python-resolve-all-constraints", @@ -92200,7 +92200,7 @@ "display_args": ["--python-infer-init-files="], "env_var": "PANTS_PYTHON_INFER_INIT_FILES", "fromfile": false, - "help": "Infer a target's dependencies on any `__init__.py` files in the packages it is located in (recursively upward in the directory structure).\n\nEven if this is set to `never` or `content_only`, Pants will still always include any ancestor `__init__.py` files in the sandbox. Only, they will not be \"proper\" dependencies, e.g. they will not show up in `scie-pants-linux-x86_64 dependencies` and their own dependencies will not be used.\n\nBy default, Pants only adds a \"proper\" dependency if there is content in the `__init__.py` file. This makes sure that dependencies are added when likely necessary to build, while also avoiding adding unnecessary dependencies. While accurate, those unnecessary dependencies can complicate setting metadata like the `interpreter_constraints` and `resolve` fields.", + "help": "Infer a target's dependencies on any `__init__.py` files in the packages it is located in (recursively upward in the directory structure).\n\nEven if this is set to `never` or `content_only`, Pants will still always include any ancestor `__init__.py` files in the sandbox. Only, they will not be \"proper\" dependencies, e.g. they will not show up in `pants dependencies` and their own dependencies will not be used.\n\nBy default, Pants only adds a \"proper\" dependency if there is content in the `__init__.py` file. This makes sure that dependencies are added when likely necessary to build, while also avoiding adding unnecessary dependencies. While accurate, those unnecessary dependencies can complicate setting metadata like the `interpreter_constraints` and `resolve` fields.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--python-infer-init-files"], @@ -92412,7 +92412,7 @@ "display_args": ["--[no-]python-infer-use-rust-parser"], "env_var": "PANTS_PYTHON_INFER_USE_RUST_PARSER", "fromfile": false, - "help": "Use the new Rust-based, multithreaded, in-process dependency parser.\n\nPants 2.17 introduced a new paradigm to dependency parsing for Python by leveraging a Rust-based parser that's called in the same process as Pants itself, instead of farming out to one-python-process-per-file.\n\nAs a result of the switch, cold-cache performance improved by a factor of about 12x, while hot-cache had no difference. Additionally, Pants can now infer dependencies from Python scripts with syntax errors.\n\nAfter leaving this defaulted to disabled for a release cycle, Pants 2.18 started defaulting to enabling this.\n\nIf you think the new behaviour is causing problems, it is recommended that you run `scie-pants-linux-x86_64 peek :: > before.json` and then `scie-pants-linux-x86_64 --python-infer-use-rust-parser=False peek :: > after.json` and compare the two results.\n\nIf you think there is a bug and need to disable it, please file an issue: https://github.com/pantsbuild/pants/issues/new/choose.", + "help": "Use the new Rust-based, multithreaded, in-process dependency parser.\n\nPants 2.17 introduced a new paradigm to dependency parsing for Python by leveraging a Rust-based parser that's called in the same process as Pants itself, instead of farming out to one-python-process-per-file.\n\nAs a result of the switch, cold-cache performance improved by a factor of about 12x, while hot-cache had no difference. Additionally, Pants can now infer dependencies from Python scripts with syntax errors.\n\nAfter leaving this defaulted to disabled for a release cycle, Pants 2.18 started defaulting to enabling this.\n\nIf you think the new behaviour is causing problems, it is recommended that you run `pants peek :: > before.json` and then `pants --python-infer-use-rust-parser=False peek :: > after.json` and compare the two results.\n\nIf you think there is a bug and need to disable it, please file an issue: https://github.com/pantsbuild/pants/issues/new/choose.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -93025,7 +93025,7 @@ "display_args": ["--[no-]pytype-skip"], "env_var": "PANTS_PYTYPE_SKIP", "fromfile": false, - "help": "If true, don't use Pytype when running `scie-pants-linux-x86_64 check`.", + "help": "If true, don't use Pytype when running `pants check`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pytype-skip", "--no-pytype-skip"], @@ -93290,7 +93290,7 @@ "display_args": ["--[no-]pyupgrade-skip"], "env_var": "PANTS_PYUPGRADE_SKIP", "fromfile": false, - "help": "If true, don't use pyupgrade when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use pyupgrade when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pyupgrade-skip", "--no-pyupgrade-skip"], @@ -93369,7 +93369,7 @@ "display_args": ["--[no-]regex-lint-skip"], "env_var": "PANTS_REGEX_LINT_SKIP", "fromfile": false, - "help": "If true, don't use regex-lint when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use regex-lint when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--regex-lint-skip", "--no-regex-lint-skip"], @@ -93889,7 +93889,7 @@ "display_args": ["--[no-]ruff-skip"], "env_var": "PANTS_RUFF_SKIP", "fromfile": false, - "help": "If true, don't use Ruff when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 fix` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Ruff when running `pants fmt` and `pants fix` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--ruff-skip", "--no-ruff-skip"], @@ -94442,7 +94442,7 @@ "display_args": ["--scalafmt-lockfile="], "env_var": "PANTS_SCALAFMT_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.20.0.dev2/src/python/pants/backend/scala/lint/scalafmt/scalafmt.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalafmt`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.20.0.dev2/src/python/pants/backend/scala/lint/scalafmt/scalafmt.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=scalafmt`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalafmt-lockfile"], @@ -94512,7 +94512,7 @@ "display_args": ["--[no-]scalafmt-skip"], "env_var": "PANTS_SCALAFMT_SKIP", "fromfile": false, - "help": "If true, don't use scalafmt when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use scalafmt when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalafmt-skip", "--no-scalafmt-skip"], @@ -94621,7 +94621,7 @@ "display_args": ["--scalapb-lockfile="], "env_var": "PANTS_SCALAPB_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.20.0.dev2/src/python/pants/backend/codegen/protobuf/scala/scalapbc.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalapb`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.20.0.dev2/src/python/pants/backend/codegen/protobuf/scala/scalapbc.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=scalapb`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalapb-lockfile"], @@ -94798,7 +94798,7 @@ "display_args": ["--scalatest-lockfile="], "env_var": "PANTS_SCALATEST_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.20.0.dev2/src/python/pants/backend/scala/subsystems/scalatest.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalatest`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.20.0.dev2/src/python/pants/backend/scala/subsystems/scalatest.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=scalatest`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalatest-lockfile"], @@ -94904,7 +94904,7 @@ "display_args": ["--[no-]scalatest-skip"], "env_var": "PANTS_SCALATEST_SKIP", "fromfile": false, - "help": "If true, don't use Scalatest when running `scie-pants-linux-x86_64 test`.", + "help": "If true, don't use Scalatest when running `pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalatest-skip", "--no-scalatest-skip"], @@ -95413,7 +95413,7 @@ "display_args": ["--[no-]semgrep-skip"], "env_var": "PANTS_SEMGREP_SKIP", "fromfile": false, - "help": "If true, don't use Semgrep when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Semgrep when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--semgrep-skip", "--no-semgrep-skip"], @@ -95909,7 +95909,7 @@ "display_args": ["--[no-]shell-test-skip"], "env_var": "PANTS_SHELL_TEST_SKIP", "fromfile": false, - "help": "If true, don't use Test with shell scripts when running `scie-pants-linux-x86_64 test`.", + "help": "If true, don't use Test with shell scripts when running `pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--shell-test-skip", "--no-shell-test-skip"], @@ -96184,7 +96184,7 @@ "display_args": ["--[no-]shellcheck-skip"], "env_var": "PANTS_SHELLCHECK_SKIP", "fromfile": false, - "help": "If true, don't use Shellcheck when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Shellcheck when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--shellcheck-skip", "--no-shellcheck-skip"], @@ -96502,7 +96502,7 @@ "display_args": ["--[no-]shfmt-skip"], "env_var": "PANTS_SHFMT_SKIP", "fromfile": false, - "help": "If true, don't use shfmt when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use shfmt when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--shfmt-skip", "--no-shfmt-skip"], @@ -96756,7 +96756,7 @@ "display_args": ["--[no-]shunit2-skip"], "env_var": "PANTS_SHUNIT2_SKIP", "fromfile": false, - "help": "If true, don't use shunit2 when running `scie-pants-linux-x86_64 test`.", + "help": "If true, don't use shunit2 when running `pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--shunit2-skip", "--no-shunit2-skip"], @@ -96963,7 +96963,7 @@ "display_args": ["--[no-]spectral-skip"], "env_var": "PANTS_SPECTRAL_SKIP", "fromfile": false, - "help": "If true, don't use Spectral when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Spectral when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--spectral-skip", "--no-spectral-skip"], @@ -97478,7 +97478,7 @@ "display_args": ["--[no-]terraform-fmt-skip"], "env_var": "PANTS_TERRAFORM_FMT_SKIP", "fromfile": false, - "help": "If true, don't use `terraform fmt` when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use `terraform fmt` when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -97640,7 +97640,7 @@ "display_args": ["--[no-]terraform-validate-skip"], "env_var": "PANTS_TERRAFORM_VALIDATE_SKIP", "fromfile": false, - "help": "If true, don't use `terraform validate` when running `scie-pants-linux-x86_64 check`.", + "help": "If true, don't use `terraform validate` when running `pants check`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -98535,7 +98535,7 @@ "display_args": ["--[no-]twine-skip"], "env_var": "PANTS_TWINE_SKIP", "fromfile": false, - "help": "If true, don't use Twine when running `scie-pants-linux-x86_64 publish`.", + "help": "If true, don't use Twine when running `pants publish`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--twine-skip", "--no-twine-skip"], @@ -99151,7 +99151,7 @@ "display_args": ["--[no-]yamllint-skip"], "env_var": "PANTS_YAMLLINT_SKIP", "fromfile": false, - "help": "If true, don't use Yamllint when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Yamllint when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--yamllint-skip", "--no-yamllint-skip"], @@ -99420,7 +99420,7 @@ "display_args": ["--[no-]yapf-skip"], "env_var": "PANTS_YAPF_SKIP", "fromfile": false, - "help": "If true, don't use yapf when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use yapf when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--yapf-skip", "--no-yapf-skip"], diff --git a/docs/reference/subsystems/add-trailing-comma.mdx b/docs/reference/subsystems/add-trailing-comma.mdx index d5439dc45..204c8e4f7 100644 --- a/docs/reference/subsystems/add-trailing-comma.mdx +++ b/docs/reference/subsystems/add-trailing-comma.mdx @@ -25,7 +25,7 @@ Config section: `[add-trailing-comma]` default_repr={`False`} > -If true, don't use add-trailing-comma when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use add-trailing-comma when running `pants fmt` and `pants lint`. diff --git a/docs/reference/subsystems/autoflake.mdx b/docs/reference/subsystems/autoflake.mdx index 5cd053774..f18de108a 100644 --- a/docs/reference/subsystems/autoflake.mdx +++ b/docs/reference/subsystems/autoflake.mdx @@ -25,7 +25,7 @@ Config section: `[autoflake]` default_repr={`False`} > -If true, don't use Autoflake when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use Autoflake when running `pants fmt` and `pants lint`. diff --git a/docs/reference/subsystems/bandit.mdx b/docs/reference/subsystems/bandit.mdx index cbf12599f..0d3b93491 100644 --- a/docs/reference/subsystems/bandit.mdx +++ b/docs/reference/subsystems/bandit.mdx @@ -25,7 +25,7 @@ Config section: `[bandit]` default_repr={`False`} > -If true, don't use Bandit when running `scie-pants-linux-x86_64 lint`. +If true, don't use Bandit when running `pants lint`. diff --git a/docs/reference/subsystems/black.mdx b/docs/reference/subsystems/black.mdx index 56caeb230..f1c15cc37 100644 --- a/docs/reference/subsystems/black.mdx +++ b/docs/reference/subsystems/black.mdx @@ -25,7 +25,7 @@ Config section: `[black]` default_repr={`False`} > -If true, don't use Black when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use Black when running `pants fmt` and `pants lint`. diff --git a/docs/reference/subsystems/buf.mdx b/docs/reference/subsystems/buf.mdx index 4d287b5d7..e254f8d00 100644 --- a/docs/reference/subsystems/buf.mdx +++ b/docs/reference/subsystems/buf.mdx @@ -25,7 +25,7 @@ Config section: `[buf]` default_repr={`False`} > -If true, don't use Buf when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use Buf when running `pants fmt` and `pants lint`. @@ -37,7 +37,7 @@ If true, don't use Buf when running `scie-pants-linux-x86_64 fmt` and `scie default_repr={`False`} > -If true, don't use Buf when running `scie-pants-linux-x86_64 lint`. +If true, don't use Buf when running `pants lint`. diff --git a/docs/reference/subsystems/build-deprecations-fixer.mdx b/docs/reference/subsystems/build-deprecations-fixer.mdx index 7f54c6e7f..663dbb00f 100644 --- a/docs/reference/subsystems/build-deprecations-fixer.mdx +++ b/docs/reference/subsystems/build-deprecations-fixer.mdx @@ -30,7 +30,7 @@ Config section: `[build-deprecations-fixer]` -If true, don't use BUILD Deprecations Fixer when running `scie-pants-linux-x86_64 fix`. +If true, don't use BUILD Deprecations Fixer when running `pants fix`. diff --git a/docs/reference/subsystems/buildifier.mdx b/docs/reference/subsystems/buildifier.mdx index 2664479ba..92bcce11d 100644 --- a/docs/reference/subsystems/buildifier.mdx +++ b/docs/reference/subsystems/buildifier.mdx @@ -32,7 +32,7 @@ Config section: `[buildifier]` default_repr={`False`} > -If true, don't use Buildifier when running `scie-pants-linux-x86_64 fmt`. +If true, don't use Buildifier when running `pants fmt`. diff --git a/docs/reference/subsystems/cli.mdx b/docs/reference/subsystems/cli.mdx index c73472624..e471cf70f 100644 --- a/docs/reference/subsystems/cli.mdx +++ b/docs/reference/subsystems/cli.mdx @@ -35,7 +35,7 @@ green = "fmt lint check" all-changed = "--changed-since=HEAD --changed-dependents=transitive" ``` -This would allow you to run `scie-pants-linux-x86_64 green all-changed`, which is shorthand for `scie-pants-linux-x86_64 fmt lint check --changed-since=HEAD --changed-dependents=transitive`. +This would allow you to run `pants green all-changed`, which is shorthand for `pants fmt lint check --changed-since=HEAD --changed-dependents=transitive`. Notice: this option must be placed in a config file (e.g. `pants.toml` or `pantsrc`) to have any effect. diff --git a/docs/reference/subsystems/docformatter.mdx b/docs/reference/subsystems/docformatter.mdx index 46fd983b5..e549aef19 100644 --- a/docs/reference/subsystems/docformatter.mdx +++ b/docs/reference/subsystems/docformatter.mdx @@ -25,7 +25,7 @@ Config section: `[docformatter]` default_repr={`False`} > -If true, don't use docformatter when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use docformatter when running `pants fmt` and `pants lint`. diff --git a/docs/reference/subsystems/docker.mdx b/docs/reference/subsystems/docker.mdx index 481ccffbb..8a3d63bdc 100644 --- a/docs/reference/subsystems/docker.mdx +++ b/docs/reference/subsystems/docker.mdx @@ -214,7 +214,7 @@ Additional arguments to use for `docker run` invocations. Example: ``` -$ scie-pants-linux-x86_64 run --docker-run-args="-p 127.0.0.1:80:8080/tcp --name demo" src/example:image -- [image entrypoint args] +$ pants run --docker-run-args="-p 127.0.0.1:80:8080/tcp --name demo" src/example:image -- [image entrypoint args] ``` To provide the top-level options to the `docker` client, use `[docker].env_vars` to configure the [Environment variables](https://docs.docker.com/engine/reference/commandline/cli/#environment-variables) as appropriate. diff --git a/docs/reference/subsystems/flake8.mdx b/docs/reference/subsystems/flake8.mdx index 47dd5996d..3ddf4f575 100644 --- a/docs/reference/subsystems/flake8.mdx +++ b/docs/reference/subsystems/flake8.mdx @@ -25,7 +25,7 @@ Config section: `[flake8]` default_repr={`False`} > -If true, don't use Flake8 when running `scie-pants-linux-x86_64 lint`. +If true, don't use Flake8 when running `pants lint`. diff --git a/docs/reference/subsystems/go-test.mdx b/docs/reference/subsystems/go-test.mdx index f3fd9afb4..125a6e1b5 100644 --- a/docs/reference/subsystems/go-test.mdx +++ b/docs/reference/subsystems/go-test.mdx @@ -88,7 +88,7 @@ This option is similar to the `go test -coverpkg` option, but without support cu default_repr={`False`} > -If true, don't use Go test binary when running `scie-pants-linux-x86_64 test`. +If true, don't use Go test binary when running `pants test`. diff --git a/docs/reference/subsystems/gofmt.mdx b/docs/reference/subsystems/gofmt.mdx index 0e737213e..b4fad02eb 100644 --- a/docs/reference/subsystems/gofmt.mdx +++ b/docs/reference/subsystems/gofmt.mdx @@ -25,7 +25,7 @@ Config section: `[gofmt]` default_repr={`False`} > -If true, don't use gofmt when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use gofmt when running `pants fmt` and `pants lint`. diff --git a/docs/reference/subsystems/google-java-format.mdx b/docs/reference/subsystems/google-java-format.mdx index b1eae0033..6b4d462d0 100644 --- a/docs/reference/subsystems/google-java-format.mdx +++ b/docs/reference/subsystems/google-java-format.mdx @@ -25,7 +25,7 @@ Config section: `[google-java-format]` default_repr={`False`} > -If true, don't use Google Java Format when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use Google Java Format when running `pants fmt` and `pants lint`. @@ -79,7 +79,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.20.0.dev2/src/python/pants/backend/java/lint/google_java_format/google_java_format.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=google-java-format`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=google-java-format`. diff --git a/docs/reference/subsystems/hadolint.mdx b/docs/reference/subsystems/hadolint.mdx index 6360a7821..a3192a1b5 100644 --- a/docs/reference/subsystems/hadolint.mdx +++ b/docs/reference/subsystems/hadolint.mdx @@ -25,7 +25,7 @@ Config section: `[hadolint]` default_repr={`False`} > -If true, don't use Hadolint when running `scie-pants-linux-x86_64 lint`. +If true, don't use Hadolint when running `pants lint`. diff --git a/docs/reference/subsystems/helm-unittest.mdx b/docs/reference/subsystems/helm-unittest.mdx index ee89dd276..40bf8380e 100644 --- a/docs/reference/subsystems/helm-unittest.mdx +++ b/docs/reference/subsystems/helm-unittest.mdx @@ -50,7 +50,7 @@ Output type used for the test report. default_repr={`False`} > -If true, don't use helmunittestsubsystem when running `scie-pants-linux-x86_64 test`. +If true, don't use helmunittestsubsystem when running `pants test`. diff --git a/docs/reference/subsystems/isort.mdx b/docs/reference/subsystems/isort.mdx index 29fe19229..e4da2052d 100644 --- a/docs/reference/subsystems/isort.mdx +++ b/docs/reference/subsystems/isort.mdx @@ -25,7 +25,7 @@ Config section: `[isort]` default_repr={`False`} > -If true, don't use isort when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use isort when running `pants fmt` and `pants lint`. diff --git a/docs/reference/subsystems/jarjar.mdx b/docs/reference/subsystems/jarjar.mdx index 53c37d1c9..f90b733be 100644 --- a/docs/reference/subsystems/jarjar.mdx +++ b/docs/reference/subsystems/jarjar.mdx @@ -80,7 +80,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.20.0.dev2/src/python/pants/jvm/shading/jarjar.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=jarjar`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=jarjar`. diff --git a/docs/reference/subsystems/junit.mdx b/docs/reference/subsystems/junit.mdx index 0cc92109a..d3bc21a5c 100644 --- a/docs/reference/subsystems/junit.mdx +++ b/docs/reference/subsystems/junit.mdx @@ -37,7 +37,7 @@ Arguments to pass directly to JUnit, e.g. `--junit-args='--disable-ansi-colors'` default_repr={`False`} > -If true, don't use JUnit when running `scie-pants-linux-x86_64 test`. +If true, don't use JUnit when running `pants test`. @@ -79,7 +79,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.20.0.dev2/src/python/pants/jvm/test/junit.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=junit`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=junit`. diff --git a/docs/reference/subsystems/ktlint.mdx b/docs/reference/subsystems/ktlint.mdx index 1f755f40b..7258c62df 100644 --- a/docs/reference/subsystems/ktlint.mdx +++ b/docs/reference/subsystems/ktlint.mdx @@ -25,7 +25,7 @@ Config section: `[ktlint]` default_repr={`False`} > -If true, don't use Ktlint when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use Ktlint when running `pants fmt` and `pants lint`. @@ -67,7 +67,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.20.0.dev2/src/python/pants/backend/kotlin/lint/ktlint/ktlint.lock for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=ktlint`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=ktlint`. diff --git a/docs/reference/subsystems/mypy.mdx b/docs/reference/subsystems/mypy.mdx index 99ff0bb0b..4f24433ad 100644 --- a/docs/reference/subsystems/mypy.mdx +++ b/docs/reference/subsystems/mypy.mdx @@ -25,7 +25,7 @@ Config section: `[mypy]` default_repr={`False`} > -If true, don't use MyPy when running `scie-pants-linux-x86_64 check`. +If true, don't use MyPy when running `pants check`. diff --git a/docs/reference/subsystems/nodejs.mdx b/docs/reference/subsystems/nodejs.mdx index 5813e3a68..4920cf081 100644 --- a/docs/reference/subsystems/nodejs.mdx +++ b/docs/reference/subsystems/nodejs.mdx @@ -136,7 +136,7 @@ Specifying a resolve name is optional. If unspecified, the default resolve name Example: An npm lockfile located at `src/js/package/package-lock.json' will result in a resolve named `js.package`, assuming src/ is a source root. -Run `scie-pants-linux-x86_64 generate-lockfiles` to generate the lockfile(s). +Run `pants generate-lockfiles` to generate the lockfile(s). diff --git a/docs/reference/subsystems/openapi-format.mdx b/docs/reference/subsystems/openapi-format.mdx index c06a7671e..391e62527 100644 --- a/docs/reference/subsystems/openapi-format.mdx +++ b/docs/reference/subsystems/openapi-format.mdx @@ -25,7 +25,7 @@ Config section: `[openapi-format]` default_repr={`False`} > -If true, don't use openapi-format when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use openapi-format when running `pants fmt` and `pants lint`. diff --git a/docs/reference/subsystems/preamble.mdx b/docs/reference/subsystems/preamble.mdx index 8577e4ba8..27fb5eb3f 100644 --- a/docs/reference/subsystems/preamble.mdx +++ b/docs/reference/subsystems/preamble.mdx @@ -29,7 +29,7 @@ Config section: `[preamble]` default_repr={`False`} > -If true, don't use preamble when running `scie-pants-linux-x86_64 fmt`. +If true, don't use preamble when running `pants fmt`. diff --git a/docs/reference/subsystems/protobuf-java-grpc.mdx b/docs/reference/subsystems/protobuf-java-grpc.mdx index 06ec6f707..2eccf1354 100644 --- a/docs/reference/subsystems/protobuf-java-grpc.mdx +++ b/docs/reference/subsystems/protobuf-java-grpc.mdx @@ -57,7 +57,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.20.0.dev2/src/python/pants/backend/codegen/protobuf/java/grpc-java.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=protobuf-java-grpc`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=protobuf-java-grpc`. diff --git a/docs/reference/subsystems/pydocstyle.mdx b/docs/reference/subsystems/pydocstyle.mdx index 41e1853cf..06fde427c 100644 --- a/docs/reference/subsystems/pydocstyle.mdx +++ b/docs/reference/subsystems/pydocstyle.mdx @@ -25,7 +25,7 @@ Config section: `[pydocstyle]` default_repr={`False`} > -If true, don't use Pydocstyle when running `scie-pants-linux-x86_64 lint`. +If true, don't use Pydocstyle when running `pants lint`. diff --git a/docs/reference/subsystems/pylint.mdx b/docs/reference/subsystems/pylint.mdx index 80e241804..a4c5e6515 100644 --- a/docs/reference/subsystems/pylint.mdx +++ b/docs/reference/subsystems/pylint.mdx @@ -25,7 +25,7 @@ Config section: `[pylint]` default_repr={`False`} > -If true, don't use Pylint when running `scie-pants-linux-x86_64 lint`. +If true, don't use Pylint when running `pants lint`. diff --git a/docs/reference/subsystems/pytest.mdx b/docs/reference/subsystems/pytest.mdx index 25746bc79..392d7a617 100644 --- a/docs/reference/subsystems/pytest.mdx +++ b/docs/reference/subsystems/pytest.mdx @@ -51,7 +51,7 @@ NOTE: Enabling `pytest-xdist` can cause high-level scoped fixtures (for example default_repr={`False`} > -If true, don't use Pytest when running `scie-pants-linux-x86_64 test`. +If true, don't use Pytest when running `pants test`. diff --git a/docs/reference/subsystems/python-infer.mdx b/docs/reference/subsystems/python-infer.mdx index a26783884..21d901feb 100644 --- a/docs/reference/subsystems/python-infer.mdx +++ b/docs/reference/subsystems/python-infer.mdx @@ -94,7 +94,7 @@ If `--assets` is True, treat valid-looking strings with at least this many forwa Infer a target's dependencies on any `__init__.py` files in the packages it is located in (recursively upward in the directory structure). -Even if this is set to `never` or `content_only`, Pants will still always include any ancestor `__init__.py` files in the sandbox. Only, they will not be "proper" dependencies, e.g. they will not show up in `scie-pants-linux-x86_64 dependencies` and their own dependencies will not be used. +Even if this is set to `never` or `content_only`, Pants will still always include any ancestor `__init__.py` files in the sandbox. Only, they will not be "proper" dependencies, e.g. they will not show up in `pants dependencies` and their own dependencies will not be used. By default, Pants only adds a "proper" dependency if there is content in the `__init__.py` file. This makes sure that dependencies are added when likely necessary to build, while also avoiding adding unnecessary dependencies. While accurate, those unnecessary dependencies can complicate setting metadata like the `interpreter_constraints` and `resolve` fields. @@ -199,7 +199,7 @@ As a result of the switch, cold-cache performance improved by a factor of about After leaving this defaulted to disabled for a release cycle, Pants 2.18 started defaulting to enabling this. -If you think the new behaviour is causing problems, it is recommended that you run `scie-pants-linux-x86_64 peek :: > before.json` and then `scie-pants-linux-x86_64 --python-infer-use-rust-parser=False peek :: > after.json` and compare the two results. +If you think the new behaviour is causing problems, it is recommended that you run `pants peek :: > before.json` and then `pants --python-infer-use-rust-parser=False peek :: > after.json` and compare the two results. If you think there is a bug and need to disable it, please file an issue: https://github.com/pantsbuild/pants/issues/new/choose. diff --git a/docs/reference/subsystems/python.mdx b/docs/reference/subsystems/python.mdx index 24d5d8453..edfd87170 100644 --- a/docs/reference/subsystems/python.mdx +++ b/docs/reference/subsystems/python.mdx @@ -107,14 +107,14 @@ A mapping of logical names to lockfile paths used in your project. Many organizations only need a single resolve for their whole project, which is a good default and often the simplest thing to do. However, you may need multiple resolves, such as if you use two conflicting versions of a requirement in your repository. -If you only need a single resolve, run `scie-pants-linux-x86_64 generate-lockfiles` to generate the lockfile. +If you only need a single resolve, run `pants generate-lockfiles` to generate the lockfile. If you need multiple resolves: 1. Via this option, define multiple resolve names and their lockfile paths. The names should be meaningful to your repository, such as `data-science` or `pants-plugins`. 2. Set the default with `[python].default_resolve`. 3. Update your `python_requirement` targets with the `resolve` field to declare which resolve they should be available in. They default to `[python].default_resolve`, so you only need to update targets that you want in non-default resolves. (Often you'll set this via the `python_requirements` or `poetry_requirements` target generators) -4. Run `scie-pants-linux-x86_64 generate-lockfiles` to generate the lockfiles. If the results aren't what you'd expect, adjust the prior step. +4. Run `pants generate-lockfiles` to generate the lockfiles. If the results aren't what you'd expect, adjust the prior step. 5. Update any targets like `python_source` / `python_sources`, `python_test` / `python_tests`, and `pex_binary` which need to set a non-default resolve with the `resolve` field. If a target can work with multiple resolves, you can either use the `parametrize` mechanism or manually create a distinct target per resolve. See https://www.pantsbuild.org/v2.20/docs/targets for information about `parametrize`. @@ -417,7 +417,7 @@ If another targets address is in conflict with the created lockfile target, it w env_repr='PANTS_PYTHON_REQUIREMENT_CONSTRAINTS' default_repr={`None`} removal_version='3.0.0.dev0' - removal_hint={'We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.

To migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `scie-pants-linux-x86_64 generate-lockfiles`.'} + removal_hint={'We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.

To migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `pants generate-lockfiles`.'} > When resolving third-party requirements for your own code (vs. tools you run), use this constraints file to determine which versions to use. @@ -437,7 +437,7 @@ This only applies when resolving user requirements, rather than tools you run li env_repr='PANTS_PYTHON_RESOLVE_ALL_CONSTRAINTS' default_repr={`True`} removal_version='3.0.0.dev0' - removal_hint={'We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.

To migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `scie-pants-linux-x86_64 generate-lockfiles`.'} + removal_hint={'We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.

To migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `pants generate-lockfiles`.'} > (Only relevant when using `[python].requirement_constraints.`) If enabled, when resolving requirements, Pants will first resolve your entire constraints file as a single global resolve. Then, if the code uses a subset of your constraints file, Pants will extract the relevant requirements from that global resolve so that only what's actually needed gets used. If disabled, Pants will not use a global resolve and will resolve each subset of your requirements independently. diff --git a/docs/reference/subsystems/pytype.mdx b/docs/reference/subsystems/pytype.mdx index c838573e4..c1fb32356 100644 --- a/docs/reference/subsystems/pytype.mdx +++ b/docs/reference/subsystems/pytype.mdx @@ -25,7 +25,7 @@ Config section: `[pytype]` default_repr={`False`} > -If true, don't use Pytype when running `scie-pants-linux-x86_64 check`. +If true, don't use Pytype when running `pants check`. diff --git a/docs/reference/subsystems/pyupgrade.mdx b/docs/reference/subsystems/pyupgrade.mdx index 18f4e2239..df68afb4e 100644 --- a/docs/reference/subsystems/pyupgrade.mdx +++ b/docs/reference/subsystems/pyupgrade.mdx @@ -25,7 +25,7 @@ Config section: `[pyupgrade]` default_repr={`False`} > -If true, don't use pyupgrade when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use pyupgrade when running `pants fmt` and `pants lint`. diff --git a/docs/reference/subsystems/regex-lint.mdx b/docs/reference/subsystems/regex-lint.mdx index a919e6ff4..20d8d1542 100644 --- a/docs/reference/subsystems/regex-lint.mdx +++ b/docs/reference/subsystems/regex-lint.mdx @@ -29,7 +29,7 @@ Config section: `[regex-lint]` default_repr={`False`} > -If true, don't use regex-lint when running `scie-pants-linux-x86_64 lint`. +If true, don't use regex-lint when running `pants lint`. diff --git a/docs/reference/subsystems/ruff.mdx b/docs/reference/subsystems/ruff.mdx index 4e379db5d..11d451b86 100644 --- a/docs/reference/subsystems/ruff.mdx +++ b/docs/reference/subsystems/ruff.mdx @@ -25,7 +25,7 @@ Config section: `[ruff]` default_repr={`False`} > -If true, don't use Ruff when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 fix` and `scie-pants-linux-x86_64 lint`. +If true, don't use Ruff when running `pants fmt` and `pants fix` and `pants lint`. diff --git a/docs/reference/subsystems/scalafmt.mdx b/docs/reference/subsystems/scalafmt.mdx index 3c5f9e7f7..b4bc0496d 100644 --- a/docs/reference/subsystems/scalafmt.mdx +++ b/docs/reference/subsystems/scalafmt.mdx @@ -25,7 +25,7 @@ Config section: `[scalafmt]` default_repr={`False`} > -If true, don't use scalafmt when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use scalafmt when running `pants fmt` and `pants lint`. @@ -67,7 +67,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.20.0.dev2/src/python/pants/backend/scala/lint/scalafmt/scalafmt.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalafmt`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=scalafmt`. diff --git a/docs/reference/subsystems/scalapb.mdx b/docs/reference/subsystems/scalapb.mdx index 6ed68ab60..c949c5200 100644 --- a/docs/reference/subsystems/scalapb.mdx +++ b/docs/reference/subsystems/scalapb.mdx @@ -69,7 +69,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.20.0.dev2/src/python/pants/backend/codegen/protobuf/scala/scalapbc.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalapb`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=scalapb`. diff --git a/docs/reference/subsystems/scalatest.mdx b/docs/reference/subsystems/scalatest.mdx index 78bbb9d83..81bcbf4c6 100644 --- a/docs/reference/subsystems/scalatest.mdx +++ b/docs/reference/subsystems/scalatest.mdx @@ -39,7 +39,7 @@ See https://www.scalatest.org/user_guide/using_the_runner for supported argument default_repr={`False`} > -If true, don't use Scalatest when running `scie-pants-linux-x86_64 test`. +If true, don't use Scalatest when running `pants test`. @@ -81,7 +81,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.20.0.dev2/src/python/pants/backend/scala/subsystems/scalatest.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalatest`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=scalatest`. diff --git a/docs/reference/subsystems/semgrep.mdx b/docs/reference/subsystems/semgrep.mdx index 0cb4606ec..119aee81a 100644 --- a/docs/reference/subsystems/semgrep.mdx +++ b/docs/reference/subsystems/semgrep.mdx @@ -41,7 +41,7 @@ This includes --quiet by default to reduce the volume of output. default_repr={`False`} > -If true, don't use Semgrep when running `scie-pants-linux-x86_64 lint`. +If true, don't use Semgrep when running `pants lint`. diff --git a/docs/reference/subsystems/shell-test.mdx b/docs/reference/subsystems/shell-test.mdx index 3c748d702..1a371c907 100644 --- a/docs/reference/subsystems/shell-test.mdx +++ b/docs/reference/subsystems/shell-test.mdx @@ -25,7 +25,7 @@ Config section: `[shell-test]` default_repr={`False`} > -If true, don't use Test with shell scripts when running `scie-pants-linux-x86_64 test`. +If true, don't use Test with shell scripts when running `pants test`. diff --git a/docs/reference/subsystems/shellcheck.mdx b/docs/reference/subsystems/shellcheck.mdx index b1c83faf1..14e1d5e4b 100644 --- a/docs/reference/subsystems/shellcheck.mdx +++ b/docs/reference/subsystems/shellcheck.mdx @@ -25,7 +25,7 @@ Config section: `[shellcheck]` default_repr={`False`} > -If true, don't use Shellcheck when running `scie-pants-linux-x86_64 lint`. +If true, don't use Shellcheck when running `pants lint`. diff --git a/docs/reference/subsystems/shfmt.mdx b/docs/reference/subsystems/shfmt.mdx index 1592849e7..671298c7e 100644 --- a/docs/reference/subsystems/shfmt.mdx +++ b/docs/reference/subsystems/shfmt.mdx @@ -25,7 +25,7 @@ Config section: `[shfmt]` default_repr={`False`} > -If true, don't use shfmt when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use shfmt when running `pants fmt` and `pants lint`. diff --git a/docs/reference/subsystems/shunit2.mdx b/docs/reference/subsystems/shunit2.mdx index ac258a59a..63fa77a54 100644 --- a/docs/reference/subsystems/shunit2.mdx +++ b/docs/reference/subsystems/shunit2.mdx @@ -25,7 +25,7 @@ Config section: `[shunit2]` default_repr={`False`} > -If true, don't use shunit2 when running `scie-pants-linux-x86_64 test`. +If true, don't use shunit2 when running `pants test`. diff --git a/docs/reference/subsystems/spectral.mdx b/docs/reference/subsystems/spectral.mdx index 2f9588306..a5ab244bd 100644 --- a/docs/reference/subsystems/spectral.mdx +++ b/docs/reference/subsystems/spectral.mdx @@ -25,7 +25,7 @@ Config section: `[spectral]` default_repr={`False`} > -If true, don't use Spectral when running `scie-pants-linux-x86_64 lint`. +If true, don't use Spectral when running `pants lint`. diff --git a/docs/reference/subsystems/terraform-fmt.mdx b/docs/reference/subsystems/terraform-fmt.mdx index 968e542ad..c675ed16b 100644 --- a/docs/reference/subsystems/terraform-fmt.mdx +++ b/docs/reference/subsystems/terraform-fmt.mdx @@ -25,7 +25,7 @@ Config section: `[terraform-fmt]` default_repr={`False`} > -If true, don't use `terraform fmt` when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use `terraform fmt` when running `pants fmt` and `pants lint`. diff --git a/docs/reference/subsystems/terraform-validate.mdx b/docs/reference/subsystems/terraform-validate.mdx index a84bf5b6c..e7686bc2f 100644 --- a/docs/reference/subsystems/terraform-validate.mdx +++ b/docs/reference/subsystems/terraform-validate.mdx @@ -25,7 +25,7 @@ Config section: `[terraform-validate]` default_repr={`False`} > -If true, don't use `terraform validate` when running `scie-pants-linux-x86_64 check`. +If true, don't use `terraform validate` when running `pants check`. diff --git a/docs/reference/subsystems/twine.mdx b/docs/reference/subsystems/twine.mdx index 7bc9e8cb7..ef60148a7 100644 --- a/docs/reference/subsystems/twine.mdx +++ b/docs/reference/subsystems/twine.mdx @@ -25,7 +25,7 @@ Config section: `[twine]` default_repr={`False`} > -If true, don't use Twine when running `scie-pants-linux-x86_64 publish`. +If true, don't use Twine when running `pants publish`. diff --git a/docs/reference/subsystems/yamllint.mdx b/docs/reference/subsystems/yamllint.mdx index c505b81e0..6a9afc15c 100644 --- a/docs/reference/subsystems/yamllint.mdx +++ b/docs/reference/subsystems/yamllint.mdx @@ -61,7 +61,7 @@ Arguments to pass directly to Yamllint, e.g. `--yamllint-args='-d relaxed'`. default_repr={`False`} > -If true, don't use Yamllint when running `scie-pants-linux-x86_64 lint`. +If true, don't use Yamllint when running `pants lint`. diff --git a/docs/reference/subsystems/yapf.mdx b/docs/reference/subsystems/yapf.mdx index 24c855a22..5da3d7118 100644 --- a/docs/reference/subsystems/yapf.mdx +++ b/docs/reference/subsystems/yapf.mdx @@ -25,7 +25,7 @@ Config section: `[yapf]` default_repr={`False`} > -If true, don't use yapf when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use yapf when running `pants fmt` and `pants lint`. diff --git a/docs/reference/targets/adhoc_tool.mdx b/docs/reference/targets/adhoc_tool.mdx index 4378a4583..985e36caa 100644 --- a/docs/reference/targets/adhoc_tool.mdx +++ b/docs/reference/targets/adhoc_tool.mdx @@ -38,7 +38,7 @@ Backend: `pants.backend.experimental.adhoc` @@ -51,7 +51,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/docs/reference/targets/archive.mdx b/docs/reference/targets/archive.mdx index c0c9b9ef7..b3f69629d 100644 --- a/docs/reference/targets/archive.mdx +++ b/docs/reference/targets/archive.mdx @@ -24,7 +24,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -52,7 +52,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. @@ -65,11 +65,11 @@ Warning: setting this value risks naming collisions with other package targets y default_repr={`None`} > -Addresses to any targets that can be built with `scie-pants-linux-x86_64 package`, e.g. `["project:app"]`. +Addresses to any targets that can be built with `pants package`, e.g. `["project:app"]`. -Pants will build the assets as if you had run `scie-pants-linux-x86_64 package`. It will include the results in your archive using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). +Pants will build the assets as if you had run `pants package`. It will include the results in your archive using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). -You can include anything that can be built by `scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or even another `archive`. +You can include anything that can be built by `pants package`, e.g. a `pex_binary`, `python_awslambda`, or even another `archive`. diff --git a/docs/reference/targets/code_quality_tool.mdx b/docs/reference/targets/code_quality_tool.mdx index 00b126e6e..b9117e2d3 100644 --- a/docs/reference/targets/code_quality_tool.mdx +++ b/docs/reference/targets/code_quality_tool.mdx @@ -34,7 +34,7 @@ Backend: `pants.backend.experimental.adhoc` @@ -47,7 +47,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/docs/reference/targets/deploy_jar.mdx b/docs/reference/targets/deploy_jar.mdx index 95232ff3e..54b6c8aca 100644 --- a/docs/reference/targets/deploy_jar.mdx +++ b/docs/reference/targets/deploy_jar.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.experimental.java` @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -65,7 +65,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. @@ -80,9 +80,9 @@ Warning: setting this value risks naming collisions with other package targets y Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/docs/reference/targets/docker_environment.mdx b/docs/reference/targets/docker_environment.mdx index e17e07b7a..2b4b8d004 100644 --- a/docs/reference/targets/docker_environment.mdx +++ b/docs/reference/targets/docker_environment.mdx @@ -30,7 +30,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/docs/reference/targets/docker_image.mdx b/docs/reference/targets/docker_image.mdx index e7e3db7fb..e29ebb08d 100644 --- a/docs/reference/targets/docker_image.mdx +++ b/docs/reference/targets/docker_image.mdx @@ -39,7 +39,7 @@ Backend: `pants.backend.docker` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -52,7 +52,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -78,9 +78,9 @@ Use `[docker].build_args` to set default build args for all images. Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -291,7 +291,7 @@ See [Docker documentation](https://docs.docker.com/develop/develop-images/build_ default_repr={`False`} > -If true, do not push this image to registries when running `scie-pants-linux-x86_64 publish`. +If true, do not push this image to registries when running `pants publish`. @@ -450,7 +450,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. diff --git a/docs/reference/targets/experimental_test_shell_command.mdx b/docs/reference/targets/experimental_test_shell_command.mdx index d9cbf0eed..58eccc73a 100644 --- a/docs/reference/targets/experimental_test_shell_command.mdx +++ b/docs/reference/targets/experimental_test_shell_command.mdx @@ -39,7 +39,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -52,7 +52,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/docs/reference/targets/experimental_wrap_as_go_package_sources.mdx b/docs/reference/targets/experimental_wrap_as_go_package_sources.mdx index 76db3f1ba..0630639a4 100644 --- a/docs/reference/targets/experimental_wrap_as_go_package_sources.mdx +++ b/docs/reference/targets/experimental_wrap_as_go_package_sources.mdx @@ -30,7 +30,7 @@ Backend: `pants.backend.experimental.go` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/docs/reference/targets/experimental_wrap_as_java_sources.mdx b/docs/reference/targets/experimental_wrap_as_java_sources.mdx index 940029f9b..ff3e04681 100644 --- a/docs/reference/targets/experimental_wrap_as_java_sources.mdx +++ b/docs/reference/targets/experimental_wrap_as_java_sources.mdx @@ -30,7 +30,7 @@ Backend: `pants.backend.experimental.java` @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/docs/reference/targets/experimental_wrap_as_kotlin_sources.mdx b/docs/reference/targets/experimental_wrap_as_kotlin_sources.mdx index 003b6ad9a..bae3428a7 100644 --- a/docs/reference/targets/experimental_wrap_as_kotlin_sources.mdx +++ b/docs/reference/targets/experimental_wrap_as_kotlin_sources.mdx @@ -30,7 +30,7 @@ Backend: `pants.backend.experimental.kotlin` @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/docs/reference/targets/experimental_wrap_as_python_sources.mdx b/docs/reference/targets/experimental_wrap_as_python_sources.mdx index a341b498b..5751ec09f 100644 --- a/docs/reference/targets/experimental_wrap_as_python_sources.mdx +++ b/docs/reference/targets/experimental_wrap_as_python_sources.mdx @@ -30,7 +30,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/docs/reference/targets/experimental_wrap_as_resources.mdx b/docs/reference/targets/experimental_wrap_as_resources.mdx index bdb4704b5..7f60252a5 100644 --- a/docs/reference/targets/experimental_wrap_as_resources.mdx +++ b/docs/reference/targets/experimental_wrap_as_resources.mdx @@ -30,7 +30,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/docs/reference/targets/experimental_wrap_as_scala_sources.mdx b/docs/reference/targets/experimental_wrap_as_scala_sources.mdx index df94d3733..5548c481b 100644 --- a/docs/reference/targets/experimental_wrap_as_scala_sources.mdx +++ b/docs/reference/targets/experimental_wrap_as_scala_sources.mdx @@ -30,7 +30,7 @@ Backend: `pants.backend.experimental.scala` @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/docs/reference/targets/file.mdx b/docs/reference/targets/file.mdx index fd1707b30..a05115348 100644 --- a/docs/reference/targets/file.mdx +++ b/docs/reference/targets/file.mdx @@ -26,7 +26,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -52,9 +52,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/docs/reference/targets/files.mdx b/docs/reference/targets/files.mdx index c37719be6..c146b1da0 100644 --- a/docs/reference/targets/files.mdx +++ b/docs/reference/targets/files.mdx @@ -24,7 +24,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -94,9 +94,9 @@ You can specify the same file name in multiple keys, so long as you don't o Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/docs/reference/targets/go_binary.mdx b/docs/reference/targets/go_binary.mdx index 55a27e2dd..e1a85a7a6 100644 --- a/docs/reference/targets/go_binary.mdx +++ b/docs/reference/targets/go_binary.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.go` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -52,7 +52,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. diff --git a/docs/reference/targets/go_mod.mdx b/docs/reference/targets/go_mod.mdx index ea3d4e8ad..a0cfd6173 100644 --- a/docs/reference/targets/go_mod.mdx +++ b/docs/reference/targets/go_mod.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.go` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/docs/reference/targets/go_package.mdx b/docs/reference/targets/go_package.mdx index 81ec39528..7d5d93f4a 100644 --- a/docs/reference/targets/go_package.mdx +++ b/docs/reference/targets/go_package.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.experimental.go` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -52,9 +52,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/docs/reference/targets/go_third_party_package.mdx b/docs/reference/targets/go_third_party_package.mdx index 866008b6e..8de2a3727 100644 --- a/docs/reference/targets/go_third_party_package.mdx +++ b/docs/reference/targets/go_third_party_package.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.go` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -54,9 +54,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/docs/reference/targets/helm_artifact.mdx b/docs/reference/targets/helm_artifact.mdx index 0c94682be..df2c66974 100644 --- a/docs/reference/targets/helm_artifact.mdx +++ b/docs/reference/targets/helm_artifact.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.helm` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/docs/reference/targets/helm_chart.mdx b/docs/reference/targets/helm_chart.mdx index 93dd00ea4..1e3fb87e6 100644 --- a/docs/reference/targets/helm_chart.mdx +++ b/docs/reference/targets/helm_chart.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.helm` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -76,9 +76,9 @@ Example: `sources=['values.yaml', 'templates/*.yaml', '!values_ignore.yaml']` Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -99,7 +99,7 @@ If undefined, this will use the path to the BUILD file, For example, `src/charts Regardless of whether you use the default or set this field, the path will end with Helms's file format of `-.tgz`, where `chart_name` and `chart_version` are the values extracted from the Chart.yaml file. So, using the default for this field, the target `src/charts/mychart:tgt_name` might have a final path like `src.charts.mychart/tgt_name/mychart-0.1.0.tgz`. -When running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. @@ -183,7 +183,7 @@ The above example shows two valid `registry` options: using an alias to a config default_repr={`False`} > -If set to true, do not push this Helm chart to registries when running `scie-pants-linux-x86_64 publish`. +If set to true, do not push this Helm chart to registries when running `pants publish`. @@ -194,7 +194,7 @@ If set to true, do not push this Helm chart to registries when running `scie-pan default_repr={`False`} > -If set to true, do not run any linting in this Helm chart when running `scie-pants-linux-x86_64 lint`. +If set to true, do not run any linting in this Helm chart when running `pants lint`. diff --git a/docs/reference/targets/helm_deployment.mdx b/docs/reference/targets/helm_deployment.mdx index 4a5947ae3..09b923cdb 100644 --- a/docs/reference/targets/helm_deployment.mdx +++ b/docs/reference/targets/helm_deployment.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.helm` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -72,9 +72,9 @@ Name of the release used in the deployment. If not set, the target name will be Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/docs/reference/targets/helm_unittest_test.mdx b/docs/reference/targets/helm_unittest_test.mdx index 332229283..e43f1e44b 100644 --- a/docs/reference/targets/helm_unittest_test.mdx +++ b/docs/reference/targets/helm_unittest_test.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.helm` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -63,9 +63,9 @@ Path is relative to the BUILD file's directory, e.g. `source='example.ext'` Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/docs/reference/targets/helm_unittest_tests.mdx b/docs/reference/targets/helm_unittest_tests.mdx index c6a2be3ab..4dd970035 100644 --- a/docs/reference/targets/helm_unittest_tests.mdx +++ b/docs/reference/targets/helm_unittest_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.helm` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -65,9 +65,9 @@ Example: `sources=['*_test.yaml', '!ignore_test.yaml']` Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/docs/reference/targets/java_source.mdx b/docs/reference/targets/java_source.mdx index 533b79ec9..9505ad6f7 100644 --- a/docs/reference/targets/java_source.mdx +++ b/docs/reference/targets/java_source.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.java` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/docs/reference/targets/java_sources.mdx b/docs/reference/targets/java_sources.mdx index 8208f1f07..ebab174f6 100644 --- a/docs/reference/targets/java_sources.mdx +++ b/docs/reference/targets/java_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.java` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -77,9 +77,9 @@ If true, don't run Google Java Format on this target's code. Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/docs/reference/targets/junit_test.mdx b/docs/reference/targets/junit_test.mdx index faffbb4f3..3dd02181b 100644 --- a/docs/reference/targets/junit_test.mdx +++ b/docs/reference/targets/junit_test.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.java` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -91,9 +91,9 @@ This will be merged with and override values from `[test].extra_env_vars`. Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/docs/reference/targets/junit_tests.mdx b/docs/reference/targets/junit_tests.mdx index cb504f530..dfca8fad4 100644 --- a/docs/reference/targets/junit_tests.mdx +++ b/docs/reference/targets/junit_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.java` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -93,9 +93,9 @@ This will be merged with and override values from `[test].extra_env_vars`. Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/docs/reference/targets/jvm_artifact.mdx b/docs/reference/targets/jvm_artifact.mdx index c9a4f38ba..eac38295f 100644 --- a/docs/reference/targets/jvm_artifact.mdx +++ b/docs/reference/targets/jvm_artifact.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.java` @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/docs/reference/targets/jvm_war.mdx b/docs/reference/targets/jvm_war.mdx index 5c7f97a2c..393b9ec79 100644 --- a/docs/reference/targets/jvm_war.mdx +++ b/docs/reference/targets/jvm_war.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.java` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -74,9 +74,9 @@ A list of addresses to `resources` and `files` targets with content to place in Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -126,7 +126,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. diff --git a/docs/reference/targets/kotlin_junit_test.mdx b/docs/reference/targets/kotlin_junit_test.mdx index e91ac24c8..efeef9922 100644 --- a/docs/reference/targets/kotlin_junit_test.mdx +++ b/docs/reference/targets/kotlin_junit_test.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.kotlin` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/docs/reference/targets/kotlin_junit_tests.mdx b/docs/reference/targets/kotlin_junit_tests.mdx index 48b013de2..6d842668f 100644 --- a/docs/reference/targets/kotlin_junit_tests.mdx +++ b/docs/reference/targets/kotlin_junit_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.kotlin` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -65,9 +65,9 @@ Example: `sources=['*Test.kt', '!TestIgnore.kt']` Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/docs/reference/targets/kotlin_source.mdx b/docs/reference/targets/kotlin_source.mdx index 17536d730..9db4549a7 100644 --- a/docs/reference/targets/kotlin_source.mdx +++ b/docs/reference/targets/kotlin_source.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.kotlin` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/docs/reference/targets/kotlin_sources.mdx b/docs/reference/targets/kotlin_sources.mdx index 0ae58e365..c3a909512 100644 --- a/docs/reference/targets/kotlin_sources.mdx +++ b/docs/reference/targets/kotlin_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.kotlin` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -77,9 +77,9 @@ If true, don't run Ktlint on this target's code. Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/docs/reference/targets/kotlinc_plugin.mdx b/docs/reference/targets/kotlinc_plugin.mdx index c8ad9eb36..828754fa0 100644 --- a/docs/reference/targets/kotlinc_plugin.mdx +++ b/docs/reference/targets/kotlinc_plugin.mdx @@ -34,7 +34,7 @@ Backend: `pants.backend.experimental.kotlin` @@ -47,7 +47,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/docs/reference/targets/local_environment.mdx b/docs/reference/targets/local_environment.mdx index 9de60b057..a71909d0d 100644 --- a/docs/reference/targets/local_environment.mdx +++ b/docs/reference/targets/local_environment.mdx @@ -30,7 +30,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/docs/reference/targets/openapi_document.mdx b/docs/reference/targets/openapi_document.mdx index e0a105698..0d7877c89 100644 --- a/docs/reference/targets/openapi_document.mdx +++ b/docs/reference/targets/openapi_document.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.openapi` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/docs/reference/targets/openapi_documents.mdx b/docs/reference/targets/openapi_documents.mdx index def8107e5..2eedb6401 100644 --- a/docs/reference/targets/openapi_documents.mdx +++ b/docs/reference/targets/openapi_documents.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.openapi` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -77,9 +77,9 @@ If true, don't run `spectral lint` on this target's code. Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/docs/reference/targets/openapi_source.mdx b/docs/reference/targets/openapi_source.mdx index a8bfd09aa..1f766dce0 100644 --- a/docs/reference/targets/openapi_source.mdx +++ b/docs/reference/targets/openapi_source.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.openapi` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/docs/reference/targets/openapi_sources.mdx b/docs/reference/targets/openapi_sources.mdx index 61a4615e3..d658b28c0 100644 --- a/docs/reference/targets/openapi_sources.mdx +++ b/docs/reference/targets/openapi_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.openapi` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -77,9 +77,9 @@ If true, don't run `openapi-format` on this target's code. Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/docs/reference/targets/pants_requirements.mdx b/docs/reference/targets/pants_requirements.mdx index 2c8163933..83993d48e 100644 --- a/docs/reference/targets/pants_requirements.mdx +++ b/docs/reference/targets/pants_requirements.mdx @@ -30,7 +30,7 @@ Backend: `pants.backend.plugin_development` @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/docs/reference/targets/pex_binaries.mdx b/docs/reference/targets/pex_binaries.mdx index 10727b91a..e41f53e36 100644 --- a/docs/reference/targets/pex_binaries.mdx +++ b/docs/reference/targets/pex_binaries.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -147,9 +147,9 @@ All dependencies must share the same value for their `resolve` field. Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/docs/reference/targets/pex_binary.mdx b/docs/reference/targets/pex_binary.mdx index 274661522..90df8b650 100644 --- a/docs/reference/targets/pex_binary.mdx +++ b/docs/reference/targets/pex_binary.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -101,9 +101,9 @@ All dependencies must share the same value for their `resolve` field. Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -376,7 +376,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. diff --git a/docs/reference/targets/pipenv_requirements.mdx b/docs/reference/targets/pipenv_requirements.mdx index e06585179..f67f613c7 100644 --- a/docs/reference/targets/pipenv_requirements.mdx +++ b/docs/reference/targets/pipenv_requirements.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/docs/reference/targets/poetry_requirements.mdx b/docs/reference/targets/poetry_requirements.mdx index 82136c634..6edf88e02 100644 --- a/docs/reference/targets/poetry_requirements.mdx +++ b/docs/reference/targets/poetry_requirements.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/docs/reference/targets/protobuf_source.mdx b/docs/reference/targets/protobuf_source.mdx index b0d1734d7..2c0fd036d 100644 --- a/docs/reference/targets/protobuf_source.mdx +++ b/docs/reference/targets/protobuf_source.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.codegen.protobuf.python Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -54,9 +54,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/docs/reference/targets/protobuf_sources.mdx b/docs/reference/targets/protobuf_sources.mdx index a51ed1cb9..6562db0ee 100644 --- a/docs/reference/targets/protobuf_sources.mdx +++ b/docs/reference/targets/protobuf_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.codegen.protobuf.python Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -218,9 +218,9 @@ Whether to generate gRPC code or not. Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/docs/reference/targets/pyoxidizer_binary.mdx b/docs/reference/targets/pyoxidizer_binary.mdx index db36b8986..c4d81128b 100644 --- a/docs/reference/targets/pyoxidizer_binary.mdx +++ b/docs/reference/targets/pyoxidizer_binary.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.python.pac Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -58,7 +58,7 @@ If undefined, this will use the path to the BUILD file, followed by the target n Regardless of whether you use the default or set this field, the path will end with PyOxidizer's file format of `/{debug,release}/install/`, where `platform` is a Rust platform triplet like `aarch-64-apple-darwin` and `binary_name` is the value of the `binary_name` field. So, using the default for this field, the target `src/python/project:bin` might have a final path like `src.python.project/bin/aarch-64-apple-darwin/release/bin`. -When running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. diff --git a/docs/reference/targets/python_aws_lambda_function.mdx b/docs/reference/targets/python_aws_lambda_function.mdx index 8466d43a6..d6585c5c1 100644 --- a/docs/reference/targets/python_aws_lambda_function.mdx +++ b/docs/reference/targets/python_aws_lambda_function.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.awslambda.python` @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -54,7 +54,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. @@ -144,9 +144,9 @@ You can specify multiple valid environments by using `parametrize`. If `__local_ Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/docs/reference/targets/python_aws_lambda_layer.mdx b/docs/reference/targets/python_aws_lambda_layer.mdx index 12a3b5f51..3d424fed7 100644 --- a/docs/reference/targets/python_aws_lambda_layer.mdx +++ b/docs/reference/targets/python_aws_lambda_layer.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.awslambda.python` @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -54,7 +54,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. @@ -155,9 +155,9 @@ Whether to resolve first party sources and include them in the AWS Lambda artifa Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/docs/reference/targets/python_distribution.mdx b/docs/reference/targets/python_distribution.mdx index b4d2a52c2..a9531a02c 100644 --- a/docs/reference/targets/python_distribution.mdx +++ b/docs/reference/targets/python_distribution.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -71,9 +71,9 @@ See https://www.pantsbuild.org/v2.20/docs/python-interpreter-compatibility for h Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -108,7 +108,7 @@ Note that Pants will assume that any value that either starts with `:` or has `/ Pants will attempt to infer dependencies, which you can confirm by running: ``` -scie-pants-linux-x86_64 dependencies +pants dependencies ``` diff --git a/docs/reference/targets/python_google_cloud_function.mdx b/docs/reference/targets/python_google_cloud_function.mdx index 8beadaeda..0b127347b 100644 --- a/docs/reference/targets/python_google_cloud_function.mdx +++ b/docs/reference/targets/python_google_cloud_function.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.google_cloud_function.p Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -54,7 +54,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. @@ -69,9 +69,9 @@ Warning: setting this value risks naming collisions with other package targets y Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/docs/reference/targets/python_requirement.mdx b/docs/reference/targets/python_requirement.mdx index 180f517c3..65b89a011 100644 --- a/docs/reference/targets/python_requirement.mdx +++ b/docs/reference/targets/python_requirement.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -69,9 +69,9 @@ If the requirement depends on some other requirement to work, such as needing `s Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/docs/reference/targets/python_requirements.mdx b/docs/reference/targets/python_requirements.mdx index 621be0c31..b4078a301 100644 --- a/docs/reference/targets/python_requirements.mdx +++ b/docs/reference/targets/python_requirements.mdx @@ -30,7 +30,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/docs/reference/targets/python_source.mdx b/docs/reference/targets/python_source.mdx index d321ee678..d9dde8c7a 100644 --- a/docs/reference/targets/python_source.mdx +++ b/docs/reference/targets/python_source.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -69,9 +69,9 @@ See https://www.pantsbuild.org/v2.20/docs/python-interpreter-compatibility for h Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/docs/reference/targets/python_sources.mdx b/docs/reference/targets/python_sources.mdx index b0f3e819e..e1f280449 100644 --- a/docs/reference/targets/python_sources.mdx +++ b/docs/reference/targets/python_sources.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -300,9 +300,9 @@ The latter mode is similar to creating, activating, and using a virtual environm Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/docs/reference/targets/python_test.mdx b/docs/reference/targets/python_test.mdx index a9768fb34..2f0a1bfd8 100644 --- a/docs/reference/targets/python_test.mdx +++ b/docs/reference/targets/python_test.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -54,9 +54,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -161,11 +161,11 @@ When tests with the same `batch_compatibility_tag` have incompatibilities in som default_repr={`None`} > -Addresses to targets that can be built with the `scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run. +Addresses to targets that can be built with the `pants package` goal and whose resulting artifacts should be included in the test run. -Pants will build the artifacts as if you had run `scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). +Pants will build the artifacts as if you had run `pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). -You can include anything that can be built by `scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_aws_lambda_function`, or an `archive`. +You can include anything that can be built by `pants package`, e.g. a `pex_binary`, `python_aws_lambda_function`, or an `archive`. diff --git a/docs/reference/targets/python_test_utils.mdx b/docs/reference/targets/python_test_utils.mdx index 43847563b..b1b25cb70 100644 --- a/docs/reference/targets/python_test_utils.mdx +++ b/docs/reference/targets/python_test_utils.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -300,9 +300,9 @@ The latter mode is similar to creating, activating, and using a virtual environm Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/docs/reference/targets/python_tests.mdx b/docs/reference/targets/python_tests.mdx index 78e1e9261..58692a1d2 100644 --- a/docs/reference/targets/python_tests.mdx +++ b/docs/reference/targets/python_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -282,9 +282,9 @@ If true, don't run Black on this target's code. Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -389,11 +389,11 @@ When tests with the same `batch_compatibility_tag` have incompatibilities in som default_repr={`None`} > -Addresses to targets that can be built with the `scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run. +Addresses to targets that can be built with the `pants package` goal and whose resulting artifacts should be included in the test run. -Pants will build the artifacts as if you had run `scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). +Pants will build the artifacts as if you had run `pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). -You can include anything that can be built by `scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_aws_lambda_function`, or an `archive`. +You can include anything that can be built by `pants package`, e.g. a `pex_binary`, `python_aws_lambda_function`, or an `archive`. diff --git a/docs/reference/targets/relocated_files.mdx b/docs/reference/targets/relocated_files.mdx index 62f3ec4e4..346339e69 100644 --- a/docs/reference/targets/relocated_files.mdx +++ b/docs/reference/targets/relocated_files.mdx @@ -61,7 +61,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -74,7 +74,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/docs/reference/targets/remote_environment.mdx b/docs/reference/targets/remote_environment.mdx index 2ccf086f5..5bb6b9a01 100644 --- a/docs/reference/targets/remote_environment.mdx +++ b/docs/reference/targets/remote_environment.mdx @@ -32,7 +32,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -45,7 +45,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/docs/reference/targets/resource.mdx b/docs/reference/targets/resource.mdx index 3d18ff066..df41a0aee 100644 --- a/docs/reference/targets/resource.mdx +++ b/docs/reference/targets/resource.mdx @@ -26,7 +26,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -52,9 +52,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/docs/reference/targets/resources.mdx b/docs/reference/targets/resources.mdx index 141647d04..0713753e0 100644 --- a/docs/reference/targets/resources.mdx +++ b/docs/reference/targets/resources.mdx @@ -24,7 +24,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -94,9 +94,9 @@ You can specify the same file name in multiple keys, so long as you don't o Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/docs/reference/targets/run_shell_command.mdx b/docs/reference/targets/run_shell_command.mdx index 96824cfac..bf8dfe79c 100644 --- a/docs/reference/targets/run_shell_command.mdx +++ b/docs/reference/targets/run_shell_command.mdx @@ -37,7 +37,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -50,7 +50,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/docs/reference/targets/scala_artifact.mdx b/docs/reference/targets/scala_artifact.mdx index 2e5f0de12..448da20e3 100644 --- a/docs/reference/targets/scala_artifact.mdx +++ b/docs/reference/targets/scala_artifact.mdx @@ -30,7 +30,7 @@ Backend: `pants.backend.experimental.scala` @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/docs/reference/targets/scala_junit_test.mdx b/docs/reference/targets/scala_junit_test.mdx index d3c57a038..f4b9e518c 100644 --- a/docs/reference/targets/scala_junit_test.mdx +++ b/docs/reference/targets/scala_junit_test.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.scala` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/docs/reference/targets/scala_junit_tests.mdx b/docs/reference/targets/scala_junit_tests.mdx index 7f0421ff7..470e49385 100644 --- a/docs/reference/targets/scala_junit_tests.mdx +++ b/docs/reference/targets/scala_junit_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.scala` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -107,9 +107,9 @@ If unset, will default to `[test].timeout_default`; if that option is also unset Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/docs/reference/targets/scala_source.mdx b/docs/reference/targets/scala_source.mdx index 40d264148..302035e13 100644 --- a/docs/reference/targets/scala_source.mdx +++ b/docs/reference/targets/scala_source.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.scala` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/docs/reference/targets/scala_sources.mdx b/docs/reference/targets/scala_sources.mdx index 3839dfb4e..11e330d11 100644 --- a/docs/reference/targets/scala_sources.mdx +++ b/docs/reference/targets/scala_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.scala` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -106,9 +106,9 @@ If true, don't run `scalafmt` on this target's code. Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/docs/reference/targets/scalac_plugin.mdx b/docs/reference/targets/scalac_plugin.mdx index 2e9c51213..5debfdf3a 100644 --- a/docs/reference/targets/scalac_plugin.mdx +++ b/docs/reference/targets/scalac_plugin.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.scala` @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/docs/reference/targets/scalatest_test.mdx b/docs/reference/targets/scalatest_test.mdx index f626603b4..c53d700d0 100644 --- a/docs/reference/targets/scalatest_test.mdx +++ b/docs/reference/targets/scalatest_test.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.scala` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/docs/reference/targets/scalatest_tests.mdx b/docs/reference/targets/scalatest_tests.mdx index 926836bd8..2bff84a27 100644 --- a/docs/reference/targets/scalatest_tests.mdx +++ b/docs/reference/targets/scalatest_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.scala` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -94,9 +94,9 @@ You can specify the same file name in multiple keys, so long as you don't o Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/docs/reference/targets/shell_command.mdx b/docs/reference/targets/shell_command.mdx index 56ea4bee6..1e096b900 100644 --- a/docs/reference/targets/shell_command.mdx +++ b/docs/reference/targets/shell_command.mdx @@ -42,7 +42,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -55,7 +55,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/docs/reference/targets/shell_source.mdx b/docs/reference/targets/shell_source.mdx index 9af19f3e7..1c6dc5bdc 100644 --- a/docs/reference/targets/shell_source.mdx +++ b/docs/reference/targets/shell_source.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/docs/reference/targets/shell_sources.mdx b/docs/reference/targets/shell_sources.mdx index 4b767bfad..e84b6f488 100644 --- a/docs/reference/targets/shell_sources.mdx +++ b/docs/reference/targets/shell_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -118,9 +118,9 @@ If true, don't run Shellcheck on this target's code. Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/docs/reference/targets/shunit2_test.mdx b/docs/reference/targets/shunit2_test.mdx index a51f07485..2f82fc266 100644 --- a/docs/reference/targets/shunit2_test.mdx +++ b/docs/reference/targets/shunit2_test.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -67,9 +67,9 @@ Path is relative to the BUILD file's directory, e.g. `source='example.ext'` Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -119,11 +119,11 @@ Which shell to run the tests with. If unspecified, Pants will look for a shebang default_repr={`None`} > -Addresses to targets that can be built with the `scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run. +Addresses to targets that can be built with the `pants package` goal and whose resulting artifacts should be included in the test run. -Pants will build the artifacts as if you had run `scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). +Pants will build the artifacts as if you had run `pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). -You can include anything that can be built by `scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_aws_lambda_function`, or an `archive`. +You can include anything that can be built by `pants package`, e.g. a `pex_binary`, `python_aws_lambda_function`, or an `archive`. diff --git a/docs/reference/targets/shunit2_tests.mdx b/docs/reference/targets/shunit2_tests.mdx index 029172608..52a4ad9d9 100644 --- a/docs/reference/targets/shunit2_tests.mdx +++ b/docs/reference/targets/shunit2_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -118,9 +118,9 @@ If true, don't run Shellcheck on this target's code. Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -170,11 +170,11 @@ Which shell to run the tests with. If unspecified, Pants will look for a shebang default_repr={`None`} > -Addresses to targets that can be built with the `scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run. +Addresses to targets that can be built with the `pants package` goal and whose resulting artifacts should be included in the test run. -Pants will build the artifacts as if you had run `scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). +Pants will build the artifacts as if you had run `pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). -You can include anything that can be built by `scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_aws_lambda_function`, or an `archive`. +You can include anything that can be built by `pants package`, e.g. a `pex_binary`, `python_aws_lambda_function`, or an `archive`. diff --git a/docs/reference/targets/system_binary.mdx b/docs/reference/targets/system_binary.mdx index 9920f16b2..d7bd775a0 100644 --- a/docs/reference/targets/system_binary.mdx +++ b/docs/reference/targets/system_binary.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.adhoc` @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/docs/reference/targets/target.mdx b/docs/reference/targets/target.mdx index 511195499..18d9f91f0 100644 --- a/docs/reference/targets/target.mdx +++ b/docs/reference/targets/target.mdx @@ -26,7 +26,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -52,9 +52,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/docs/reference/targets/terraform_deployment.mdx b/docs/reference/targets/terraform_deployment.mdx index 79f25e8a9..fec9f55e0 100644 --- a/docs/reference/targets/terraform_deployment.mdx +++ b/docs/reference/targets/terraform_deployment.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.terraform` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/docs/reference/targets/terraform_module.mdx b/docs/reference/targets/terraform_module.mdx index 33d0a5fc1..fbede7796 100644 --- a/docs/reference/targets/terraform_module.mdx +++ b/docs/reference/targets/terraform_module.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.terraform` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -54,9 +54,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/docs/reference/targets/thrift_source.mdx b/docs/reference/targets/thrift_source.mdx index 9de43d94f..59d3e6e61 100644 --- a/docs/reference/targets/thrift_source.mdx +++ b/docs/reference/targets/thrift_source.mdx @@ -27,7 +27,7 @@ Backend: `pants.backend.codegen.thrift.apache.p Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -40,7 +40,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -53,9 +53,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/docs/reference/targets/thrift_sources.mdx b/docs/reference/targets/thrift_sources.mdx index 9fe7dea6c..1c9fd65a9 100644 --- a/docs/reference/targets/thrift_sources.mdx +++ b/docs/reference/targets/thrift_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.codegen.thrift.apache.p Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -109,9 +109,9 @@ All dependencies must share the same value for their `resolve` field. Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.20/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/docs/reference/targets/vcs_version.mdx b/docs/reference/targets/vcs_version.mdx index 8a0c290ec..03d0ae014 100644 --- a/docs/reference/targets/vcs_version.mdx +++ b/docs/reference/targets/vcs_version.mdx @@ -30,7 +30,7 @@ Backend: `pants.backend.experimental.python` @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.0/reference/help-all.json b/versioned_docs/version-2.0/reference/help-all.json index 45fe64755..b0948fbb8 100644 --- a/versioned_docs/version-2.0/reference/help-all.json +++ b/versioned_docs/version-2.0/reference/help-all.json @@ -1367,7 +1367,7 @@ { "details": "from env var PANTS_BIN_NAME", "rank": "ENVIRONMENT", - "value": "/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64" + "value": "/home/josh/work/scie-pants/dist/pants" } ] } @@ -4088,7 +4088,7 @@ "deprecated_message": null, "display_args": ["--[no-]bandit-skip"], "env_var": "PANTS_BANDIT_SKIP", - "help": "Don't use Bandit when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`", + "help": "Don't use Bandit when running `/home/josh/work/scie-pants/dist/pants lint`", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--bandit-skip", "--no-bandit-skip"], @@ -4415,7 +4415,7 @@ "deprecated_message": null, "display_args": ["--[no-]black-skip"], "env_var": "PANTS_BLACK_SKIP", - "help": "Don't use Black when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`", + "help": "Don't use Black when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--black-skip", "--no-black-skip"], @@ -5365,7 +5365,7 @@ "deprecated_message": null, "display_args": ["--[no-]docformatter-skip"], "env_var": "PANTS_DOCFORMATTER_SKIP", - "help": "Don't use docformatter when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use docformatter when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -6100,7 +6100,7 @@ "deprecated_message": null, "display_args": ["--[no-]flake8-skip"], "env_var": "PANTS_FLAKE8_SKIP", - "help": "Don't use Flake8 when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`", + "help": "Don't use Flake8 when running `/home/josh/work/scie-pants/dist/pants lint`", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--flake8-skip", "--no-flake8-skip"], @@ -6743,7 +6743,7 @@ "deprecated_message": null, "display_args": ["--[no-]isort-skip"], "env_var": "PANTS_ISORT_SKIP", - "help": "Don't use isort when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use isort when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--isort-skip", "--no-isort-skip"], @@ -7379,7 +7379,7 @@ "deprecated_message": null, "display_args": ["--[no-]mypy-skip"], "env_var": "PANTS_MYPY_SKIP", - "help": "Don't use MyPy when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use MyPy when running `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--mypy-skip", "--no-mypy-skip"], @@ -7951,7 +7951,7 @@ "deprecated_message": null, "display_args": ["--[no-]pylint-skip"], "env_var": "PANTS_PYLINT_SKIP", - "help": "Don't use Pylint when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`", + "help": "Don't use Pylint when running `/home/josh/work/scie-pants/dist/pants lint`", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pylint-skip", "--no-pylint-skip"], diff --git a/versioned_docs/version-2.0/reference/subsystems/bandit.mdx b/versioned_docs/version-2.0/reference/subsystems/bandit.mdx index 8977c0ca1..bb689f55f 100644 --- a/versioned_docs/version-2.0/reference/subsystems/bandit.mdx +++ b/versioned_docs/version-2.0/reference/subsystems/bandit.mdx @@ -25,7 +25,7 @@ Config section: `[bandit]` default_repr={`False`} > -Don't use Bandit when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint` +Don't use Bandit when running `/home/josh/work/scie-pants/dist/pants lint` diff --git a/versioned_docs/version-2.0/reference/subsystems/black.mdx b/versioned_docs/version-2.0/reference/subsystems/black.mdx index bdb6e49ca..f3659d7f2 100644 --- a/versioned_docs/version-2.0/reference/subsystems/black.mdx +++ b/versioned_docs/version-2.0/reference/subsystems/black.mdx @@ -25,7 +25,7 @@ Config section: `[black]` default_repr={`False`} > -Don't use Black when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint` +Don't use Black when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint` diff --git a/versioned_docs/version-2.0/reference/subsystems/docformatter.mdx b/versioned_docs/version-2.0/reference/subsystems/docformatter.mdx index a574b3120..4d72644b3 100644 --- a/versioned_docs/version-2.0/reference/subsystems/docformatter.mdx +++ b/versioned_docs/version-2.0/reference/subsystems/docformatter.mdx @@ -25,7 +25,7 @@ Config section: `[docformatter]` default_repr={`False`} > -Don't use docformatter when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use docformatter when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.0/reference/subsystems/flake8.mdx b/versioned_docs/version-2.0/reference/subsystems/flake8.mdx index 7512a0bac..40289939f 100644 --- a/versioned_docs/version-2.0/reference/subsystems/flake8.mdx +++ b/versioned_docs/version-2.0/reference/subsystems/flake8.mdx @@ -25,7 +25,7 @@ Config section: `[flake8]` default_repr={`False`} > -Don't use Flake8 when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint` +Don't use Flake8 when running `/home/josh/work/scie-pants/dist/pants lint` diff --git a/versioned_docs/version-2.0/reference/subsystems/isort.mdx b/versioned_docs/version-2.0/reference/subsystems/isort.mdx index ea684feda..d17d20853 100644 --- a/versioned_docs/version-2.0/reference/subsystems/isort.mdx +++ b/versioned_docs/version-2.0/reference/subsystems/isort.mdx @@ -25,7 +25,7 @@ Config section: `[isort]` default_repr={`False`} > -Don't use isort when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use isort when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.0/reference/subsystems/mypy.mdx b/versioned_docs/version-2.0/reference/subsystems/mypy.mdx index ad7e9d64b..69f932388 100644 --- a/versioned_docs/version-2.0/reference/subsystems/mypy.mdx +++ b/versioned_docs/version-2.0/reference/subsystems/mypy.mdx @@ -25,7 +25,7 @@ Config section: `[mypy]` default_repr={`False`} > -Don't use MyPy when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use MyPy when running `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.0/reference/subsystems/pylint.mdx b/versioned_docs/version-2.0/reference/subsystems/pylint.mdx index 9f5310f0e..2b3fb18cd 100644 --- a/versioned_docs/version-2.0/reference/subsystems/pylint.mdx +++ b/versioned_docs/version-2.0/reference/subsystems/pylint.mdx @@ -25,7 +25,7 @@ Config section: `[pylint]` default_repr={`False`} > -Don't use Pylint when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint` +Don't use Pylint when running `/home/josh/work/scie-pants/dist/pants lint` diff --git a/versioned_docs/version-2.1/reference/help-all.json b/versioned_docs/version-2.1/reference/help-all.json index 890eb3b13..8161f2ebe 100644 --- a/versioned_docs/version-2.1/reference/help-all.json +++ b/versioned_docs/version-2.1/reference/help-all.json @@ -1319,7 +1319,7 @@ { "details": "from env var PANTS_BIN_NAME", "rank": "ENVIRONMENT", - "value": "/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64" + "value": "/home/josh/work/scie-pants/dist/pants" } ] } @@ -3712,7 +3712,7 @@ "deprecated_message": null, "display_args": ["--[no-]bandit-skip"], "env_var": "PANTS_BANDIT_SKIP", - "help": "Don't use Bandit when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`", + "help": "Don't use Bandit when running `/home/josh/work/scie-pants/dist/pants lint`", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--bandit-skip", "--no-bandit-skip"], @@ -3926,7 +3926,7 @@ "deprecated_message": null, "display_args": ["--[no-]black-skip"], "env_var": "PANTS_BLACK_SKIP", - "help": "Don't use Black when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`", + "help": "Don't use Black when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--black-skip", "--no-black-skip"], @@ -4745,7 +4745,7 @@ "deprecated_message": null, "display_args": ["--[no-]docformatter-skip"], "env_var": "PANTS_DOCFORMATTER_SKIP", - "help": "Don't use docformatter when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use docformatter when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -5379,7 +5379,7 @@ "deprecated_message": null, "display_args": ["--[no-]flake8-skip"], "env_var": "PANTS_FLAKE8_SKIP", - "help": "Don't use Flake8 when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`", + "help": "Don't use Flake8 when running `/home/josh/work/scie-pants/dist/pants lint`", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--flake8-skip", "--no-flake8-skip"], @@ -5919,7 +5919,7 @@ "deprecated_message": null, "display_args": ["--[no-]isort-skip"], "env_var": "PANTS_ISORT_SKIP", - "help": "Don't use isort when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use isort when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--isort-skip", "--no-isort-skip"], @@ -6487,7 +6487,7 @@ "deprecated_message": null, "display_args": ["--[no-]mypy-skip"], "env_var": "PANTS_MYPY_SKIP", - "help": "Don't use MyPy when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use MyPy when running `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--mypy-skip", "--no-mypy-skip"], @@ -6994,7 +6994,7 @@ "deprecated_message": null, "display_args": ["--[no-]pylint-skip"], "env_var": "PANTS_PYLINT_SKIP", - "help": "Don't use Pylint when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`", + "help": "Don't use Pylint when running `/home/josh/work/scie-pants/dist/pants lint`", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pylint-skip", "--no-pylint-skip"], diff --git a/versioned_docs/version-2.1/reference/subsystems/bandit.mdx b/versioned_docs/version-2.1/reference/subsystems/bandit.mdx index fbb4af88d..40364a77f 100644 --- a/versioned_docs/version-2.1/reference/subsystems/bandit.mdx +++ b/versioned_docs/version-2.1/reference/subsystems/bandit.mdx @@ -25,7 +25,7 @@ Config section: `[bandit]` default_repr={`False`} > -Don't use Bandit when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint` +Don't use Bandit when running `/home/josh/work/scie-pants/dist/pants lint` diff --git a/versioned_docs/version-2.1/reference/subsystems/black.mdx b/versioned_docs/version-2.1/reference/subsystems/black.mdx index bdb6e49ca..f3659d7f2 100644 --- a/versioned_docs/version-2.1/reference/subsystems/black.mdx +++ b/versioned_docs/version-2.1/reference/subsystems/black.mdx @@ -25,7 +25,7 @@ Config section: `[black]` default_repr={`False`} > -Don't use Black when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint` +Don't use Black when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint` diff --git a/versioned_docs/version-2.1/reference/subsystems/docformatter.mdx b/versioned_docs/version-2.1/reference/subsystems/docformatter.mdx index a574b3120..4d72644b3 100644 --- a/versioned_docs/version-2.1/reference/subsystems/docformatter.mdx +++ b/versioned_docs/version-2.1/reference/subsystems/docformatter.mdx @@ -25,7 +25,7 @@ Config section: `[docformatter]` default_repr={`False`} > -Don't use docformatter when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use docformatter when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.1/reference/subsystems/flake8.mdx b/versioned_docs/version-2.1/reference/subsystems/flake8.mdx index d3e9a2cf3..e6b12a1e5 100644 --- a/versioned_docs/version-2.1/reference/subsystems/flake8.mdx +++ b/versioned_docs/version-2.1/reference/subsystems/flake8.mdx @@ -25,7 +25,7 @@ Config section: `[flake8]` default_repr={`False`} > -Don't use Flake8 when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint` +Don't use Flake8 when running `/home/josh/work/scie-pants/dist/pants lint` diff --git a/versioned_docs/version-2.1/reference/subsystems/isort.mdx b/versioned_docs/version-2.1/reference/subsystems/isort.mdx index ea684feda..d17d20853 100644 --- a/versioned_docs/version-2.1/reference/subsystems/isort.mdx +++ b/versioned_docs/version-2.1/reference/subsystems/isort.mdx @@ -25,7 +25,7 @@ Config section: `[isort]` default_repr={`False`} > -Don't use isort when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use isort when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.1/reference/subsystems/mypy.mdx b/versioned_docs/version-2.1/reference/subsystems/mypy.mdx index ad7e9d64b..69f932388 100644 --- a/versioned_docs/version-2.1/reference/subsystems/mypy.mdx +++ b/versioned_docs/version-2.1/reference/subsystems/mypy.mdx @@ -25,7 +25,7 @@ Config section: `[mypy]` default_repr={`False`} > -Don't use MyPy when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use MyPy when running `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.1/reference/subsystems/pylint.mdx b/versioned_docs/version-2.1/reference/subsystems/pylint.mdx index 4a5738e4b..2144b0084 100644 --- a/versioned_docs/version-2.1/reference/subsystems/pylint.mdx +++ b/versioned_docs/version-2.1/reference/subsystems/pylint.mdx @@ -25,7 +25,7 @@ Config section: `[pylint]` default_repr={`False`} > -Don't use Pylint when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint` +Don't use Pylint when running `/home/josh/work/scie-pants/dist/pants lint` diff --git a/versioned_docs/version-2.10/reference/help-all.json b/versioned_docs/version-2.10/reference/help-all.json index a08dfdf5f..d7c5a5d7b 100644 --- a/versioned_docs/version-2.10/reference/help-all.json +++ b/versioned_docs/version-2.10/reference/help-all.json @@ -11469,7 +11469,7 @@ { "details": "from env var PANTS_BIN_NAME", "rank": "ENVIRONMENT", - "value": "/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64" + "value": "/home/josh/work/scie-pants/dist/pants" } ] } @@ -14329,7 +14329,7 @@ "deprecation_active": false, "display_args": ["--[no-]autoflake-skip"], "env_var": "PANTS_AUTOFLAKE_SKIP", - "help": "Don't use Autoflake when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`", + "help": "Don't use Autoflake when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--autoflake-skip", "--no-autoflake-skip"], @@ -14578,7 +14578,7 @@ "deprecation_active": false, "display_args": ["--[no-]bandit-skip"], "env_var": "PANTS_BANDIT_SKIP", - "help": "Don't use Bandit when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`", + "help": "Don't use Bandit when running `/home/josh/work/scie-pants/dist/pants lint`", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--bandit-skip", "--no-bandit-skip"], @@ -14897,7 +14897,7 @@ "deprecation_active": false, "display_args": ["--[no-]black-skip"], "env_var": "PANTS_BLACK_SKIP", - "help": "Don't use Black when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`", + "help": "Don't use Black when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--black-skip", "--no-black-skip"], @@ -16251,7 +16251,7 @@ "deprecation_active": false, "display_args": ["--[no-]docformatter-skip"], "env_var": "PANTS_DOCFORMATTER_SKIP", - "help": "Don't use docformatter when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use docformatter when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -17560,7 +17560,7 @@ "deprecation_active": false, "display_args": ["--[no-]flake8-skip"], "env_var": "PANTS_FLAKE8_SKIP", - "help": "Don't use Flake8 when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`", + "help": "Don't use Flake8 when running `/home/josh/work/scie-pants/dist/pants lint`", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--flake8-skip", "--no-flake8-skip"], @@ -17856,7 +17856,7 @@ "deprecation_active": false, "display_args": ["--[no-]gofmt-skip"], "env_var": "PANTS_GOFMT_SKIP", - "help": "Don't use gofmt when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use gofmt when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--gofmt-skip", "--no-gofmt-skip"], @@ -18107,7 +18107,7 @@ "deprecation_active": false, "display_args": ["--[no-]google-java-format-skip"], "env_var": "PANTS_GOOGLE_JAVA_FORMAT_SKIP", - "help": "Don't use Google Java Format when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`", + "help": "Don't use Google Java Format when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -19169,7 +19169,7 @@ "deprecation_active": false, "display_args": ["--[no-]isort-skip"], "env_var": "PANTS_ISORT_SKIP", - "help": "Don't use isort when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use isort when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--isort-skip", "--no-isort-skip"], @@ -20419,7 +20419,7 @@ "deprecation_active": false, "display_args": ["--[no-]mypy-skip"], "env_var": "PANTS_MYPY_SKIP", - "help": "Don't use MyPy when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 typecheck`.", + "help": "Don't use MyPy when running `/home/josh/work/scie-pants/dist/pants typecheck`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--mypy-skip", "--no-mypy-skip"], @@ -21860,7 +21860,7 @@ "deprecation_active": false, "display_args": ["--[no-]pylint-skip"], "env_var": "PANTS_PYLINT_SKIP", - "help": "Don't use Pylint when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`", + "help": "Don't use Pylint when running `/home/josh/work/scie-pants/dist/pants lint`", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pylint-skip", "--no-pylint-skip"], @@ -23983,7 +23983,7 @@ "deprecation_active": false, "display_args": ["--[no-]pyupgrade-skip"], "env_var": "PANTS_PYUPGRADE_SKIP", - "help": "Don't use pyupgrade when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use pyupgrade when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pyupgrade-skip", "--no-pyupgrade-skip"], @@ -24660,7 +24660,7 @@ "deprecation_active": false, "display_args": ["--[no-]scalafmt-skip"], "env_var": "PANTS_SCALAFMT_SKIP", - "help": "Don't use `scalafmt` when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`", + "help": "Don't use `scalafmt` when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalafmt-skip", "--no-scalafmt-skip"], @@ -27515,7 +27515,7 @@ "deprecation_active": false, "display_args": ["--[no-]yapf-skip"], "env_var": "PANTS_YAPF_SKIP", - "help": "Don't use yapf when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use yapf when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--yapf-skip", "--no-yapf-skip"], diff --git a/versioned_docs/version-2.10/reference/subsystems/autoflake.mdx b/versioned_docs/version-2.10/reference/subsystems/autoflake.mdx index cbd4b3579..1609baf2c 100644 --- a/versioned_docs/version-2.10/reference/subsystems/autoflake.mdx +++ b/versioned_docs/version-2.10/reference/subsystems/autoflake.mdx @@ -25,7 +25,7 @@ Config section: `[autoflake]` default_repr={`False`} > -Don't use Autoflake when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint` +Don't use Autoflake when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint` diff --git a/versioned_docs/version-2.10/reference/subsystems/bandit.mdx b/versioned_docs/version-2.10/reference/subsystems/bandit.mdx index 40d7bfe60..854df22bf 100644 --- a/versioned_docs/version-2.10/reference/subsystems/bandit.mdx +++ b/versioned_docs/version-2.10/reference/subsystems/bandit.mdx @@ -25,7 +25,7 @@ Config section: `[bandit]` default_repr={`False`} > -Don't use Bandit when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint` +Don't use Bandit when running `/home/josh/work/scie-pants/dist/pants lint` diff --git a/versioned_docs/version-2.10/reference/subsystems/black.mdx b/versioned_docs/version-2.10/reference/subsystems/black.mdx index 01d085688..a2eef953a 100644 --- a/versioned_docs/version-2.10/reference/subsystems/black.mdx +++ b/versioned_docs/version-2.10/reference/subsystems/black.mdx @@ -25,7 +25,7 @@ Config section: `[black]` default_repr={`False`} > -Don't use Black when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint` +Don't use Black when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint` diff --git a/versioned_docs/version-2.10/reference/subsystems/docformatter.mdx b/versioned_docs/version-2.10/reference/subsystems/docformatter.mdx index ade048b37..19b128ff0 100644 --- a/versioned_docs/version-2.10/reference/subsystems/docformatter.mdx +++ b/versioned_docs/version-2.10/reference/subsystems/docformatter.mdx @@ -25,7 +25,7 @@ Config section: `[docformatter]` default_repr={`False`} > -Don't use docformatter when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use docformatter when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.10/reference/subsystems/flake8.mdx b/versioned_docs/version-2.10/reference/subsystems/flake8.mdx index 7bb217dc8..b5ea435c7 100644 --- a/versioned_docs/version-2.10/reference/subsystems/flake8.mdx +++ b/versioned_docs/version-2.10/reference/subsystems/flake8.mdx @@ -25,7 +25,7 @@ Config section: `[flake8]` default_repr={`False`} > -Don't use Flake8 when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint` +Don't use Flake8 when running `/home/josh/work/scie-pants/dist/pants lint` diff --git a/versioned_docs/version-2.10/reference/subsystems/gofmt.mdx b/versioned_docs/version-2.10/reference/subsystems/gofmt.mdx index 01c96bcf2..a4ae242b4 100644 --- a/versioned_docs/version-2.10/reference/subsystems/gofmt.mdx +++ b/versioned_docs/version-2.10/reference/subsystems/gofmt.mdx @@ -25,7 +25,7 @@ Config section: `[gofmt]` default_repr={`False`} > -Don't use gofmt when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use gofmt when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.10/reference/subsystems/google-java-format.mdx b/versioned_docs/version-2.10/reference/subsystems/google-java-format.mdx index 103f2e222..a296bb586 100644 --- a/versioned_docs/version-2.10/reference/subsystems/google-java-format.mdx +++ b/versioned_docs/version-2.10/reference/subsystems/google-java-format.mdx @@ -25,7 +25,7 @@ Config section: `[google-java-format]` default_repr={`False`} > -Don't use Google Java Format when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint` +Don't use Google Java Format when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint` diff --git a/versioned_docs/version-2.10/reference/subsystems/isort.mdx b/versioned_docs/version-2.10/reference/subsystems/isort.mdx index 86fd31aa0..25abddcc1 100644 --- a/versioned_docs/version-2.10/reference/subsystems/isort.mdx +++ b/versioned_docs/version-2.10/reference/subsystems/isort.mdx @@ -25,7 +25,7 @@ Config section: `[isort]` default_repr={`False`} > -Don't use isort when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use isort when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.10/reference/subsystems/mypy.mdx b/versioned_docs/version-2.10/reference/subsystems/mypy.mdx index 2730cc68a..f953f196d 100644 --- a/versioned_docs/version-2.10/reference/subsystems/mypy.mdx +++ b/versioned_docs/version-2.10/reference/subsystems/mypy.mdx @@ -25,7 +25,7 @@ Config section: `[mypy]` default_repr={`False`} > -Don't use MyPy when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 typecheck`. +Don't use MyPy when running `/home/josh/work/scie-pants/dist/pants typecheck`. diff --git a/versioned_docs/version-2.10/reference/subsystems/pylint.mdx b/versioned_docs/version-2.10/reference/subsystems/pylint.mdx index 3c3795e80..1edb76602 100644 --- a/versioned_docs/version-2.10/reference/subsystems/pylint.mdx +++ b/versioned_docs/version-2.10/reference/subsystems/pylint.mdx @@ -25,7 +25,7 @@ Config section: `[pylint]` default_repr={`False`} > -Don't use Pylint when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint` +Don't use Pylint when running `/home/josh/work/scie-pants/dist/pants lint` diff --git a/versioned_docs/version-2.10/reference/subsystems/pyupgrade.mdx b/versioned_docs/version-2.10/reference/subsystems/pyupgrade.mdx index a65a67643..32422d6aa 100644 --- a/versioned_docs/version-2.10/reference/subsystems/pyupgrade.mdx +++ b/versioned_docs/version-2.10/reference/subsystems/pyupgrade.mdx @@ -25,7 +25,7 @@ Config section: `[pyupgrade]` default_repr={`False`} > -Don't use pyupgrade when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use pyupgrade when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.10/reference/subsystems/scalafmt.mdx b/versioned_docs/version-2.10/reference/subsystems/scalafmt.mdx index 72b812352..7813be79c 100644 --- a/versioned_docs/version-2.10/reference/subsystems/scalafmt.mdx +++ b/versioned_docs/version-2.10/reference/subsystems/scalafmt.mdx @@ -25,7 +25,7 @@ Config section: `[scalafmt]` default_repr={`False`} > -Don't use `scalafmt` when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint` +Don't use `scalafmt` when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint` diff --git a/versioned_docs/version-2.10/reference/subsystems/yapf.mdx b/versioned_docs/version-2.10/reference/subsystems/yapf.mdx index cfabb64b3..e1cfa2dbc 100644 --- a/versioned_docs/version-2.10/reference/subsystems/yapf.mdx +++ b/versioned_docs/version-2.10/reference/subsystems/yapf.mdx @@ -25,7 +25,7 @@ Config section: `[yapf]` default_repr={`False`} > -Don't use yapf when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use yapf when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.11/reference/global-options.mdx b/versioned_docs/version-2.11/reference/global-options.mdx index 124895289..647d1c733 100644 --- a/versioned_docs/version-2.11/reference/global-options.mdx +++ b/versioned_docs/version-2.11/reference/global-options.mdx @@ -314,9 +314,9 @@ ignore_warnings = [ Use this Pants version. Note that Pants only uses this to verify that you are using the requested version, as Pants cannot dynamically change the version it is using once the program is already running. -If you use the `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64` script from https://www.pantsbuild.org/v2.11/docs/installation, however, changing the value in your `pants.toml` will cause the new version to be installed and run automatically. +If you use the `/home/josh/work/scie-pants/dist/pants` script from https://www.pantsbuild.org/v2.11/docs/installation, however, changing the value in your `pants.toml` will cause the new version to be installed and run automatically. -Run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --version` to check what is being used. +Run `/home/josh/work/scie-pants/dist/pants --version` to check what is being used. @@ -1183,7 +1183,7 @@ True if stats recording should be allowed to complete asynchronously when `pants env_repr='PANTS_USE_DEPRECATED_PYTHON_MACROS' default_repr={`False`} removal_version='2.12.0.dev0' - removal_hint={'In Pants 2.12, the deprecated Python macros like `python_requirements` will be replaced with improved target generators, which are now enabled by default.

If you already migrated by setting `use_deprecated_python_macros = false`, simply delete the option.

Otherwise, when you are ready to upgrade, follow these steps:

1. Run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 update-build-files --fix-python-macros`
2. Check the logs for an ERROR log to see if you have to manually add `name=` anywhere.
3. Remove `use_deprecated_python_macros = true` from `[GLOBAL]` in pants.toml.

(Why upgrade from the old macro mechanism to target generation? Among other benefits, it makes sure that the Pants daemon is properly invalidated when you change `requirements.txt` and `pyproject.toml`.)'} + removal_hint={'In Pants 2.12, the deprecated Python macros like `python_requirements` will be replaced with improved target generators, which are now enabled by default.

If you already migrated by setting `use_deprecated_python_macros = false`, simply delete the option.

Otherwise, when you are ready to upgrade, follow these steps:

1. Run `/home/josh/work/scie-pants/dist/pants update-build-files --fix-python-macros`
2. Check the logs for an ERROR log to see if you have to manually add `name=` anywhere.
3. Remove `use_deprecated_python_macros = true` from `[GLOBAL]` in pants.toml.

(Why upgrade from the old macro mechanism to target generation? Among other benefits, it makes sure that the Pants daemon is properly invalidated when you change `requirements.txt` and `pyproject.toml`.)'} > If true, use Pants's deprecated macro system for `python_requirements`, `poetry_requirements`, and `pipenv_requirements` rather than target generation. diff --git a/versioned_docs/version-2.11/reference/goals/experimental-bsp.mdx b/versioned_docs/version-2.11/reference/goals/experimental-bsp.mdx index 3e74c0105..0dcf8894f 100644 --- a/versioned_docs/version-2.11/reference/goals/experimental-bsp.mdx +++ b/versioned_docs/version-2.11/reference/goals/experimental-bsp.mdx @@ -47,7 +47,7 @@ Run the Build Server Protocol server. Pants will receive BSP RPC requests via th Environment variables to set in the BSP runner script when setting up BSP in a repository. Entries are either strings in the form `ENV_VAR=value` to set an explicit value; or just `ENV_VAR` to copy the value from Pants' own environment when the experimental-bsp goal was run. -This option only takes effect when the BSP runner script is written. If the option changes, you must run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 experimental-bsp` again to write a new copy of the BSP runner script. +This option only takes effect when the BSP runner script is written. If the option changes, you must run `/home/josh/work/scie-pants/dist/pants experimental-bsp` again to write a new copy of the BSP runner script. Note: The environment variables passed to the Pants BSP server will be those set for your IDE and not your shell. For example, on macOS, the IDE is generally launched by `launchd` after clicking on a Dock icon, and not from the shell. Thus, any environment variables set for your shell will likely not be seen by the Pants BSP server. At the very least, on macOS consider writing an explicit PATH into the BSP runner script via this option. diff --git a/versioned_docs/version-2.11/reference/goals/generate-lockfiles.mdx b/versioned_docs/version-2.11/reference/goals/generate-lockfiles.mdx index b08aaff9a..90348459c 100644 --- a/versioned_docs/version-2.11/reference/goals/generate-lockfiles.mdx +++ b/versioned_docs/version-2.11/reference/goals/generate-lockfiles.mdx @@ -33,7 +33,7 @@ Only generate lockfiles for the specified resolve(s). Resolves are the logical names for the different lockfiles used in your project. For your own code's dependencies, these come from the option `[python].resolves`. For tool lockfiles, resolve names are the options scope for that tool such as `black`, `pytest`, and `mypy-protobuf`. -For example, you can run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=black --resolve=pytest --resolve=data-science` to only generate lockfiles for those two tools and your resolve named `data-science`. +For example, you can run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=black --resolve=pytest --resolve=data-science` to only generate lockfiles for those two tools and your resolve named `data-science`. If you specify an invalid resolve name, like 'fake', Pants will output all possible values. @@ -51,7 +51,7 @@ If not specified, Pants will generate lockfiles for all resolves. default_repr={`None`} > -If set, lockfile headers will say to run this command to regenerate the lockfile, rather than running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=` like normal. +If set, lockfile headers will say to run this command to regenerate the lockfile, rather than running `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=` like normal. diff --git a/versioned_docs/version-2.11/reference/help-all.json b/versioned_docs/version-2.11/reference/help-all.json index 5420a1a04..39fce1e15 100644 --- a/versioned_docs/version-2.11/reference/help-all.json +++ b/versioned_docs/version-2.11/reference/help-all.json @@ -205,7 +205,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -213,7 +213,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -221,7 +221,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -229,7 +229,7 @@ { "alias": "packages", "default": null, - "description": "Addresses to any targets that can be built with `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, e.g. `[\"project:app\"]`.\n\nPants will build the assets as if you had run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`. It will include the results in your archive using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or even another `archive`.", + "description": "Addresses to any targets that can be built with `/home/josh/work/scie-pants/dist/pants package`, e.g. `[\"project:app\"]`.\n\nPants will build the assets as if you had run `/home/josh/work/scie-pants/dist/pants package`. It will include the results in your archive using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `/home/josh/work/scie-pants/dist/pants package`, e.g. a `pex_binary`, `python_awslambda`, or even another `archive`.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -261,7 +261,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -269,7 +269,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -277,7 +277,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -285,7 +285,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -333,7 +333,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -341,7 +341,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -357,7 +357,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -437,7 +437,7 @@ { "alias": "skip_push", "default": "False", - "description": "If set to true, do not push this image to registries when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 publish`.", + "description": "If set to true, do not push this image to registries when running `/home/josh/work/scie-pants/dist/pants publish`.", "provider": "", "required": false, "type_hint": "bool" @@ -477,7 +477,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -485,7 +485,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -493,7 +493,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -525,7 +525,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -533,7 +533,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -541,7 +541,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -597,7 +597,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -605,7 +605,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -613,7 +613,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -637,7 +637,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -645,7 +645,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -669,7 +669,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -685,7 +685,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -693,7 +693,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -701,7 +701,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -733,7 +733,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -741,7 +741,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -757,7 +757,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -765,7 +765,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -773,7 +773,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -821,7 +821,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -829,7 +829,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -837,7 +837,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -861,7 +861,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -869,7 +869,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -893,7 +893,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -901,7 +901,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built directory tree should be located.\n\nIf undefined, this will use the path to the BUILD file, For example, `src/charts/mychart:tgt_name` would be `src.charts.mychart/tgt_name/`.\n\nRegardless of whether you use the default or set this field, the path will end with Helms's file format of `-.tgz`, where `chart_name` and `chart_version` are the values extracted from the Chart.yaml file. So, using the default for this field, the target `src/charts/mychart:tgt_name` might have a final path like `src.charts.mychart/tgt_name/mychart-0.1.0.tgz`.\n\nWhen running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built directory tree should be located.\n\nIf undefined, this will use the path to the BUILD file, For example, `src/charts/mychart:tgt_name` would be `src.charts.mychart/tgt_name/`.\n\nRegardless of whether you use the default or set this field, the path will end with Helms's file format of `-.tgz`, where `chart_name` and `chart_version` are the values extracted from the Chart.yaml file. So, using the default for this field, the target `src/charts/mychart:tgt_name` might have a final path like `src.charts.mychart/tgt_name/mychart-0.1.0.tgz`.\n\nWhen running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -917,7 +917,7 @@ { "alias": "skip_push", "default": "False", - "description": "If set to true, do not push this helm chart to registries when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 publish`.", + "description": "If set to true, do not push this helm chart to registries when running `/home/josh/work/scie-pants/dist/pants publish`.", "provider": "", "required": false, "type_hint": "bool" @@ -933,7 +933,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -941,7 +941,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -949,7 +949,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -1005,7 +1005,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -1013,7 +1013,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -1029,7 +1029,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -1069,7 +1069,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -1077,7 +1077,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -1093,7 +1093,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -1133,7 +1133,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -1141,7 +1141,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -1157,7 +1157,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -1197,7 +1197,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -1205,7 +1205,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -1285,7 +1285,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -1293,7 +1293,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -1317,7 +1317,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -1333,7 +1333,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -1349,7 +1349,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -1357,7 +1357,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -1389,7 +1389,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -1397,7 +1397,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -1437,7 +1437,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -1557,7 +1557,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -1565,7 +1565,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -1589,7 +1589,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -1717,7 +1717,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -1733,7 +1733,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -1741,7 +1741,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -1797,7 +1797,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -1805,7 +1805,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -1861,7 +1861,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -1869,7 +1869,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -1877,7 +1877,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -1965,7 +1965,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -1973,7 +1973,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -2061,7 +2061,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -2077,7 +2077,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -2085,7 +2085,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -2093,7 +2093,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built directory tree should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:bin` would be `src.python.project/bin/`.\n\nRegardless of whether you use the default or set this field, the path will end with PyOxidizer's file format of `/{debug,release}/install/`, where `platform` is a Rust platform triplet like `aarch-64-apple-darwin` and `binary_name` is the `name` of the `pyoxidizer_target`. So, using the default for this field, the target `src/python/project:bin` might have a final path like `src.python.project/bin/aarch-64-apple-darwin/release/bin`.\n\nWhen running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built directory tree should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:bin` would be `src.python.project/bin/`.\n\nRegardless of whether you use the default or set this field, the path will end with PyOxidizer's file format of `/{debug,release}/install/`, where `platform` is a Rust platform triplet like `aarch-64-apple-darwin` and `binary_name` is the `name` of the `pyoxidizer_target`. So, using the default for this field, the target `src/python/project:bin` might have a final path like `src.python.project/bin/aarch-64-apple-darwin/release/bin`.\n\nWhen running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -2141,7 +2141,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -2149,7 +2149,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -2157,7 +2157,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -2165,7 +2165,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -2221,7 +2221,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -2229,7 +2229,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -2237,7 +2237,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -2245,7 +2245,7 @@ { "alias": "entry_points", "default": null, - "description": "Any entry points, such as `console_scripts` and `gui_scripts`.\n\nSpecify as a nested dictionary, with a dictionary for each type of entry point, e.g. `console_scripts` vs. `gui_scripts`. Each dictionary maps the entry point name to either a setuptools entry point (\"path.to.module:func\") or a Pants target address to a pex_binary target.\n\nExample:\n\n entry_points={\n \"console_scripts\": {\n \"my-script\": \"project.app:main\",\n \"another-script\": \"project/subdir:pex_binary_tgt\"\n }\n }\n\nNote that Pants will assume that any value that either starts with `:` or has `/` in it, is a target address to a pex_binary target. Otherwise, it will assume it's a setuptools entry point as defined by https://packaging.python.org/specifications/entry-points/#entry-points-specification. Use `//` as a prefix for target addresses if you need to disambiguate.\n\nPants will attempt to infer dependencies, which you can confirm by running:\n\n /home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies \n\n", + "description": "Any entry points, such as `console_scripts` and `gui_scripts`.\n\nSpecify as a nested dictionary, with a dictionary for each type of entry point, e.g. `console_scripts` vs. `gui_scripts`. Each dictionary maps the entry point name to either a setuptools entry point (\"path.to.module:func\") or a Pants target address to a pex_binary target.\n\nExample:\n\n entry_points={\n \"console_scripts\": {\n \"my-script\": \"project.app:main\",\n \"another-script\": \"project/subdir:pex_binary_tgt\"\n }\n }\n\nNote that Pants will assume that any value that either starts with `:` or has `/` in it, is a target address to a pex_binary target. Otherwise, it will assume it's a setuptools entry point as defined by https://packaging.python.org/specifications/entry-points/#entry-points-specification. Use `//` as a prefix for target addresses if you need to disambiguate.\n\nPants will attempt to infer dependencies, which you can confirm by running:\n\n /home/josh/work/scie-pants/dist/pants dependencies \n\n", "provider": "", "required": false, "type_hint": "Dict[str, Dict[str, str]] | None" @@ -2333,7 +2333,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -2341,7 +2341,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -2349,7 +2349,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -2357,7 +2357,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -2413,7 +2413,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -2421,7 +2421,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -2429,7 +2429,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -2477,7 +2477,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -2485,7 +2485,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -2541,7 +2541,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -2549,7 +2549,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -2565,7 +2565,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -2677,7 +2677,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -2685,7 +2685,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -2797,7 +2797,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -2821,7 +2821,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -2829,7 +2829,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -2837,7 +2837,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -2861,7 +2861,7 @@ { "alias": "runtime_package_dependencies", "default": null, - "description": "Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`.", + "description": "Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/pants package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `/home/josh/work/scie-pants/dist/pants package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -2893,7 +2893,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -2997,7 +2997,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -3005,7 +3005,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -3117,7 +3117,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -3141,7 +3141,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -3149,7 +3149,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -3253,7 +3253,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -3277,7 +3277,7 @@ { "alias": "runtime_package_dependencies", "default": null, - "description": "Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`.", + "description": "Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/pants package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `/home/josh/work/scie-pants/dist/pants package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -3317,7 +3317,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -3325,7 +3325,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -3365,7 +3365,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -3373,7 +3373,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -3381,7 +3381,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -3405,7 +3405,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -3413,7 +3413,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -3437,7 +3437,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -3453,7 +3453,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -3461,7 +3461,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -3469,7 +3469,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -3525,7 +3525,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -3533,7 +3533,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -3549,7 +3549,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -3597,7 +3597,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -3605,7 +3605,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -3613,7 +3613,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -3677,7 +3677,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -3685,7 +3685,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -3709,7 +3709,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -3757,7 +3757,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -3765,7 +3765,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -3797,7 +3797,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -3805,7 +3805,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -3813,7 +3813,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -3869,7 +3869,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -3877,7 +3877,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -3893,7 +3893,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -3941,7 +3941,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -3949,7 +3949,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -3957,7 +3957,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -3997,7 +3997,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -4005,7 +4005,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -4045,7 +4045,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -4061,7 +4061,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -4069,7 +4069,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -4085,7 +4085,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -4117,7 +4117,7 @@ { "alias": "runtime_package_dependencies", "default": null, - "description": "Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`.", + "description": "Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/pants package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `/home/josh/work/scie-pants/dist/pants package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -4149,7 +4149,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -4157,7 +4157,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -4197,7 +4197,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -4229,7 +4229,7 @@ { "alias": "runtime_package_dependencies", "default": null, - "description": "Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`.", + "description": "Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/pants package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `/home/josh/work/scie-pants/dist/pants package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -4245,7 +4245,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -4253,7 +4253,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -4261,7 +4261,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -4277,7 +4277,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -4285,7 +4285,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -4293,7 +4293,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -4317,7 +4317,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -4325,7 +4325,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -4333,7 +4333,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -4365,7 +4365,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -4373,7 +4373,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -4405,7 +4405,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -12914,7 +12914,7 @@ "deprecation_active": false, "display_args": ["--pants-version="], "env_var": "PANTS_VERSION", - "help": "Use this Pants version. Note that Pants only uses this to verify that you are using the requested version, as Pants cannot dynamically change the version it is using once the program is already running.\n\nIf you use the `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64` script from https://www.pantsbuild.org/v2.11/docs/installation, however, changing the value in your `pants.toml` will cause the new version to be installed and run automatically.\n\nRun `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --version` to check what is being used.", + "help": "Use this Pants version. Note that Pants only uses this to verify that you are using the requested version, as Pants cannot dynamically change the version it is using once the program is already running.\n\nIf you use the `/home/josh/work/scie-pants/dist/pants` script from https://www.pantsbuild.org/v2.11/docs/installation, however, changing the value in your `pants.toml` will cause the new version to be installed and run automatically.\n\nRun `/home/josh/work/scie-pants/dist/pants --version` to check what is being used.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pants-version"], @@ -12971,7 +12971,7 @@ { "details": "from env var PANTS_BIN_NAME", "rank": "ENVIRONMENT", - "value": "/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64" + "value": "/home/josh/work/scie-pants/dist/pants" } ] } @@ -15495,7 +15495,7 @@ "display_args": ["--[no-]use-deprecated-python-macros"], "env_var": "PANTS_USE_DEPRECATED_PYTHON_MACROS", "help": "If true, use Pants's deprecated macro system for `python_requirements`, `poetry_requirements`, and `pipenv_requirements` rather than target generation.\n\nThe address for macros is different. Rather than `3rdparty/python#Django`, the address will look like `3rdparty/python:Django`. The macro (`python_requirements` et al) also was not a proper target, meaning that you could not give it a `name`. In contrast, if the target generator sets its `name`, e.g. to `reqs`, generated targets will have an address like `3rdparty/python:reqs#Django`.", - "removal_hint": "In Pants 2.12, the deprecated Python macros like `python_requirements` will be replaced with improved target generators, which are now enabled by default.\n\nIf you already migrated by setting `use_deprecated_python_macros = false`, simply delete the option.\n\nOtherwise, when you are ready to upgrade, follow these steps:\n\n 1. Run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 update-build-files --fix-python-macros`\n 2. Check the logs for an ERROR log to see if you have to manually add `name=` anywhere.\n 3. Remove `use_deprecated_python_macros = true` from `[GLOBAL]` in pants.toml.\n\n(Why upgrade from the old macro mechanism to target generation? Among other benefits, it makes sure that the Pants daemon is properly invalidated when you change `requirements.txt` and `pyproject.toml`.)", + "removal_hint": "In Pants 2.12, the deprecated Python macros like `python_requirements` will be replaced with improved target generators, which are now enabled by default.\n\nIf you already migrated by setting `use_deprecated_python_macros = false`, simply delete the option.\n\nOtherwise, when you are ready to upgrade, follow these steps:\n\n 1. Run `/home/josh/work/scie-pants/dist/pants update-build-files --fix-python-macros`\n 2. Check the logs for an ERROR log to see if you have to manually add `name=` anywhere.\n 3. Remove `use_deprecated_python_macros = true` from `[GLOBAL]` in pants.toml.\n\n(Why upgrade from the old macro mechanism to target generation? Among other benefits, it makes sure that the Pants daemon is properly invalidated when you change `requirements.txt` and `pyproject.toml`.)", "removal_version": "2.12.0.dev0", "scoped_cmd_line_args": [ "--use-deprecated-python-macros", @@ -15783,7 +15783,7 @@ "deprecation_active": false, "display_args": ["--autoflake-lockfile="], "env_var": "PANTS_AUTOFLAKE_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.11.1/src/python/pants/backend/python/lint/autoflake/autoflake.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=autoflake`.\n\nAs explained at https://www.pantsbuild.org/v2.11/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.11.1/src/python/pants/backend/python/lint/autoflake/autoflake.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=autoflake`.\n\nAs explained at https://www.pantsbuild.org/v2.11/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--autoflake-lockfile"], @@ -15873,7 +15873,7 @@ "deprecation_active": false, "display_args": ["--[no-]autoflake-skip"], "env_var": "PANTS_AUTOFLAKE_SKIP", - "help": "Don't use Autoflake when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use Autoflake when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--autoflake-skip", "--no-autoflake-skip"], @@ -16011,7 +16011,7 @@ "deprecation_active": false, "display_args": ["--bandit-lockfile="], "env_var": "PANTS_BANDIT_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.11.1/src/python/pants/backend/python/lint/bandit/bandit.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=bandit`.\n\nAs explained at https://www.pantsbuild.org/v2.11/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.11.1/src/python/pants/backend/python/lint/bandit/bandit.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=bandit`.\n\nAs explained at https://www.pantsbuild.org/v2.11/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--bandit-lockfile"], @@ -16127,7 +16127,7 @@ "deprecation_active": false, "display_args": ["--[no-]bandit-skip"], "env_var": "PANTS_BANDIT_SKIP", - "help": "Don't use Bandit when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use Bandit when running `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--bandit-skip", "--no-bandit-skip"], @@ -16298,7 +16298,7 @@ "deprecation_active": false, "display_args": ["--black-lockfile="], "env_var": "PANTS_BLACK_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.11.1/src/python/pants/backend/python/lint/black/black.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=black`.\n\nAs explained at https://www.pantsbuild.org/v2.11/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.11.1/src/python/pants/backend/python/lint/black/black.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=black`.\n\nAs explained at https://www.pantsbuild.org/v2.11/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--black-lockfile"], @@ -16451,7 +16451,7 @@ "deprecation_active": false, "display_args": ["--[no-]black-skip"], "env_var": "PANTS_BLACK_SKIP", - "help": "Don't use Black when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use Black when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--black-skip", "--no-black-skip"], @@ -16704,7 +16704,7 @@ "deprecation_active": false, "display_args": ["--[no-]buf-format-skip"], "env_var": "PANTS_BUF_FORMAT_SKIP", - "help": "Don't use Buf when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use Buf when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--buf-format-skip", "--no-buf-format-skip"], @@ -16735,7 +16735,7 @@ "deprecation_active": false, "display_args": ["--[no-]buf-lint-skip"], "env_var": "PANTS_BUF_LINT_SKIP", - "help": "Don't use Buf when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use Buf when running `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--buf-lint-skip", "--no-buf-lint-skip"], @@ -16979,7 +16979,7 @@ "deprecation_active": false, "display_args": ["--cli-alias=\"{'key1': val1, 'key2': val2, ...}\""], "env_var": "PANTS_CLI_ALIAS", - "help": "Register command line aliases.\nExample:\n\n [cli.alias]\n green = \"fmt lint check\"\n all-changed = \"--changed-since=HEAD --changed-dependees=transitive\"\n\nThis would allow you to run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 green all-changed`, which is shorthand for `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt lint check --changed-since=HEAD --changed-dependees=transitive`.\n\nNotice: this option must be placed in a config file (e.g. `pants.toml` or `pantsrc`) to have any effect.", + "help": "Register command line aliases.\nExample:\n\n [cli.alias]\n green = \"fmt lint check\"\n all-changed = \"--changed-since=HEAD --changed-dependees=transitive\"\n\nThis would allow you to run `/home/josh/work/scie-pants/dist/pants green all-changed`, which is shorthand for `/home/josh/work/scie-pants/dist/pants fmt lint check --changed-since=HEAD --changed-dependees=transitive`.\n\nNotice: this option must be placed in a config file (e.g. `pants.toml` or `pantsrc`) to have any effect.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--cli-alias"], @@ -17357,7 +17357,7 @@ "deprecation_active": false, "display_args": ["--coverage-py-lockfile="], "env_var": "PANTS_COVERAGE_PY_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.11.1/src/python/pants/backend/python/subsystems/coverage_py.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=coverage-py`.\n\nAs explained at https://www.pantsbuild.org/v2.11/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.11.1/src/python/pants/backend/python/subsystems/coverage_py.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=coverage-py`.\n\nAs explained at https://www.pantsbuild.org/v2.11/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--coverage-py-lockfile"], @@ -18044,7 +18044,7 @@ "deprecation_active": false, "display_args": ["--docformatter-lockfile="], "env_var": "PANTS_DOCFORMATTER_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.11.1/src/python/pants/backend/python/lint/docformatter/docformatter.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=docformatter`.\n\nAs explained at https://www.pantsbuild.org/v2.11/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.11.1/src/python/pants/backend/python/lint/docformatter/docformatter.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=docformatter`.\n\nAs explained at https://www.pantsbuild.org/v2.11/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--docformatter-lockfile"], @@ -18134,7 +18134,7 @@ "deprecation_active": false, "display_args": ["--[no-]docformatter-skip"], "env_var": "PANTS_DOCFORMATTER_SKIP", - "help": "Don't use docformatter when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use docformatter when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -18500,7 +18500,7 @@ "--docker-run-args=\"[, , ...]\"" ], "env_var": "PANTS_DOCKER_RUN_ARGS", - "help": "Additional arguments to use for `docker run` invocations.\n\nExample:\n\n $ /home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 run --docker-run-args=\"-p 127.0.0.1:80:8080/tcp --name demo\" src/example:image -- [image entrypoint args]\n\nTo provide the top-level options to the `docker` client, use `[docker].env_vars` to configure the [Environment variables](https://docs.docker.com/engine/reference/commandline/cli/#environment-variables) as appropriate.\n\nThe arguments for the image entrypoint may be passed on the command line after a double dash (`--`), or using the `--run-args` option.\n\nDefaults to `--interactive --tty` when stdout is connected to a terminal.", + "help": "Additional arguments to use for `docker run` invocations.\n\nExample:\n\n $ /home/josh/work/scie-pants/dist/pants run --docker-run-args=\"-p 127.0.0.1:80:8080/tcp --name demo\" src/example:image -- [image entrypoint args]\n\nTo provide the top-level options to the `docker` client, use `[docker].env_vars` to configure the [Environment variables](https://docs.docker.com/engine/reference/commandline/cli/#environment-variables) as appropriate.\n\nThe arguments for the image entrypoint may be passed on the command line after a double dash (`--`), or using the `--run-args` option.\n\nDefaults to `--interactive --tty` when stdout is connected to a terminal.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--docker-run-args"], @@ -18640,7 +18640,7 @@ "deprecation_active": false, "display_args": ["--dockerfile-parser-lockfile="], "env_var": "PANTS_DOCKERFILE_PARSER_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.11.1/src/python/pants/backend/docker/subsystems/dockerfile.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=dockerfile-parser`.\n\nAs explained at https://www.pantsbuild.org/v2.11/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.11.1/src/python/pants/backend/docker/subsystems/dockerfile.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=dockerfile-parser`.\n\nAs explained at https://www.pantsbuild.org/v2.11/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--dockerfile-parser-lockfile"], @@ -18908,7 +18908,7 @@ "--experimental-bsp-runner-env-vars=\"['', '', ...]\"" ], "env_var": "PANTS_EXPERIMENTAL_BSP_RUNNER_ENV_VARS", - "help": "Environment variables to set in the BSP runner script when setting up BSP in a repository. Entries are either strings in the form `ENV_VAR=value` to set an explicit value; or just `ENV_VAR` to copy the value from Pants' own environment when the experimental-bsp goal was run.\n\nThis option only takes effect when the BSP runner script is written. If the option changes, you must run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 experimental-bsp` again to write a new copy of the BSP runner script.\n\nNote: The environment variables passed to the Pants BSP server will be those set for your IDE and not your shell. For example, on macOS, the IDE is generally launched by `launchd` after clicking on a Dock icon, and not from the shell. Thus, any environment variables set for your shell will likely not be seen by the Pants BSP server. At the very least, on macOS consider writing an explicit PATH into the BSP runner script via this option.", + "help": "Environment variables to set in the BSP runner script when setting up BSP in a repository. Entries are either strings in the form `ENV_VAR=value` to set an explicit value; or just `ENV_VAR` to copy the value from Pants' own environment when the experimental-bsp goal was run.\n\nThis option only takes effect when the BSP runner script is written. If the option changes, you must run `/home/josh/work/scie-pants/dist/pants experimental-bsp` again to write a new copy of the BSP runner script.\n\nNote: The environment variables passed to the Pants BSP server will be those set for your IDE and not your shell. For example, on macOS, the IDE is generally launched by `launchd` after clicking on a Dock icon, and not from the shell. Thus, any environment variables set for your shell will likely not be seen by the Pants BSP server. At the very least, on macOS consider writing an explicit PATH into the BSP runner script via this option.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--experimental-bsp-runner-env-vars"], @@ -19399,7 +19399,7 @@ "deprecation_active": false, "display_args": ["--flake8-lockfile="], "env_var": "PANTS_FLAKE8_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.11.1/src/python/pants/backend/python/lint/flake8/flake8.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=flake8`.\n\nAs explained at https://www.pantsbuild.org/v2.11/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.11.1/src/python/pants/backend/python/lint/flake8/flake8.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=flake8`.\n\nAs explained at https://www.pantsbuild.org/v2.11/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--flake8-lockfile"], @@ -19585,7 +19585,7 @@ "deprecation_active": false, "display_args": ["--[no-]flake8-skip"], "env_var": "PANTS_FLAKE8_SKIP", - "help": "Don't use Flake8 when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use Flake8 when running `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--flake8-skip", "--no-flake8-skip"], @@ -19731,7 +19731,7 @@ "deprecation_active": false, "display_args": ["--generate-lockfiles-custom-command="], "env_var": "PANTS_GENERATE_LOCKFILES_CUSTOM_COMMAND", - "help": "If set, lockfile headers will say to run this command to regenerate the lockfile, rather than running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=` like normal.", + "help": "If set, lockfile headers will say to run this command to regenerate the lockfile, rather than running `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=` like normal.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--generate-lockfiles-custom-command"], @@ -19761,7 +19761,7 @@ "--generate-lockfiles-resolve=\"['', '', ...]\"" ], "env_var": "PANTS_GENERATE_LOCKFILES_RESOLVE", - "help": "Only generate lockfiles for the specified resolve(s).\n\nResolves are the logical names for the different lockfiles used in your project. For your own code's dependencies, these come from the option `[python].resolves`. For tool lockfiles, resolve names are the options scope for that tool such as `black`, `pytest`, and `mypy-protobuf`.\n\nFor example, you can run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=black --resolve=pytest --resolve=data-science` to only generate lockfiles for those two tools and your resolve named `data-science`.\n\nIf you specify an invalid resolve name, like 'fake', Pants will output all possible values.\n\nIf not specified, Pants will generate lockfiles for all resolves.", + "help": "Only generate lockfiles for the specified resolve(s).\n\nResolves are the logical names for the different lockfiles used in your project. For your own code's dependencies, these come from the option `[python].resolves`. For tool lockfiles, resolve names are the options scope for that tool such as `black`, `pytest`, and `mypy-protobuf`.\n\nFor example, you can run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=black --resolve=pytest --resolve=data-science` to only generate lockfiles for those two tools and your resolve named `data-science`.\n\nIf you specify an invalid resolve name, like 'fake', Pants will output all possible values.\n\nIf not specified, Pants will generate lockfiles for all resolves.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--generate-lockfiles-resolve"], @@ -19848,7 +19848,7 @@ "deprecation_active": false, "display_args": ["--[no-]gofmt-skip"], "env_var": "PANTS_GOFMT_SKIP", - "help": "Don't use gofmt when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use gofmt when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--gofmt-skip", "--no-gofmt-skip"], @@ -20066,7 +20066,7 @@ "deprecation_active": false, "display_args": ["--google-java-format-lockfile="], "env_var": "PANTS_GOOGLE_JAVA_FORMAT_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.11.1/src/python/pants/backend/java/lint/google_java_format/google_java_format.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=google-java-format`.\n\n", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.11.1/src/python/pants/backend/java/lint/google_java_format/google_java_format.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=google-java-format`.\n\n", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--google-java-format-lockfile"], @@ -20099,7 +20099,7 @@ "deprecation_active": false, "display_args": ["--[no-]google-java-format-skip"], "env_var": "PANTS_GOOGLE_JAVA_FORMAT_SKIP", - "help": "Don't use Google Java Format when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use Google Java Format when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -20613,7 +20613,7 @@ "deprecation_active": false, "display_args": ["--[no-]hadolint-skip"], "env_var": "PANTS_HADOLINT_SKIP", - "help": "Don't use Hadolint when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use Hadolint when running `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--hadolint-skip", "--no-hadolint-skip"], @@ -21006,7 +21006,7 @@ "deprecation_active": false, "display_args": ["--ipython-lockfile="], "env_var": "PANTS_IPYTHON_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.11.1/src/python/pants/backend/python/subsystems/ipython.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=ipython`.\n\nAs explained at https://www.pantsbuild.org/v2.11/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.11.1/src/python/pants/backend/python/subsystems/ipython.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=ipython`.\n\nAs explained at https://www.pantsbuild.org/v2.11/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--ipython-lockfile"], @@ -21236,7 +21236,7 @@ "deprecation_active": false, "display_args": ["--isort-lockfile="], "env_var": "PANTS_ISORT_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.11.1/src/python/pants/backend/python/lint/isort/isort.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=isort`.\n\nAs explained at https://www.pantsbuild.org/v2.11/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.11.1/src/python/pants/backend/python/lint/isort/isort.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=isort`.\n\nAs explained at https://www.pantsbuild.org/v2.11/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--isort-lockfile"], @@ -21396,7 +21396,7 @@ "deprecation_active": false, "display_args": ["--[no-]isort-skip"], "env_var": "PANTS_ISORT_SKIP", - "help": "Don't use isort when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use isort when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--isort-skip", "--no-isort-skip"], @@ -21729,7 +21729,7 @@ "deprecation_active": false, "display_args": ["--junit-lockfile="], "env_var": "PANTS_JUNIT_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.11.1/src/python/pants/jvm/test/junit.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=junit`.\n\n", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.11.1/src/python/pants/jvm/test/junit.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=junit`.\n\n", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--junit-lockfile"], @@ -22076,7 +22076,7 @@ "deprecation_active": false, "display_args": ["--lambdex-lockfile="], "env_var": "PANTS_LAMBDEX_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.11.1/src/python/pants/backend/python/subsystems/lambdex.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=lambdex`.\n\nAs explained at https://www.pantsbuild.org/v2.11/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.11.1/src/python/pants/backend/python/subsystems/lambdex.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=lambdex`.\n\nAs explained at https://www.pantsbuild.org/v2.11/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--lambdex-lockfile"], @@ -22445,7 +22445,7 @@ "deprecation_active": false, "display_args": ["--mypy-lockfile="], "env_var": "PANTS_MYPY_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.11.1/src/python/pants/backend/python/typecheck/mypy/mypy.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=mypy`.\n\nAs explained at https://www.pantsbuild.org/v2.11/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.11.1/src/python/pants/backend/python/typecheck/mypy/mypy.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=mypy`.\n\nAs explained at https://www.pantsbuild.org/v2.11/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--mypy-lockfile"], @@ -22664,7 +22664,7 @@ "deprecation_active": false, "display_args": ["--[no-]mypy-skip"], "env_var": "PANTS_MYPY_SKIP", - "help": "Don't use MyPy when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 check`.", + "help": "Don't use MyPy when running `/home/josh/work/scie-pants/dist/pants check`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--mypy-skip", "--no-mypy-skip"], @@ -22833,7 +22833,7 @@ "deprecation_active": false, "display_args": ["--mypy-protobuf-lockfile="], "env_var": "PANTS_MYPY_PROTOBUF_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.11.1/src/python/pants/backend/codegen/protobuf/python/mypy_protobuf.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=mypy-protobuf`.\n\nAs explained at https://www.pantsbuild.org/v2.11/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.11.1/src/python/pants/backend/codegen/protobuf/python/mypy_protobuf.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=mypy-protobuf`.\n\nAs explained at https://www.pantsbuild.org/v2.11/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--mypy-protobuf-lockfile"], @@ -23929,7 +23929,7 @@ "deprecation_active": false, "display_args": ["--pylint-lockfile="], "env_var": "PANTS_PYLINT_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.11.1/src/python/pants/backend/python/lint/pylint/pylint.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=pylint`.\n\nAs explained at https://www.pantsbuild.org/v2.11/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.11.1/src/python/pants/backend/python/lint/pylint/pylint.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=pylint`.\n\nAs explained at https://www.pantsbuild.org/v2.11/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pylint-lockfile"], @@ -24115,7 +24115,7 @@ "deprecation_active": false, "display_args": ["--[no-]pylint-skip"], "env_var": "PANTS_PYLINT_SKIP", - "help": "Don't use Pylint when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use Pylint when running `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pylint-skip", "--no-pylint-skip"], @@ -24450,7 +24450,7 @@ "deprecation_active": false, "display_args": ["--pytest-lockfile="], "env_var": "PANTS_PYTEST_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.11.1/src/python/pants/backend/python/subsystems/pytest.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=pytest`.\n\nAs explained at https://www.pantsbuild.org/v2.11/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.11.1/src/python/pants/backend/python/subsystems/pytest.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=pytest`.\n\nAs explained at https://www.pantsbuild.org/v2.11/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pytest-lockfile"], @@ -24877,7 +24877,7 @@ "--python-resolves=\"{'key1': val1, 'key2': val2, ...}\"" ], "env_var": "PANTS_PYTHON_RESOLVES", - "help": "A mapping of logical names to lockfile paths used in your project.\n\nMany organizations only need a single resolve for their whole project, which is a good default and often the simplest thing to do. However, you may need multiple resolves, such as if you use two conflicting versions of a requirement in your repository.\n\nIf you only need a single resolve, run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles` to generate the lockfile.\n\nIf you need multiple resolves:\n\n 1. Via this option, define multiple resolve names and their lockfile paths. The names should be meaningful to your repository, such as `data-science` or `pants-plugins`.\n 2. Set the default with `[python].default_resolve`.\n 3. Update your `python_requirement` targets with the `resolve` field to declare which resolve they should be available in. They default to `[python].default_resolve`, so you only need to update targets that you want in non-default resolves. (Often you'll set this via the `python_requirements` or `poetry_requirements` target generators)\n 4. Run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles` to generate the lockfiles. If the results aren't what you'd expect, adjust the prior step.\n 5. Update any targets like `python_source` / `python_sources`, `python_test` / `python_tests`, and `pex_binary` which need to set a non-default resolve with the `resolve` field.\n\nIf a target can work with multiple resolves, you can either use the `parametrize` mechanism or manually create a distinct target per resolve. See https://www.pantsbuild.org/v2.11/docs/targets for information about `parametrize`. For example:\n\n python_sources(\n resolve=parametrize(data-science', 'web-app'),\n )\n\nYou can name the lockfile paths what you would like; Pants does not expect a certain file extension or location.\n\nOnly applies if `[python].enable_resolves` is true.", + "help": "A mapping of logical names to lockfile paths used in your project.\n\nMany organizations only need a single resolve for their whole project, which is a good default and often the simplest thing to do. However, you may need multiple resolves, such as if you use two conflicting versions of a requirement in your repository.\n\nIf you only need a single resolve, run `/home/josh/work/scie-pants/dist/pants generate-lockfiles` to generate the lockfile.\n\nIf you need multiple resolves:\n\n 1. Via this option, define multiple resolve names and their lockfile paths. The names should be meaningful to your repository, such as `data-science` or `pants-plugins`.\n 2. Set the default with `[python].default_resolve`.\n 3. Update your `python_requirement` targets with the `resolve` field to declare which resolve they should be available in. They default to `[python].default_resolve`, so you only need to update targets that you want in non-default resolves. (Often you'll set this via the `python_requirements` or `poetry_requirements` target generators)\n 4. Run `/home/josh/work/scie-pants/dist/pants generate-lockfiles` to generate the lockfiles. If the results aren't what you'd expect, adjust the prior step.\n 5. Update any targets like `python_source` / `python_sources`, `python_test` / `python_tests`, and `pex_binary` which need to set a non-default resolve with the `resolve` field.\n\nIf a target can work with multiple resolves, you can either use the `parametrize` mechanism or manually create a distinct target per resolve. See https://www.pantsbuild.org/v2.11/docs/targets for information about `parametrize`. For example:\n\n python_sources(\n resolve=parametrize(data-science', 'web-app'),\n )\n\nYou can name the lockfile paths what you would like; Pants does not expect a certain file extension or location.\n\nOnly applies if `[python].enable_resolves` is true.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--python-resolves"], @@ -25009,7 +25009,7 @@ "deprecation_active": false, "display_args": ["--python-lockfile-generator="], "env_var": "PANTS_PYTHON_LOCKFILE_GENERATOR", - "help": "Whether to use Pex or Poetry with the `generate-lockfiles` goal.\n\nPoetry does not support these features:\n\n 1) `[python-repos]` for custom indexes/cheeseshops.\n 2) VCS (Git) requirements.\n 3) `[GLOBAL].ca_certs_path`\n\n.If you use any of these features, you should use Pex.\n\nSeveral users have also had issues with how Poetry's lockfile generation handles environment markers for transitive dependencies; certain dependencies end up with nonsensical environment markers which cause the dependency to not be installed, then for Pants/Pex to complain the dependency is missing, even though it's in the lockfile. There is a workaround: for `[python].resolves`, manually create a `python_requirement` target for the problematic transitive dependencies so that they are seen as direct requirements, rather than transitive. For tool lockfiles, add the problematic transitive dependency to `[tool].extra_requirements`, e.g. `[isort].extra_requirements`. Then, regenerate the lockfile(s) with the `generate-lockfiles` goal. Alternatively, use Pex for generation.\n\nFinally, installing from a Poetry-generated lockfile is slower than installing from a Pex lockfile. When using a Pex lockfile, Pants will only install the subset needed for the current task.\n\nHowever, Pex lockfile generation is a beta feature. Given how vast the Python packaging ecosystem is, it is possible you may experience edge cases / bugs we haven't yet covered. Bug reports are appreciated! https://github.com/pantsbuild/pants/issues/new/choose\n\nNote that while Pex generates locks in a proprietary JSON format, you can use the `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export` goal for Pants to create a virtual environment for interoperability with tools like IDEs.", + "help": "Whether to use Pex or Poetry with the `generate-lockfiles` goal.\n\nPoetry does not support these features:\n\n 1) `[python-repos]` for custom indexes/cheeseshops.\n 2) VCS (Git) requirements.\n 3) `[GLOBAL].ca_certs_path`\n\n.If you use any of these features, you should use Pex.\n\nSeveral users have also had issues with how Poetry's lockfile generation handles environment markers for transitive dependencies; certain dependencies end up with nonsensical environment markers which cause the dependency to not be installed, then for Pants/Pex to complain the dependency is missing, even though it's in the lockfile. There is a workaround: for `[python].resolves`, manually create a `python_requirement` target for the problematic transitive dependencies so that they are seen as direct requirements, rather than transitive. For tool lockfiles, add the problematic transitive dependency to `[tool].extra_requirements`, e.g. `[isort].extra_requirements`. Then, regenerate the lockfile(s) with the `generate-lockfiles` goal. Alternatively, use Pex for generation.\n\nFinally, installing from a Poetry-generated lockfile is slower than installing from a Pex lockfile. When using a Pex lockfile, Pants will only install the subset needed for the current task.\n\nHowever, Pex lockfile generation is a beta feature. Given how vast the Python packaging ecosystem is, it is possible you may experience edge cases / bugs we haven't yet covered. Bug reports are appreciated! https://github.com/pantsbuild/pants/issues/new/choose\n\nNote that while Pex generates locks in a proprietary JSON format, you can use the `/home/josh/work/scie-pants/dist/pants export` goal for Pants to create a virtual environment for interoperability with tools like IDEs.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--python-lockfile-generator"], @@ -25609,7 +25609,7 @@ "deprecation_active": false, "display_args": ["--[no-]python-infer-inits"], "env_var": "PANTS_PYTHON_INFER_INITS", - "help": "Infer a target's dependencies on any `__init__.py` files in the packages it is located in (recursively upward in the directory structure).\n\nEven if this is disabled, Pants will still include any ancestor `__init__.py` files, only they will not be 'proper' dependencies, e.g. they will not show up in `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` and their own dependencies will not be used.\n\nIf you have empty `__init__.py` files, it's safe to leave this option off; otherwise, you should enable this option.", + "help": "Infer a target's dependencies on any `__init__.py` files in the packages it is located in (recursively upward in the directory structure).\n\nEven if this is disabled, Pants will still include any ancestor `__init__.py` files, only they will not be 'proper' dependencies, e.g. they will not show up in `/home/josh/work/scie-pants/dist/pants dependencies` and their own dependencies will not be used.\n\nIf you have empty `__init__.py` files, it's safe to leave this option off; otherwise, you should enable this option.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -26170,7 +26170,7 @@ "deprecation_active": false, "display_args": ["--pyupgrade-lockfile="], "env_var": "PANTS_PYUPGRADE_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.11.1/src/python/pants/backend/python/lint/pyupgrade/pyupgrade.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=pyupgrade`.\n\nAs explained at https://www.pantsbuild.org/v2.11/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.11.1/src/python/pants/backend/python/lint/pyupgrade/pyupgrade.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=pyupgrade`.\n\nAs explained at https://www.pantsbuild.org/v2.11/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pyupgrade-lockfile"], @@ -26260,7 +26260,7 @@ "deprecation_active": false, "display_args": ["--[no-]pyupgrade-skip"], "env_var": "PANTS_PYUPGRADE_SKIP", - "help": "Don't use pyupgrade when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use pyupgrade when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pyupgrade-skip", "--no-pyupgrade-skip"], @@ -26949,7 +26949,7 @@ "deprecation_active": false, "display_args": ["--scalafmt-lockfile="], "env_var": "PANTS_SCALAFMT_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.11.1/src/python/pants/backend/scala/lint/scalafmt/scalafmt.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalafmt`.\n\n", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.11.1/src/python/pants/backend/scala/lint/scalafmt/scalafmt.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=scalafmt`.\n\n", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalafmt-lockfile"], @@ -26982,7 +26982,7 @@ "deprecation_active": false, "display_args": ["--[no-]scalafmt-skip"], "env_var": "PANTS_SCALAFMT_SKIP", - "help": "Don't use scalafmt when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use scalafmt when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalafmt-skip", "--no-scalafmt-skip"], @@ -27085,7 +27085,7 @@ "deprecation_active": false, "display_args": ["--scalapb-lockfile="], "env_var": "PANTS_SCALAPB_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.11.1/src/python/pants/backend/codegen/protobuf/scala/scalapbc.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalapb`.\n\n", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.11.1/src/python/pants/backend/codegen/protobuf/scala/scalapbc.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=scalapb`.\n\n", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalapb-lockfile"], @@ -27254,7 +27254,7 @@ "deprecation_active": false, "display_args": ["--scalatest-lockfile="], "env_var": "PANTS_SCALATEST_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.11.1/src/python/pants/backend/scala/subsystems/scalatest.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalatest`.\n\n", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.11.1/src/python/pants/backend/scala/subsystems/scalatest.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=scalatest`.\n\n", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalatest-lockfile"], @@ -27703,7 +27703,7 @@ "deprecation_active": false, "display_args": ["--setuptools-lockfile="], "env_var": "PANTS_SETUPTOOLS_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.11.1/src/python/pants/backend/python/subsystems/setuptools.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=setuptools`.\n\nAs explained at https://www.pantsbuild.org/v2.11/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.11.1/src/python/pants/backend/python/subsystems/setuptools.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=setuptools`.\n\nAs explained at https://www.pantsbuild.org/v2.11/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--setuptools-lockfile"], @@ -28046,7 +28046,7 @@ "deprecation_active": false, "display_args": ["--[no-]shellcheck-skip"], "env_var": "PANTS_SHELLCHECK_SKIP", - "help": "Don't use Shellcheck when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use Shellcheck when running `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--shellcheck-skip", "--no-shellcheck-skip"], @@ -28340,7 +28340,7 @@ "deprecation_active": false, "display_args": ["--[no-]shfmt-skip"], "env_var": "PANTS_SHFMT_SKIP", - "help": "Don't use shfmt when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use shfmt when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--shfmt-skip", "--no-shfmt-skip"], @@ -28870,7 +28870,7 @@ "deprecation_active": false, "display_args": ["--[no-]terraform-fmt-skip"], "env_var": "PANTS_TERRAFORM_FMT_SKIP", - "help": "Don't use `terraform fmt` when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use `terraform fmt` when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -29015,7 +29015,7 @@ "deprecation_active": false, "display_args": ["--terraform-hcl2-parser-lockfile="], "env_var": "PANTS_TERRAFORM_HCL2_PARSER_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.11.1/src/python/pants/backend/terraform/hcl2.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=terraform-hcl2-parser`.\n\nAs explained at https://www.pantsbuild.org/v2.11/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.11.1/src/python/pants/backend/terraform/hcl2.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=terraform-hcl2-parser`.\n\nAs explained at https://www.pantsbuild.org/v2.11/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--terraform-hcl2-parser-lockfile"], @@ -29058,7 +29058,7 @@ "deprecation_active": false, "display_args": ["--[no-]terraform-validate-skip"], "env_var": "PANTS_TERRAFORM_VALIDATE_SKIP", - "help": "Don't use `terraform validate` when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 check`.", + "help": "Don't use `terraform validate` when running `/home/josh/work/scie-pants/dist/pants check`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -29477,7 +29477,7 @@ "deprecation_active": false, "display_args": ["--twine-lockfile="], "env_var": "PANTS_TWINE_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.11.1/src/python/pants/backend/python/subsystems/twine.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=twine`.\n\nAs explained at https://www.pantsbuild.org/v2.11/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.11.1/src/python/pants/backend/python/subsystems/twine.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=twine`.\n\nAs explained at https://www.pantsbuild.org/v2.11/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--twine-lockfile"], @@ -29661,7 +29661,7 @@ "deprecation_active": false, "display_args": ["--[no-]twine-skip"], "env_var": "PANTS_TWINE_SKIP", - "help": "Don't use Twine when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 publish`.", + "help": "Don't use Twine when running `/home/josh/work/scie-pants/dist/pants publish`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--twine-skip", "--no-twine-skip"], @@ -30024,7 +30024,7 @@ "deprecation_active": false, "display_args": ["--yapf-lockfile="], "env_var": "PANTS_YAPF_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.11.1/src/python/pants/backend/python/lint/yapf/yapf.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=yapf`.\n\nAs explained at https://www.pantsbuild.org/v2.11/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.11.1/src/python/pants/backend/python/lint/yapf/yapf.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=yapf`.\n\nAs explained at https://www.pantsbuild.org/v2.11/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--yapf-lockfile"], @@ -30177,7 +30177,7 @@ "deprecation_active": false, "display_args": ["--[no-]yapf-skip"], "env_var": "PANTS_YAPF_SKIP", - "help": "Don't use yapf when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use yapf when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--yapf-skip", "--no-yapf-skip"], diff --git a/versioned_docs/version-2.11/reference/subsystems/autoflake.mdx b/versioned_docs/version-2.11/reference/subsystems/autoflake.mdx index f252dd0db..6012a28f4 100644 --- a/versioned_docs/version-2.11/reference/subsystems/autoflake.mdx +++ b/versioned_docs/version-2.11/reference/subsystems/autoflake.mdx @@ -25,7 +25,7 @@ Config section: `[autoflake]` default_repr={`False`} > -Don't use Autoflake when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use Autoflake when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. @@ -93,7 +93,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=autoflake`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=autoflake`. As explained at https://www.pantsbuild.org/v2.11/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.11/reference/subsystems/bandit.mdx b/versioned_docs/version-2.11/reference/subsystems/bandit.mdx index 07d684edf..c0fb484be 100644 --- a/versioned_docs/version-2.11/reference/subsystems/bandit.mdx +++ b/versioned_docs/version-2.11/reference/subsystems/bandit.mdx @@ -25,7 +25,7 @@ Config section: `[bandit]` default_repr={`False`} > -Don't use Bandit when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use Bandit when running `/home/josh/work/scie-pants/dist/pants lint`. @@ -81,7 +81,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=bandit`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=bandit`. As explained at https://www.pantsbuild.org/v2.11/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.11/reference/subsystems/black.mdx b/versioned_docs/version-2.11/reference/subsystems/black.mdx index d0df66424..ff5b48850 100644 --- a/versioned_docs/version-2.11/reference/subsystems/black.mdx +++ b/versioned_docs/version-2.11/reference/subsystems/black.mdx @@ -25,7 +25,7 @@ Config section: `[black]` default_repr={`False`} > -Don't use Black when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use Black when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. @@ -93,7 +93,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=black`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=black`. As explained at https://www.pantsbuild.org/v2.11/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.11/reference/subsystems/buf.mdx b/versioned_docs/version-2.11/reference/subsystems/buf.mdx index bc855a376..1bb10798e 100644 --- a/versioned_docs/version-2.11/reference/subsystems/buf.mdx +++ b/versioned_docs/version-2.11/reference/subsystems/buf.mdx @@ -25,7 +25,7 @@ Config section: `[buf]` default_repr={`False`} > -Don't use Buf when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use Buf when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. @@ -37,7 +37,7 @@ Don't use Buf when running `/home/josh/work/scie-pants/dist/scie-pants-linu default_repr={`False`} > -Don't use Buf when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use Buf when running `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.11/reference/subsystems/cli.mdx b/versioned_docs/version-2.11/reference/subsystems/cli.mdx index 894dce956..f5f8582c8 100644 --- a/versioned_docs/version-2.11/reference/subsystems/cli.mdx +++ b/versioned_docs/version-2.11/reference/subsystems/cli.mdx @@ -34,7 +34,7 @@ green = "fmt lint check" all-changed = "--changed-since=HEAD --changed-dependees=transitive" ``` -This would allow you to run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 green all-changed`, which is shorthand for `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt lint check --changed-since=HEAD --changed-dependees=transitive`. +This would allow you to run `/home/josh/work/scie-pants/dist/pants green all-changed`, which is shorthand for `/home/josh/work/scie-pants/dist/pants fmt lint check --changed-since=HEAD --changed-dependees=transitive`. Notice: this option must be placed in a config file (e.g. `pants.toml` or `pantsrc`) to have any effect. diff --git a/versioned_docs/version-2.11/reference/subsystems/coverage-py.mdx b/versioned_docs/version-2.11/reference/subsystems/coverage-py.mdx index 74f07f756..c7b36947e 100644 --- a/versioned_docs/version-2.11/reference/subsystems/coverage-py.mdx +++ b/versioned_docs/version-2.11/reference/subsystems/coverage-py.mdx @@ -130,7 +130,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=coverage-py`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=coverage-py`. As explained at https://www.pantsbuild.org/v2.11/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.11/reference/subsystems/docformatter.mdx b/versioned_docs/version-2.11/reference/subsystems/docformatter.mdx index f82eff9ed..8997c1a67 100644 --- a/versioned_docs/version-2.11/reference/subsystems/docformatter.mdx +++ b/versioned_docs/version-2.11/reference/subsystems/docformatter.mdx @@ -25,7 +25,7 @@ Config section: `[docformatter]` default_repr={`False`} > -Don't use docformatter when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use docformatter when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. @@ -93,7 +93,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=docformatter`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=docformatter`. As explained at https://www.pantsbuild.org/v2.11/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.11/reference/subsystems/docker.mdx b/versioned_docs/version-2.11/reference/subsystems/docker.mdx index 1c4e4d9ec..b28c8057b 100644 --- a/versioned_docs/version-2.11/reference/subsystems/docker.mdx +++ b/versioned_docs/version-2.11/reference/subsystems/docker.mdx @@ -151,7 +151,7 @@ Additional arguments to use for `docker run` invocations. Example: ``` -$ /home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 run --docker-run-args="-p 127.0.0.1:80:8080/tcp --name demo" src/example:image -- [image entrypoint args] +$ /home/josh/work/scie-pants/dist/pants run --docker-run-args="-p 127.0.0.1:80:8080/tcp --name demo" src/example:image -- [image entrypoint args] ``` To provide the top-level options to the `docker` client, use `[docker].env_vars` to configure the [Environment variables](https://docs.docker.com/engine/reference/commandline/cli/#environment-variables) as appropriate. diff --git a/versioned_docs/version-2.11/reference/subsystems/dockerfile-parser.mdx b/versioned_docs/version-2.11/reference/subsystems/dockerfile-parser.mdx index b8e428f6a..2e6c3fc02 100644 --- a/versioned_docs/version-2.11/reference/subsystems/dockerfile-parser.mdx +++ b/versioned_docs/version-2.11/reference/subsystems/dockerfile-parser.mdx @@ -71,7 +71,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=dockerfile-parser`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=dockerfile-parser`. As explained at https://www.pantsbuild.org/v2.11/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.11/reference/subsystems/flake8.mdx b/versioned_docs/version-2.11/reference/subsystems/flake8.mdx index c9fd78406..567290241 100644 --- a/versioned_docs/version-2.11/reference/subsystems/flake8.mdx +++ b/versioned_docs/version-2.11/reference/subsystems/flake8.mdx @@ -25,7 +25,7 @@ Config section: `[flake8]` default_repr={`False`} > -Don't use Flake8 when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use Flake8 when running `/home/josh/work/scie-pants/dist/pants lint`. @@ -81,7 +81,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=flake8`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=flake8`. As explained at https://www.pantsbuild.org/v2.11/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.11/reference/subsystems/gofmt.mdx b/versioned_docs/version-2.11/reference/subsystems/gofmt.mdx index 01c96bcf2..a4ae242b4 100644 --- a/versioned_docs/version-2.11/reference/subsystems/gofmt.mdx +++ b/versioned_docs/version-2.11/reference/subsystems/gofmt.mdx @@ -25,7 +25,7 @@ Config section: `[gofmt]` default_repr={`False`} > -Don't use gofmt when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use gofmt when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.11/reference/subsystems/google-java-format.mdx b/versioned_docs/version-2.11/reference/subsystems/google-java-format.mdx index b1f4eadc2..aec5d1e70 100644 --- a/versioned_docs/version-2.11/reference/subsystems/google-java-format.mdx +++ b/versioned_docs/version-2.11/reference/subsystems/google-java-format.mdx @@ -25,7 +25,7 @@ Config section: `[google-java-format]` default_repr={`False`} > -Don't use Google Java Format when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use Google Java Format when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. @@ -79,7 +79,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.11.1/src/python/pants/backend/java/lint/google_java_format/google_java_format.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=google-java-format`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=google-java-format`. diff --git a/versioned_docs/version-2.11/reference/subsystems/hadolint.mdx b/versioned_docs/version-2.11/reference/subsystems/hadolint.mdx index 3a006c18c..ec3957462 100644 --- a/versioned_docs/version-2.11/reference/subsystems/hadolint.mdx +++ b/versioned_docs/version-2.11/reference/subsystems/hadolint.mdx @@ -25,7 +25,7 @@ Config section: `[hadolint]` default_repr={`False`} > -Don't use Hadolint when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use Hadolint when running `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.11/reference/subsystems/ipython.mdx b/versioned_docs/version-2.11/reference/subsystems/ipython.mdx index 9bcc4eb4e..dcafd18d7 100644 --- a/versioned_docs/version-2.11/reference/subsystems/ipython.mdx +++ b/versioned_docs/version-2.11/reference/subsystems/ipython.mdx @@ -59,7 +59,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=ipython`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=ipython`. As explained at https://www.pantsbuild.org/v2.11/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.11/reference/subsystems/isort.mdx b/versioned_docs/version-2.11/reference/subsystems/isort.mdx index b5914cc3e..87b3a6102 100644 --- a/versioned_docs/version-2.11/reference/subsystems/isort.mdx +++ b/versioned_docs/version-2.11/reference/subsystems/isort.mdx @@ -25,7 +25,7 @@ Config section: `[isort]` default_repr={`False`} > -Don't use isort when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use isort when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. @@ -93,7 +93,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=isort`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=isort`. As explained at https://www.pantsbuild.org/v2.11/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.11/reference/subsystems/junit.mdx b/versioned_docs/version-2.11/reference/subsystems/junit.mdx index 5b8f895fc..34e934ddb 100644 --- a/versioned_docs/version-2.11/reference/subsystems/junit.mdx +++ b/versioned_docs/version-2.11/reference/subsystems/junit.mdx @@ -67,7 +67,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.11.1/src/python/pants/jvm/test/junit.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=junit`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=junit`. diff --git a/versioned_docs/version-2.11/reference/subsystems/lambdex.mdx b/versioned_docs/version-2.11/reference/subsystems/lambdex.mdx index 3f92917ad..bd187d067 100644 --- a/versioned_docs/version-2.11/reference/subsystems/lambdex.mdx +++ b/versioned_docs/version-2.11/reference/subsystems/lambdex.mdx @@ -71,7 +71,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=lambdex`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=lambdex`. As explained at https://www.pantsbuild.org/v2.11/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.11/reference/subsystems/mypy-protobuf.mdx b/versioned_docs/version-2.11/reference/subsystems/mypy-protobuf.mdx index a5aa15bdb..9d83072db 100644 --- a/versioned_docs/version-2.11/reference/subsystems/mypy-protobuf.mdx +++ b/versioned_docs/version-2.11/reference/subsystems/mypy-protobuf.mdx @@ -71,7 +71,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=mypy-protobuf`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=mypy-protobuf`. As explained at https://www.pantsbuild.org/v2.11/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.11/reference/subsystems/mypy.mdx b/versioned_docs/version-2.11/reference/subsystems/mypy.mdx index 8846d5786..92807925b 100644 --- a/versioned_docs/version-2.11/reference/subsystems/mypy.mdx +++ b/versioned_docs/version-2.11/reference/subsystems/mypy.mdx @@ -25,7 +25,7 @@ Config section: `[mypy]` default_repr={`False`} > -Don't use MyPy when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 check`. +Don't use MyPy when running `/home/josh/work/scie-pants/dist/pants check`. @@ -93,7 +93,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=mypy`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=mypy`. As explained at https://www.pantsbuild.org/v2.11/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.11/reference/subsystems/pylint.mdx b/versioned_docs/version-2.11/reference/subsystems/pylint.mdx index 113c60869..57bac754d 100644 --- a/versioned_docs/version-2.11/reference/subsystems/pylint.mdx +++ b/versioned_docs/version-2.11/reference/subsystems/pylint.mdx @@ -25,7 +25,7 @@ Config section: `[pylint]` default_repr={`False`} > -Don't use Pylint when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use Pylint when running `/home/josh/work/scie-pants/dist/pants lint`. @@ -81,7 +81,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=pylint`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=pylint`. As explained at https://www.pantsbuild.org/v2.11/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.11/reference/subsystems/pytest.mdx b/versioned_docs/version-2.11/reference/subsystems/pytest.mdx index 0c2909cfe..63a8923b1 100644 --- a/versioned_docs/version-2.11/reference/subsystems/pytest.mdx +++ b/versioned_docs/version-2.11/reference/subsystems/pytest.mdx @@ -81,7 +81,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=pytest`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=pytest`. As explained at https://www.pantsbuild.org/v2.11/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.11/reference/subsystems/python-infer.mdx b/versioned_docs/version-2.11/reference/subsystems/python-infer.mdx index 8e5c417d5..32f8f6bf1 100644 --- a/versioned_docs/version-2.11/reference/subsystems/python-infer.mdx +++ b/versioned_docs/version-2.11/reference/subsystems/python-infer.mdx @@ -91,7 +91,7 @@ If --assets is True, treat valid-looking strings with at least this many forward Infer a target's dependencies on any `__init__.py` files in the packages it is located in (recursively upward in the directory structure). -Even if this is disabled, Pants will still include any ancestor `__init__.py` files, only they will not be 'proper' dependencies, e.g. they will not show up in `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` and their own dependencies will not be used. +Even if this is disabled, Pants will still include any ancestor `__init__.py` files, only they will not be 'proper' dependencies, e.g. they will not show up in `/home/josh/work/scie-pants/dist/pants dependencies` and their own dependencies will not be used. If you have empty `__init__.py` files, it's safe to leave this option off; otherwise, you should enable this option. diff --git a/versioned_docs/version-2.11/reference/subsystems/python.mdx b/versioned_docs/version-2.11/reference/subsystems/python.mdx index c6bd00c4f..9889e71ee 100644 --- a/versioned_docs/version-2.11/reference/subsystems/python.mdx +++ b/versioned_docs/version-2.11/reference/subsystems/python.mdx @@ -89,14 +89,14 @@ A mapping of logical names to lockfile paths used in your project. Many organizations only need a single resolve for their whole project, which is a good default and often the simplest thing to do. However, you may need multiple resolves, such as if you use two conflicting versions of a requirement in your repository. -If you only need a single resolve, run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles` to generate the lockfile. +If you only need a single resolve, run `/home/josh/work/scie-pants/dist/pants generate-lockfiles` to generate the lockfile. If you need multiple resolves: 1. Via this option, define multiple resolve names and their lockfile paths. The names should be meaningful to your repository, such as `data-science` or `pants-plugins`. 2. Set the default with `[python].default_resolve`. 3. Update your `python_requirement` targets with the `resolve` field to declare which resolve they should be available in. They default to `[python].default_resolve`, so you only need to update targets that you want in non-default resolves. (Often you'll set this via the `python_requirements` or `poetry_requirements` target generators) -4. Run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles` to generate the lockfiles. If the results aren't what you'd expect, adjust the prior step. +4. Run `/home/josh/work/scie-pants/dist/pants generate-lockfiles` to generate the lockfiles. If the results aren't what you'd expect, adjust the prior step. 5. Update any targets like `python_source` / `python_sources`, `python_test` / `python_tests`, and `pex_binary` which need to set a non-default resolve with the `resolve` field. If a target can work with multiple resolves, you can either use the `parametrize` mechanism or manually create a distinct target per resolve. See https://www.pantsbuild.org/v2.11/docs/targets for information about `parametrize`. For example: @@ -189,7 +189,7 @@ Finally, installing from a Poetry-generated lockfile is slower than installing f However, Pex lockfile generation is a beta feature. Given how vast the Python packaging ecosystem is, it is possible you may experience edge cases / bugs we haven't yet covered. Bug reports are appreciated! https://github.com/pantsbuild/pants/issues/new/choose -Note that while Pex generates locks in a proprietary JSON format, you can use the `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export` goal for Pants to create a virtual environment for interoperability with tools like IDEs. +Note that while Pex generates locks in a proprietary JSON format, you can use the `/home/josh/work/scie-pants/dist/pants export` goal for Pants to create a virtual environment for interoperability with tools like IDEs. diff --git a/versioned_docs/version-2.11/reference/subsystems/pyupgrade.mdx b/versioned_docs/version-2.11/reference/subsystems/pyupgrade.mdx index f174ffa6c..b16e9d370 100644 --- a/versioned_docs/version-2.11/reference/subsystems/pyupgrade.mdx +++ b/versioned_docs/version-2.11/reference/subsystems/pyupgrade.mdx @@ -25,7 +25,7 @@ Config section: `[pyupgrade]` default_repr={`False`} > -Don't use pyupgrade when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use pyupgrade when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. @@ -93,7 +93,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=pyupgrade`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=pyupgrade`. As explained at https://www.pantsbuild.org/v2.11/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.11/reference/subsystems/scalafmt.mdx b/versioned_docs/version-2.11/reference/subsystems/scalafmt.mdx index b0256ac8d..255cacadd 100644 --- a/versioned_docs/version-2.11/reference/subsystems/scalafmt.mdx +++ b/versioned_docs/version-2.11/reference/subsystems/scalafmt.mdx @@ -25,7 +25,7 @@ Config section: `[scalafmt]` default_repr={`False`} > -Don't use scalafmt when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use scalafmt when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. @@ -67,7 +67,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.11.1/src/python/pants/backend/scala/lint/scalafmt/scalafmt.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalafmt`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=scalafmt`. diff --git a/versioned_docs/version-2.11/reference/subsystems/scalapb.mdx b/versioned_docs/version-2.11/reference/subsystems/scalapb.mdx index c15d18456..bbf0e9cda 100644 --- a/versioned_docs/version-2.11/reference/subsystems/scalapb.mdx +++ b/versioned_docs/version-2.11/reference/subsystems/scalapb.mdx @@ -81,7 +81,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.11.1/src/python/pants/backend/codegen/protobuf/scala/scalapbc.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalapb`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=scalapb`. diff --git a/versioned_docs/version-2.11/reference/subsystems/scalatest.mdx b/versioned_docs/version-2.11/reference/subsystems/scalatest.mdx index 7e4c1400c..d5618b6e7 100644 --- a/versioned_docs/version-2.11/reference/subsystems/scalatest.mdx +++ b/versioned_docs/version-2.11/reference/subsystems/scalatest.mdx @@ -69,7 +69,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.11.1/src/python/pants/backend/scala/subsystems/scalatest.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalatest`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=scalatest`. diff --git a/versioned_docs/version-2.11/reference/subsystems/setuptools.mdx b/versioned_docs/version-2.11/reference/subsystems/setuptools.mdx index 98ab88c12..f00525203 100644 --- a/versioned_docs/version-2.11/reference/subsystems/setuptools.mdx +++ b/versioned_docs/version-2.11/reference/subsystems/setuptools.mdx @@ -59,7 +59,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=setuptools`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=setuptools`. As explained at https://www.pantsbuild.org/v2.11/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.11/reference/subsystems/shellcheck.mdx b/versioned_docs/version-2.11/reference/subsystems/shellcheck.mdx index ea2a466c2..605400902 100644 --- a/versioned_docs/version-2.11/reference/subsystems/shellcheck.mdx +++ b/versioned_docs/version-2.11/reference/subsystems/shellcheck.mdx @@ -25,7 +25,7 @@ Config section: `[shellcheck]` default_repr={`False`} > -Don't use Shellcheck when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use Shellcheck when running `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.11/reference/subsystems/shfmt.mdx b/versioned_docs/version-2.11/reference/subsystems/shfmt.mdx index 1c268fae2..9a272088a 100644 --- a/versioned_docs/version-2.11/reference/subsystems/shfmt.mdx +++ b/versioned_docs/version-2.11/reference/subsystems/shfmt.mdx @@ -25,7 +25,7 @@ Config section: `[shfmt]` default_repr={`False`} > -Don't use shfmt when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use shfmt when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.11/reference/subsystems/terraform-fmt.mdx b/versioned_docs/version-2.11/reference/subsystems/terraform-fmt.mdx index 0ea670e77..92c3c6ec7 100644 --- a/versioned_docs/version-2.11/reference/subsystems/terraform-fmt.mdx +++ b/versioned_docs/version-2.11/reference/subsystems/terraform-fmt.mdx @@ -25,7 +25,7 @@ Config section: `[terraform-fmt]` default_repr={`False`} > -Don't use `terraform fmt` when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use `terraform fmt` when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.11/reference/subsystems/terraform-hcl2-parser.mdx b/versioned_docs/version-2.11/reference/subsystems/terraform-hcl2-parser.mdx index 183d83c92..fba65f5ba 100644 --- a/versioned_docs/version-2.11/reference/subsystems/terraform-hcl2-parser.mdx +++ b/versioned_docs/version-2.11/reference/subsystems/terraform-hcl2-parser.mdx @@ -71,7 +71,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=terraform-hcl2-parser`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=terraform-hcl2-parser`. As explained at https://www.pantsbuild.org/v2.11/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.11/reference/subsystems/terraform-validate.mdx b/versioned_docs/version-2.11/reference/subsystems/terraform-validate.mdx index 0756cde83..89fa2bb81 100644 --- a/versioned_docs/version-2.11/reference/subsystems/terraform-validate.mdx +++ b/versioned_docs/version-2.11/reference/subsystems/terraform-validate.mdx @@ -25,7 +25,7 @@ Config section: `[terraform-validate]` default_repr={`False`} > -Don't use `terraform validate` when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 check`. +Don't use `terraform validate` when running `/home/josh/work/scie-pants/dist/pants check`. diff --git a/versioned_docs/version-2.11/reference/subsystems/twine.mdx b/versioned_docs/version-2.11/reference/subsystems/twine.mdx index 98e6d4830..ead8a3024 100644 --- a/versioned_docs/version-2.11/reference/subsystems/twine.mdx +++ b/versioned_docs/version-2.11/reference/subsystems/twine.mdx @@ -25,7 +25,7 @@ Config section: `[twine]` default_repr={`False`} > -Don't use Twine when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 publish`. +Don't use Twine when running `/home/josh/work/scie-pants/dist/pants publish`. @@ -93,7 +93,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=twine`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=twine`. As explained at https://www.pantsbuild.org/v2.11/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.11/reference/subsystems/yapf.mdx b/versioned_docs/version-2.11/reference/subsystems/yapf.mdx index 7c79f47ed..9d21f54b5 100644 --- a/versioned_docs/version-2.11/reference/subsystems/yapf.mdx +++ b/versioned_docs/version-2.11/reference/subsystems/yapf.mdx @@ -25,7 +25,7 @@ Config section: `[yapf]` default_repr={`False`} > -Don't use yapf when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use yapf when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. @@ -95,7 +95,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=yapf`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=yapf`. As explained at https://www.pantsbuild.org/v2.11/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.11/reference/targets/archive.mdx b/versioned_docs/version-2.11/reference/targets/archive.mdx index eee2b5712..801685458 100644 --- a/versioned_docs/version-2.11/reference/targets/archive.mdx +++ b/versioned_docs/version-2.11/reference/targets/archive.mdx @@ -24,7 +24,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -52,7 +52,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. @@ -65,11 +65,11 @@ Warning: setting this value risks naming collisions with other package targets y default_repr={`None`} > -Addresses to any targets that can be built with `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, e.g. `["project:app"]`. +Addresses to any targets that can be built with `/home/josh/work/scie-pants/dist/pants package`, e.g. `["project:app"]`. -Pants will build the assets as if you had run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`. It will include the results in your archive using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). +Pants will build the assets as if you had run `/home/josh/work/scie-pants/dist/pants package`. It will include the results in your archive using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). -You can include anything that can be built by `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or even another `archive`. +You can include anything that can be built by `/home/josh/work/scie-pants/dist/pants package`, e.g. a `pex_binary`, `python_awslambda`, or even another `archive`. diff --git a/versioned_docs/version-2.11/reference/targets/deploy_jar.mdx b/versioned_docs/version-2.11/reference/targets/deploy_jar.mdx index 88a13111f..5fccca533 100644 --- a/versioned_docs/version-2.11/reference/targets/deploy_jar.mdx +++ b/versioned_docs/version-2.11/reference/targets/deploy_jar.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.experimental.java` @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -52,9 +52,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -73,7 +73,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. diff --git a/versioned_docs/version-2.11/reference/targets/docker_image.mdx b/versioned_docs/version-2.11/reference/targets/docker_image.mdx index ed5088831..7583625bc 100644 --- a/versioned_docs/version-2.11/reference/targets/docker_image.mdx +++ b/versioned_docs/version-2.11/reference/targets/docker_image.mdx @@ -39,7 +39,7 @@ Backend: `pants.backend.docker` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -52,7 +52,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -78,9 +78,9 @@ Use `[docker].build_args` to set default build args for all images. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -275,7 +275,7 @@ See [Docker documentation](https://docs.docker.com/develop/develop-images/build_ default_repr={`False`} > -If set to true, do not push this image to registries when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 publish`. +If set to true, do not push this image to registries when running `/home/josh/work/scie-pants/dist/pants publish`. diff --git a/versioned_docs/version-2.11/reference/targets/experimental_run_shell_command.mdx b/versioned_docs/version-2.11/reference/targets/experimental_run_shell_command.mdx index 1c5143120..874b73543 100644 --- a/versioned_docs/version-2.11/reference/targets/experimental_run_shell_command.mdx +++ b/versioned_docs/version-2.11/reference/targets/experimental_run_shell_command.mdx @@ -37,7 +37,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -50,7 +50,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -63,9 +63,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.11/reference/targets/experimental_shell_command.mdx b/versioned_docs/version-2.11/reference/targets/experimental_shell_command.mdx index 0ea663f9c..b07d86f3f 100644 --- a/versioned_docs/version-2.11/reference/targets/experimental_shell_command.mdx +++ b/versioned_docs/version-2.11/reference/targets/experimental_shell_command.mdx @@ -41,7 +41,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -54,7 +54,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -67,9 +67,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.11/reference/targets/file.mdx b/versioned_docs/version-2.11/reference/targets/file.mdx index 17ea74501..4966422b0 100644 --- a/versioned_docs/version-2.11/reference/targets/file.mdx +++ b/versioned_docs/version-2.11/reference/targets/file.mdx @@ -26,7 +26,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -52,9 +52,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.11/reference/targets/files.mdx b/versioned_docs/version-2.11/reference/targets/files.mdx index 358e366f4..3916bf5de 100644 --- a/versioned_docs/version-2.11/reference/targets/files.mdx +++ b/versioned_docs/version-2.11/reference/targets/files.mdx @@ -24,7 +24,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -94,9 +94,9 @@ You can specify the same file name in multiple keys, so long as you don't o Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.11/reference/targets/go_binary.mdx b/versioned_docs/version-2.11/reference/targets/go_binary.mdx index 3f172d7d0..26351b1ff 100644 --- a/versioned_docs/version-2.11/reference/targets/go_binary.mdx +++ b/versioned_docs/version-2.11/reference/targets/go_binary.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.go` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -52,7 +52,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. diff --git a/versioned_docs/version-2.11/reference/targets/go_mod.mdx b/versioned_docs/version-2.11/reference/targets/go_mod.mdx index 605db3545..caeac0e75 100644 --- a/versioned_docs/version-2.11/reference/targets/go_mod.mdx +++ b/versioned_docs/version-2.11/reference/targets/go_mod.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.go` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.11/reference/targets/go_package.mdx b/versioned_docs/version-2.11/reference/targets/go_package.mdx index 2a3ccd352..a11b5b419 100644 --- a/versioned_docs/version-2.11/reference/targets/go_package.mdx +++ b/versioned_docs/version-2.11/reference/targets/go_package.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.experimental.go` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -52,9 +52,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.11/reference/targets/go_third_party_package.mdx b/versioned_docs/version-2.11/reference/targets/go_third_party_package.mdx index 326de44c4..3dea74496 100644 --- a/versioned_docs/version-2.11/reference/targets/go_third_party_package.mdx +++ b/versioned_docs/version-2.11/reference/targets/go_third_party_package.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.go` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -54,9 +54,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.11/reference/targets/helm_chart.mdx b/versioned_docs/version-2.11/reference/targets/helm_chart.mdx index 263ad148b..54f5c679b 100644 --- a/versioned_docs/version-2.11/reference/targets/helm_chart.mdx +++ b/versioned_docs/version-2.11/reference/targets/helm_chart.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.helm` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -76,9 +76,9 @@ Example: `sources=['example.ext', 'test_*.ext', '!test_ignore.ext']`. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -99,7 +99,7 @@ If undefined, this will use the path to the BUILD file, For example, `src/charts Regardless of whether you use the default or set this field, the path will end with Helms's file format of `-.tgz`, where `chart_name` and `chart_version` are the values extracted from the Chart.yaml file. So, using the default for this field, the target `src/charts/mychart:tgt_name` might have a final path like `src.charts.mychart/tgt_name/mychart-0.1.0.tgz`. -When running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. @@ -123,7 +123,7 @@ If set to true, enables strict linting of this Helm chart default_repr={`False`} > -If set to true, do not push this helm chart to registries when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 publish`. +If set to true, do not push this helm chart to registries when running `/home/josh/work/scie-pants/dist/pants publish`. diff --git a/versioned_docs/version-2.11/reference/targets/java_source.mdx b/versioned_docs/version-2.11/reference/targets/java_source.mdx index 2b5048cc5..e566d7228 100644 --- a/versioned_docs/version-2.11/reference/targets/java_source.mdx +++ b/versioned_docs/version-2.11/reference/targets/java_source.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.java` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.11/reference/targets/java_sources.mdx b/versioned_docs/version-2.11/reference/targets/java_sources.mdx index e670a1e8f..d6a815f47 100644 --- a/versioned_docs/version-2.11/reference/targets/java_sources.mdx +++ b/versioned_docs/version-2.11/reference/targets/java_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.java` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -65,9 +65,9 @@ Example: `sources=['example.ext', 'test_*.ext', '!test_ignore.ext']`. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.11/reference/targets/junit_test.mdx b/versioned_docs/version-2.11/reference/targets/junit_test.mdx index cfd25b3f3..15071c6c8 100644 --- a/versioned_docs/version-2.11/reference/targets/junit_test.mdx +++ b/versioned_docs/version-2.11/reference/targets/junit_test.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.java` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -63,9 +63,9 @@ Path is relative to the BUILD file's directory, e.g. `source='example.ext'` Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.11/reference/targets/junit_tests.mdx b/versioned_docs/version-2.11/reference/targets/junit_tests.mdx index 659e2bf59..7e454997b 100644 --- a/versioned_docs/version-2.11/reference/targets/junit_tests.mdx +++ b/versioned_docs/version-2.11/reference/targets/junit_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.java` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -65,9 +65,9 @@ Example: `sources=['example.ext', 'test_*.ext', '!test_ignore.ext']`. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.11/reference/targets/jvm_artifact.mdx b/versioned_docs/version-2.11/reference/targets/jvm_artifact.mdx index 5ebb71056..8770aaf7b 100644 --- a/versioned_docs/version-2.11/reference/targets/jvm_artifact.mdx +++ b/versioned_docs/version-2.11/reference/targets/jvm_artifact.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.java` @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.11/reference/targets/jvm_war.mdx b/versioned_docs/version-2.11/reference/targets/jvm_war.mdx index 8f5b32af9..97ec21a70 100644 --- a/versioned_docs/version-2.11/reference/targets/jvm_war.mdx +++ b/versioned_docs/version-2.11/reference/targets/jvm_war.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.java` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -74,9 +74,9 @@ A list of addresses to `resources` and `files` targets with content to place in Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -106,7 +106,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. diff --git a/versioned_docs/version-2.11/reference/targets/pants_requirements.mdx b/versioned_docs/version-2.11/reference/targets/pants_requirements.mdx index 643b4f4d9..e3db65610 100644 --- a/versioned_docs/version-2.11/reference/targets/pants_requirements.mdx +++ b/versioned_docs/version-2.11/reference/targets/pants_requirements.mdx @@ -30,7 +30,7 @@ Backend: `pants.backend.plugin_development` @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.11/reference/targets/pex_binaries.mdx b/versioned_docs/version-2.11/reference/targets/pex_binaries.mdx index 33026144c..af5795761 100644 --- a/versioned_docs/version-2.11/reference/targets/pex_binaries.mdx +++ b/versioned_docs/version-2.11/reference/targets/pex_binaries.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -132,9 +132,9 @@ All dependencies must share the same value for their `resolve` field. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.11/reference/targets/pex_binary.mdx b/versioned_docs/version-2.11/reference/targets/pex_binary.mdx index 00558b167..3b7a8d753 100644 --- a/versioned_docs/version-2.11/reference/targets/pex_binary.mdx +++ b/versioned_docs/version-2.11/reference/targets/pex_binary.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -86,9 +86,9 @@ All dependencies must share the same value for their `resolve` field. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -326,7 +326,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. diff --git a/versioned_docs/version-2.11/reference/targets/pipenv_requirements.mdx b/versioned_docs/version-2.11/reference/targets/pipenv_requirements.mdx index d40fcc1e4..ac468ba54 100644 --- a/versioned_docs/version-2.11/reference/targets/pipenv_requirements.mdx +++ b/versioned_docs/version-2.11/reference/targets/pipenv_requirements.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.11/reference/targets/poetry_requirements.mdx b/versioned_docs/version-2.11/reference/targets/poetry_requirements.mdx index cbbdd8e7d..30bf28543 100644 --- a/versioned_docs/version-2.11/reference/targets/poetry_requirements.mdx +++ b/versioned_docs/version-2.11/reference/targets/poetry_requirements.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.11/reference/targets/protobuf_source.mdx b/versioned_docs/version-2.11/reference/targets/protobuf_source.mdx index 89d941174..1fa649318 100644 --- a/versioned_docs/version-2.11/reference/targets/protobuf_source.mdx +++ b/versioned_docs/version-2.11/reference/targets/protobuf_source.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.codegen.protobuf.python Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -54,9 +54,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.11/reference/targets/protobuf_sources.mdx b/versioned_docs/version-2.11/reference/targets/protobuf_sources.mdx index ca7d89005..f27d77874 100644 --- a/versioned_docs/version-2.11/reference/targets/protobuf_sources.mdx +++ b/versioned_docs/version-2.11/reference/targets/protobuf_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.codegen.protobuf.python Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -205,9 +205,9 @@ Whether to generate gRPC code or not. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.11/reference/targets/pyoxidizer_binary.mdx b/versioned_docs/version-2.11/reference/targets/pyoxidizer_binary.mdx index 7521af761..a78052950 100644 --- a/versioned_docs/version-2.11/reference/targets/pyoxidizer_binary.mdx +++ b/versioned_docs/version-2.11/reference/targets/pyoxidizer_binary.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.python.pac Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -58,7 +58,7 @@ If undefined, this will use the path to the BUILD file, followed by the target n Regardless of whether you use the default or set this field, the path will end with PyOxidizer's file format of `/{debug,release}/install/`, where `platform` is a Rust platform triplet like `aarch-64-apple-darwin` and `binary_name` is the `name` of the `pyoxidizer_target`. So, using the default for this field, the target `src/python/project:bin` might have a final path like `src.python.project/bin/aarch-64-apple-darwin/release/bin`. -When running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. diff --git a/versioned_docs/version-2.11/reference/targets/python_awslambda.mdx b/versioned_docs/version-2.11/reference/targets/python_awslambda.mdx index 15ea769b8..5221c53a5 100644 --- a/versioned_docs/version-2.11/reference/targets/python_awslambda.mdx +++ b/versioned_docs/version-2.11/reference/targets/python_awslambda.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.awslambda.python` @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -54,7 +54,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. @@ -69,9 +69,9 @@ Warning: setting this value risks naming collisions with other package targets y Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.11/reference/targets/python_distribution.mdx b/versioned_docs/version-2.11/reference/targets/python_distribution.mdx index 2ea0d536d..bf6df82f6 100644 --- a/versioned_docs/version-2.11/reference/targets/python_distribution.mdx +++ b/versioned_docs/version-2.11/reference/targets/python_distribution.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -52,9 +52,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -89,7 +89,7 @@ Note that Pants will assume that any value that either starts with `:` or has `/ Pants will attempt to infer dependencies, which you can confirm by running: ``` -/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies +/home/josh/work/scie-pants/dist/pants dependencies ``` diff --git a/versioned_docs/version-2.11/reference/targets/python_google_cloud_function.mdx b/versioned_docs/version-2.11/reference/targets/python_google_cloud_function.mdx index 13f83bc8f..47e5cc797 100644 --- a/versioned_docs/version-2.11/reference/targets/python_google_cloud_function.mdx +++ b/versioned_docs/version-2.11/reference/targets/python_google_cloud_function.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.google_cloud_function.p Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -54,7 +54,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. @@ -69,9 +69,9 @@ Warning: setting this value risks naming collisions with other package targets y Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.11/reference/targets/python_requirement.mdx b/versioned_docs/version-2.11/reference/targets/python_requirement.mdx index 028f0cab6..28bd38d90 100644 --- a/versioned_docs/version-2.11/reference/targets/python_requirement.mdx +++ b/versioned_docs/version-2.11/reference/targets/python_requirement.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -54,9 +54,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.11/reference/targets/python_requirements.mdx b/versioned_docs/version-2.11/reference/targets/python_requirements.mdx index 0ef2d3cce..73dbabfc2 100644 --- a/versioned_docs/version-2.11/reference/targets/python_requirements.mdx +++ b/versioned_docs/version-2.11/reference/targets/python_requirements.mdx @@ -30,7 +30,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.11/reference/targets/python_source.mdx b/versioned_docs/version-2.11/reference/targets/python_source.mdx index 756754d5b..9761bc430 100644 --- a/versioned_docs/version-2.11/reference/targets/python_source.mdx +++ b/versioned_docs/version-2.11/reference/targets/python_source.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -69,9 +69,9 @@ See https://www.pantsbuild.org/v2.11/docs/python-interpreter-compatibility for h Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.11/reference/targets/python_sources.mdx b/versioned_docs/version-2.11/reference/targets/python_sources.mdx index c4119324b..2b0a495b8 100644 --- a/versioned_docs/version-2.11/reference/targets/python_sources.mdx +++ b/versioned_docs/version-2.11/reference/targets/python_sources.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -231,9 +231,9 @@ All dependencies must share the same value for their `resolve` field. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.11/reference/targets/python_test.mdx b/versioned_docs/version-2.11/reference/targets/python_test.mdx index 73a056cee..a33818c1d 100644 --- a/versioned_docs/version-2.11/reference/targets/python_test.mdx +++ b/versioned_docs/version-2.11/reference/targets/python_test.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -54,9 +54,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -99,11 +99,11 @@ If unset, will default to `[pytest].timeout_default`; if that option is also uns default_repr={`None`} > -Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run. +Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/pants package` goal and whose resulting artifacts should be included in the test run. -Pants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). +Pants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). -You can include anything that can be built by `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`. +You can include anything that can be built by `/home/josh/work/scie-pants/dist/pants package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`. @@ -157,9 +157,9 @@ If true, don't run this target's tests. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.11/reference/targets/python_test_utils.mdx b/versioned_docs/version-2.11/reference/targets/python_test_utils.mdx index 15c096d99..b7a3447e2 100644 --- a/versioned_docs/version-2.11/reference/targets/python_test_utils.mdx +++ b/versioned_docs/version-2.11/reference/targets/python_test_utils.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -231,9 +231,9 @@ All dependencies must share the same value for their `resolve` field. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.11/reference/targets/python_tests.mdx b/versioned_docs/version-2.11/reference/targets/python_tests.mdx index 2c2522571..f093c82cc 100644 --- a/versioned_docs/version-2.11/reference/targets/python_tests.mdx +++ b/versioned_docs/version-2.11/reference/targets/python_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -214,9 +214,9 @@ If true, don't run MyPy on this target's code. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -259,11 +259,11 @@ If unset, will default to `[pytest].timeout_default`; if that option is also uns default_repr={`None`} > -Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run. +Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/pants package` goal and whose resulting artifacts should be included in the test run. -Pants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). +Pants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). -You can include anything that can be built by `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`. +You can include anything that can be built by `/home/josh/work/scie-pants/dist/pants package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`. diff --git a/versioned_docs/version-2.11/reference/targets/relocated_files.mdx b/versioned_docs/version-2.11/reference/targets/relocated_files.mdx index 73ed0c422..b920f40cd 100644 --- a/versioned_docs/version-2.11/reference/targets/relocated_files.mdx +++ b/versioned_docs/version-2.11/reference/targets/relocated_files.mdx @@ -61,7 +61,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -74,7 +74,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.11/reference/targets/resource.mdx b/versioned_docs/version-2.11/reference/targets/resource.mdx index affd26e09..68152301f 100644 --- a/versioned_docs/version-2.11/reference/targets/resource.mdx +++ b/versioned_docs/version-2.11/reference/targets/resource.mdx @@ -26,7 +26,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -52,9 +52,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.11/reference/targets/resources.mdx b/versioned_docs/version-2.11/reference/targets/resources.mdx index 5c0a7d32d..659ff2d46 100644 --- a/versioned_docs/version-2.11/reference/targets/resources.mdx +++ b/versioned_docs/version-2.11/reference/targets/resources.mdx @@ -24,7 +24,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -94,9 +94,9 @@ You can specify the same file name in multiple keys, so long as you don't o Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.11/reference/targets/scala_junit_test.mdx b/versioned_docs/version-2.11/reference/targets/scala_junit_test.mdx index b40fce477..e2fdbbeab 100644 --- a/versioned_docs/version-2.11/reference/targets/scala_junit_test.mdx +++ b/versioned_docs/version-2.11/reference/targets/scala_junit_test.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.scala` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.11/reference/targets/scala_junit_tests.mdx b/versioned_docs/version-2.11/reference/targets/scala_junit_tests.mdx index 95bb49029..72fae4e86 100644 --- a/versioned_docs/version-2.11/reference/targets/scala_junit_tests.mdx +++ b/versioned_docs/version-2.11/reference/targets/scala_junit_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.scala` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -65,9 +65,9 @@ Example: `sources=['example.ext', 'test_*.ext', '!test_ignore.ext']`. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.11/reference/targets/scala_source.mdx b/versioned_docs/version-2.11/reference/targets/scala_source.mdx index 588e11fcc..06745d7a7 100644 --- a/versioned_docs/version-2.11/reference/targets/scala_source.mdx +++ b/versioned_docs/version-2.11/reference/targets/scala_source.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.scala` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.11/reference/targets/scala_sources.mdx b/versioned_docs/version-2.11/reference/targets/scala_sources.mdx index 6099096cc..293b301dc 100644 --- a/versioned_docs/version-2.11/reference/targets/scala_sources.mdx +++ b/versioned_docs/version-2.11/reference/targets/scala_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.scala` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -77,9 +77,9 @@ If true, don't run `scalafmt` on this target's code. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.11/reference/targets/scalac_plugin.mdx b/versioned_docs/version-2.11/reference/targets/scalac_plugin.mdx index 53c633e66..2d5fa0e60 100644 --- a/versioned_docs/version-2.11/reference/targets/scalac_plugin.mdx +++ b/versioned_docs/version-2.11/reference/targets/scalac_plugin.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.scala` @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.11/reference/targets/scalatest_test.mdx b/versioned_docs/version-2.11/reference/targets/scalatest_test.mdx index 59b2cfaab..b90a50990 100644 --- a/versioned_docs/version-2.11/reference/targets/scalatest_test.mdx +++ b/versioned_docs/version-2.11/reference/targets/scalatest_test.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.scala` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.11/reference/targets/scalatest_tests.mdx b/versioned_docs/version-2.11/reference/targets/scalatest_tests.mdx index d281116bc..2eab8a3e7 100644 --- a/versioned_docs/version-2.11/reference/targets/scalatest_tests.mdx +++ b/versioned_docs/version-2.11/reference/targets/scalatest_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.scala` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -65,9 +65,9 @@ Example: `sources=['example.ext', 'test_*.ext', '!test_ignore.ext']`. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.11/reference/targets/shell_source.mdx b/versioned_docs/version-2.11/reference/targets/shell_source.mdx index b1404cf3b..576500bf0 100644 --- a/versioned_docs/version-2.11/reference/targets/shell_source.mdx +++ b/versioned_docs/version-2.11/reference/targets/shell_source.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.11/reference/targets/shell_sources.mdx b/versioned_docs/version-2.11/reference/targets/shell_sources.mdx index f32dff3e1..9827060a3 100644 --- a/versioned_docs/version-2.11/reference/targets/shell_sources.mdx +++ b/versioned_docs/version-2.11/reference/targets/shell_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -118,9 +118,9 @@ If true, don't run shfmt on this target's code. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.11/reference/targets/shunit2_test.mdx b/versioned_docs/version-2.11/reference/targets/shunit2_test.mdx index 8e3ef017f..5167da6d7 100644 --- a/versioned_docs/version-2.11/reference/targets/shunit2_test.mdx +++ b/versioned_docs/version-2.11/reference/targets/shunit2_test.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -67,9 +67,9 @@ Path is relative to the BUILD file's directory, e.g. `source='example.ext'` Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -119,11 +119,11 @@ Which shell to run the tests with. If unspecified, Pants will look for a shebang default_repr={`None`} > -Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run. +Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/pants package` goal and whose resulting artifacts should be included in the test run. -Pants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). +Pants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). -You can include anything that can be built by `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`. +You can include anything that can be built by `/home/josh/work/scie-pants/dist/pants package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`. diff --git a/versioned_docs/version-2.11/reference/targets/shunit2_tests.mdx b/versioned_docs/version-2.11/reference/targets/shunit2_tests.mdx index 915fc1b7b..d79bd6151 100644 --- a/versioned_docs/version-2.11/reference/targets/shunit2_tests.mdx +++ b/versioned_docs/version-2.11/reference/targets/shunit2_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -118,9 +118,9 @@ If true, don't run shfmt on this target's code. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -170,11 +170,11 @@ Which shell to run the tests with. If unspecified, Pants will look for a shebang default_repr={`None`} > -Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run. +Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/pants package` goal and whose resulting artifacts should be included in the test run. -Pants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). +Pants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). -You can include anything that can be built by `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`. +You can include anything that can be built by `/home/josh/work/scie-pants/dist/pants package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`. diff --git a/versioned_docs/version-2.11/reference/targets/target.mdx b/versioned_docs/version-2.11/reference/targets/target.mdx index 5c94c6f5e..5bc7335d0 100644 --- a/versioned_docs/version-2.11/reference/targets/target.mdx +++ b/versioned_docs/version-2.11/reference/targets/target.mdx @@ -26,7 +26,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -52,9 +52,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.11/reference/targets/terraform_module.mdx b/versioned_docs/version-2.11/reference/targets/terraform_module.mdx index 7c40d4c70..c0ff34a11 100644 --- a/versioned_docs/version-2.11/reference/targets/terraform_module.mdx +++ b/versioned_docs/version-2.11/reference/targets/terraform_module.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.terraform` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -54,9 +54,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.11/reference/targets/thrift_source.mdx b/versioned_docs/version-2.11/reference/targets/thrift_source.mdx index 4eef6214f..e66ed9156 100644 --- a/versioned_docs/version-2.11/reference/targets/thrift_source.mdx +++ b/versioned_docs/version-2.11/reference/targets/thrift_source.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.codegen.thrift.apache.p Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -52,9 +52,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.11/reference/targets/thrift_sources.mdx b/versioned_docs/version-2.11/reference/targets/thrift_sources.mdx index 52af1ec87..83dfbb4e8 100644 --- a/versioned_docs/version-2.11/reference/targets/thrift_sources.mdx +++ b/versioned_docs/version-2.11/reference/targets/thrift_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.codegen.thrift.apache.p Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -109,9 +109,9 @@ All dependencies must share the same value for their `resolve` field. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.11/docs/targets#target-addresses and https://www.pantsbuild.org/v2.11/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.12/reference/global-options.mdx b/versioned_docs/version-2.12/reference/global-options.mdx index dd3ad74bb..0c03f44db 100644 --- a/versioned_docs/version-2.12/reference/global-options.mdx +++ b/versioned_docs/version-2.12/reference/global-options.mdx @@ -314,9 +314,9 @@ ignore_warnings = [ Use this Pants version. Note that Pants only uses this to verify that you are using the requested version, as Pants cannot dynamically change the version it is using once the program is already running. -If you use the `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64` script from https://www.pantsbuild.org/v2.12/docs/installation, however, changing the value in your `pants.toml` will cause the new version to be installed and run automatically. +If you use the `/home/josh/work/scie-pants/dist/pants` script from https://www.pantsbuild.org/v2.12/docs/installation, however, changing the value in your `pants.toml` will cause the new version to be installed and run automatically. -Run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --version` to check what is being used. +Run `/home/josh/work/scie-pants/dist/pants --version` to check what is being used. @@ -798,7 +798,7 @@ Whether or not to use nailgun to run JVM requests that are marked as supporting default_repr={`3`} > -The time in seconds to wait when gracefully shutting down an interactive process (such as one opened using `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 run`) before killing it. +The time in seconds to wait when gracefully shutting down an interactive process (such as one opened using `/home/josh/work/scie-pants/dist/pants run`) before killing it. diff --git a/versioned_docs/version-2.12/reference/goals/experimental-bsp.mdx b/versioned_docs/version-2.12/reference/goals/experimental-bsp.mdx index d6c922d3b..9601d9650 100644 --- a/versioned_docs/version-2.12/reference/goals/experimental-bsp.mdx +++ b/versioned_docs/version-2.12/reference/goals/experimental-bsp.mdx @@ -79,7 +79,7 @@ Run the Build Server Protocol server. Pants will receive BSP RPC requests via th Environment variables to set in the BSP runner script when setting up BSP in a repository. Entries are either strings in the form `ENV_VAR=value` to set an explicit value; or just `ENV_VAR` to copy the value from Pants' own environment when the experimental-bsp goal was run. -This option only takes effect when the BSP runner script is written. If the option changes, you must run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 experimental-bsp` again to write a new copy of the BSP runner script. +This option only takes effect when the BSP runner script is written. If the option changes, you must run `/home/josh/work/scie-pants/dist/pants experimental-bsp` again to write a new copy of the BSP runner script. Note: The environment variables passed to the Pants BSP server will be those set for your IDE and not your shell. For example, on macOS, the IDE is generally launched by `launchd` after clicking on a Dock icon, and not from the shell. Thus, any environment variables set for your shell will likely not be seen by the Pants BSP server. At the very least, on macOS consider writing an explicit PATH into the BSP runner script via this option. diff --git a/versioned_docs/version-2.12/reference/goals/generate-lockfiles.mdx b/versioned_docs/version-2.12/reference/goals/generate-lockfiles.mdx index b08aaff9a..90348459c 100644 --- a/versioned_docs/version-2.12/reference/goals/generate-lockfiles.mdx +++ b/versioned_docs/version-2.12/reference/goals/generate-lockfiles.mdx @@ -33,7 +33,7 @@ Only generate lockfiles for the specified resolve(s). Resolves are the logical names for the different lockfiles used in your project. For your own code's dependencies, these come from the option `[python].resolves`. For tool lockfiles, resolve names are the options scope for that tool such as `black`, `pytest`, and `mypy-protobuf`. -For example, you can run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=black --resolve=pytest --resolve=data-science` to only generate lockfiles for those two tools and your resolve named `data-science`. +For example, you can run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=black --resolve=pytest --resolve=data-science` to only generate lockfiles for those two tools and your resolve named `data-science`. If you specify an invalid resolve name, like 'fake', Pants will output all possible values. @@ -51,7 +51,7 @@ If not specified, Pants will generate lockfiles for all resolves. default_repr={`None`} > -If set, lockfile headers will say to run this command to regenerate the lockfile, rather than running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=` like normal. +If set, lockfile headers will say to run this command to regenerate the lockfile, rather than running `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=` like normal. diff --git a/versioned_docs/version-2.12/reference/help-all.json b/versioned_docs/version-2.12/reference/help-all.json index 7c7175620..f739b4447 100644 --- a/versioned_docs/version-2.12/reference/help-all.json +++ b/versioned_docs/version-2.12/reference/help-all.json @@ -205,7 +205,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -213,7 +213,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -221,7 +221,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -229,7 +229,7 @@ { "alias": "packages", "default": null, - "description": "Addresses to any targets that can be built with `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, e.g. `[\"project:app\"]`.\n\nPants will build the assets as if you had run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`. It will include the results in your archive using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or even another `archive`.", + "description": "Addresses to any targets that can be built with `/home/josh/work/scie-pants/dist/pants package`, e.g. `[\"project:app\"]`.\n\nPants will build the assets as if you had run `/home/josh/work/scie-pants/dist/pants package`. It will include the results in your archive using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `/home/josh/work/scie-pants/dist/pants package`, e.g. a `pex_binary`, `python_awslambda`, or even another `archive`.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -261,7 +261,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -269,7 +269,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -277,7 +277,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -285,7 +285,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -333,7 +333,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -341,7 +341,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -357,7 +357,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -437,7 +437,7 @@ { "alias": "skip_push", "default": "False", - "description": "If set to true, do not push this image to registries when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 publish`.", + "description": "If set to true, do not push this image to registries when running `/home/josh/work/scie-pants/dist/pants publish`.", "provider": "", "required": false, "type_hint": "bool" @@ -477,7 +477,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -485,7 +485,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -493,7 +493,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -525,7 +525,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -533,7 +533,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -541,7 +541,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -597,7 +597,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -605,7 +605,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -613,7 +613,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -637,7 +637,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -645,7 +645,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -669,7 +669,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -685,7 +685,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -693,7 +693,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -701,7 +701,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -733,7 +733,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -741,7 +741,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -757,7 +757,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -765,7 +765,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -773,7 +773,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -821,7 +821,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -829,7 +829,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -837,7 +837,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -861,7 +861,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -869,7 +869,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -917,7 +917,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -925,7 +925,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -949,7 +949,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -957,7 +957,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built directory tree should be located.\n\nIf undefined, this will use the path to the BUILD file, For example, `src/charts/mychart:tgt_name` would be `src.charts.mychart/tgt_name/`.\n\nRegardless of whether you use the default or set this field, the path will end with Helms's file format of `-.tgz`, where `chart_name` and `chart_version` are the values extracted from the Chart.yaml file. So, using the default for this field, the target `src/charts/mychart:tgt_name` might have a final path like `src.charts.mychart/tgt_name/mychart-0.1.0.tgz`.\n\nWhen running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built directory tree should be located.\n\nIf undefined, this will use the path to the BUILD file, For example, `src/charts/mychart:tgt_name` would be `src.charts.mychart/tgt_name/`.\n\nRegardless of whether you use the default or set this field, the path will end with Helms's file format of `-.tgz`, where `chart_name` and `chart_version` are the values extracted from the Chart.yaml file. So, using the default for this field, the target `src/charts/mychart:tgt_name` might have a final path like `src.charts.mychart/tgt_name/mychart-0.1.0.tgz`.\n\nWhen running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -989,7 +989,7 @@ { "alias": "skip_push", "default": "False", - "description": "If set to true, do not push this helm chart to registries when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 publish`.", + "description": "If set to true, do not push this helm chart to registries when running `/home/josh/work/scie-pants/dist/pants publish`.", "provider": "", "required": false, "type_hint": "bool" @@ -1005,7 +1005,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -1013,7 +1013,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -1029,7 +1029,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -1045,7 +1045,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -1053,7 +1053,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -1069,7 +1069,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -1077,7 +1077,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -1093,7 +1093,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -1101,7 +1101,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -1109,7 +1109,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -1165,7 +1165,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -1173,7 +1173,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -1197,7 +1197,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -1237,7 +1237,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -1245,7 +1245,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -1261,7 +1261,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -1301,7 +1301,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -1309,7 +1309,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -1325,7 +1325,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -1365,7 +1365,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -1373,7 +1373,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -1453,7 +1453,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -1461,7 +1461,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -1485,7 +1485,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -1501,7 +1501,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -1517,7 +1517,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -1525,7 +1525,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -1533,7 +1533,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -1597,7 +1597,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -1605,7 +1605,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -1629,7 +1629,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -1677,7 +1677,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -1685,7 +1685,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -1725,7 +1725,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -1733,7 +1733,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -1765,7 +1765,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -1773,7 +1773,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -1813,7 +1813,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -1933,7 +1933,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -1941,7 +1941,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -1965,7 +1965,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -2093,7 +2093,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -2109,7 +2109,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -2117,7 +2117,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -2173,7 +2173,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -2181,7 +2181,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -2237,7 +2237,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -2245,7 +2245,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -2253,7 +2253,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -2341,7 +2341,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -2349,7 +2349,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -2437,7 +2437,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -2453,7 +2453,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -2461,7 +2461,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -2469,7 +2469,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built directory tree should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:bin` would be `src.python.project/bin/`.\n\nRegardless of whether you use the default or set this field, the path will end with PyOxidizer's file format of `/{debug,release}/install/`, where `platform` is a Rust platform triplet like `aarch-64-apple-darwin` and `binary_name` is the `name` of the `pyoxidizer_target`. So, using the default for this field, the target `src/python/project:bin` might have a final path like `src.python.project/bin/aarch-64-apple-darwin/release/bin`.\n\nWhen running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built directory tree should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:bin` would be `src.python.project/bin/`.\n\nRegardless of whether you use the default or set this field, the path will end with PyOxidizer's file format of `/{debug,release}/install/`, where `platform` is a Rust platform triplet like `aarch-64-apple-darwin` and `binary_name` is the `name` of the `pyoxidizer_target`. So, using the default for this field, the target `src/python/project:bin` might have a final path like `src.python.project/bin/aarch-64-apple-darwin/release/bin`.\n\nWhen running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -2517,7 +2517,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -2525,7 +2525,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -2533,7 +2533,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -2541,7 +2541,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -2597,7 +2597,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -2605,7 +2605,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -2613,7 +2613,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -2621,7 +2621,7 @@ { "alias": "entry_points", "default": null, - "description": "Any entry points, such as `console_scripts` and `gui_scripts`.\n\nSpecify as a nested dictionary, with a dictionary for each type of entry point, e.g. `console_scripts` vs. `gui_scripts`. Each dictionary maps the entry point name to either a setuptools entry point (\"path.to.module:func\") or a Pants target address to a pex_binary target.\n\n Example:\n\n entry_points={\n \"console_scripts\": {\n \"my-script\": \"project.app:main\",\n \"another-script\": \"project/subdir:pex_binary_tgt\"\n }\n }\n\nNote that Pants will assume that any value that either starts with `:` or has `/` in it, is a target address to a pex_binary target. Otherwise, it will assume it's a setuptools entry point as defined by https://packaging.python.org/specifications/entry-points/#entry-points-specification. Use `//` as a prefix for target addresses if you need to disambiguate.\n\nPants will attempt to infer dependencies, which you can confirm by running:\n\n /home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies ", + "description": "Any entry points, such as `console_scripts` and `gui_scripts`.\n\nSpecify as a nested dictionary, with a dictionary for each type of entry point, e.g. `console_scripts` vs. `gui_scripts`. Each dictionary maps the entry point name to either a setuptools entry point (\"path.to.module:func\") or a Pants target address to a pex_binary target.\n\n Example:\n\n entry_points={\n \"console_scripts\": {\n \"my-script\": \"project.app:main\",\n \"another-script\": \"project/subdir:pex_binary_tgt\"\n }\n }\n\nNote that Pants will assume that any value that either starts with `:` or has `/` in it, is a target address to a pex_binary target. Otherwise, it will assume it's a setuptools entry point as defined by https://packaging.python.org/specifications/entry-points/#entry-points-specification. Use `//` as a prefix for target addresses if you need to disambiguate.\n\nPants will attempt to infer dependencies, which you can confirm by running:\n\n /home/josh/work/scie-pants/dist/pants dependencies ", "provider": "", "required": false, "type_hint": "Dict[str, Dict[str, str]] | None" @@ -2709,7 +2709,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -2717,7 +2717,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -2725,7 +2725,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -2733,7 +2733,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -2789,7 +2789,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -2797,7 +2797,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -2805,7 +2805,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -2853,7 +2853,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -2861,7 +2861,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -2917,7 +2917,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -2925,7 +2925,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -2941,7 +2941,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -3053,7 +3053,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -3061,7 +3061,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -3173,7 +3173,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -3197,7 +3197,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -3205,7 +3205,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -3213,7 +3213,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -3237,7 +3237,7 @@ { "alias": "runtime_package_dependencies", "default": null, - "description": "Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`.", + "description": "Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/pants package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `/home/josh/work/scie-pants/dist/pants package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -3269,7 +3269,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -3373,7 +3373,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -3381,7 +3381,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -3493,7 +3493,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -3517,7 +3517,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -3525,7 +3525,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -3629,7 +3629,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -3653,7 +3653,7 @@ { "alias": "runtime_package_dependencies", "default": null, - "description": "Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`.", + "description": "Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/pants package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `/home/josh/work/scie-pants/dist/pants package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -3693,7 +3693,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -3701,7 +3701,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -3741,7 +3741,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -3749,7 +3749,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -3757,7 +3757,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -3781,7 +3781,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -3789,7 +3789,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -3813,7 +3813,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -3829,7 +3829,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -3837,7 +3837,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -3845,7 +3845,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -3901,7 +3901,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -3909,7 +3909,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -3925,7 +3925,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -3973,7 +3973,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -3981,7 +3981,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -3989,7 +3989,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -4053,7 +4053,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -4061,7 +4061,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -4085,7 +4085,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -4133,7 +4133,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -4141,7 +4141,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -4173,7 +4173,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -4181,7 +4181,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -4189,7 +4189,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -4245,7 +4245,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -4253,7 +4253,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -4269,7 +4269,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -4317,7 +4317,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -4325,7 +4325,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -4333,7 +4333,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -4373,7 +4373,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -4381,7 +4381,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -4421,7 +4421,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -4437,7 +4437,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -4445,7 +4445,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -4461,7 +4461,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -4493,7 +4493,7 @@ { "alias": "runtime_package_dependencies", "default": null, - "description": "Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`.", + "description": "Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/pants package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `/home/josh/work/scie-pants/dist/pants package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -4525,7 +4525,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -4533,7 +4533,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -4573,7 +4573,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -4605,7 +4605,7 @@ { "alias": "runtime_package_dependencies", "default": null, - "description": "Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`.", + "description": "Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/pants package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `/home/josh/work/scie-pants/dist/pants package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -4621,7 +4621,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -4629,7 +4629,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -4637,7 +4637,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -4653,7 +4653,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -4661,7 +4661,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -4669,7 +4669,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -4693,7 +4693,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -4701,7 +4701,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -4709,7 +4709,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -4741,7 +4741,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -4749,7 +4749,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -4781,7 +4781,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -13986,7 +13986,7 @@ "deprecation_active": false, "display_args": ["--pants-version="], "env_var": "PANTS_VERSION", - "help": "Use this Pants version. Note that Pants only uses this to verify that you are using the requested version, as Pants cannot dynamically change the version it is using once the program is already running.\n\nIf you use the `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64` script from https://www.pantsbuild.org/v2.12/docs/installation, however, changing the value in your `pants.toml` will cause the new version to be installed and run automatically.\n\nRun `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --version` to check what is being used.", + "help": "Use this Pants version. Note that Pants only uses this to verify that you are using the requested version, as Pants cannot dynamically change the version it is using once the program is already running.\n\nIf you use the `/home/josh/work/scie-pants/dist/pants` script from https://www.pantsbuild.org/v2.12/docs/installation, however, changing the value in your `pants.toml` will cause the new version to be installed and run automatically.\n\nRun `/home/josh/work/scie-pants/dist/pants --version` to check what is being used.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pants-version"], @@ -14043,7 +14043,7 @@ { "details": "from env var PANTS_BIN_NAME", "rank": "ENVIRONMENT", - "value": "/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64" + "value": "/home/josh/work/scie-pants/dist/pants" } ] } @@ -15150,7 +15150,7 @@ "--process-execution-graceful-shutdown-timeout=" ], "env_var": "PANTS_PROCESS_EXECUTION_GRACEFUL_SHUTDOWN_TIMEOUT", - "help": "The time in seconds to wait when gracefully shutting down an interactive process (such as one opened using `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 run`) before killing it.", + "help": "The time in seconds to wait when gracefully shutting down an interactive process (such as one opened using `/home/josh/work/scie-pants/dist/pants run`) before killing it.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -16911,7 +16911,7 @@ "deprecation_active": false, "display_args": ["--autoflake-lockfile="], "env_var": "PANTS_AUTOFLAKE_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.12.1/src/python/pants/backend/python/lint/autoflake/autoflake.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=autoflake`.\n\nAs explained at https://www.pantsbuild.org/v2.12/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.12.1/src/python/pants/backend/python/lint/autoflake/autoflake.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=autoflake`.\n\nAs explained at https://www.pantsbuild.org/v2.12/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--autoflake-lockfile"], @@ -17001,7 +17001,7 @@ "deprecation_active": false, "display_args": ["--[no-]autoflake-skip"], "env_var": "PANTS_AUTOFLAKE_SKIP", - "help": "Don't use Autoflake when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use Autoflake when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--autoflake-skip", "--no-autoflake-skip"], @@ -17065,7 +17065,7 @@ "deprecation_active": false, "display_args": ["--[no-]autoflake-export"], "env_var": "PANTS_AUTOFLAKE_EXPORT", - "help": "If true, export a virtual environment with Autoflake when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with Autoflake when running `/home/josh/work/scie-pants/dist/pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -17173,7 +17173,7 @@ "deprecation_active": false, "display_args": ["--bandit-lockfile="], "env_var": "PANTS_BANDIT_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.12.1/src/python/pants/backend/python/lint/bandit/bandit.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=bandit`.\n\nAs explained at https://www.pantsbuild.org/v2.12/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.12.1/src/python/pants/backend/python/lint/bandit/bandit.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=bandit`.\n\nAs explained at https://www.pantsbuild.org/v2.12/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--bandit-lockfile"], @@ -17289,7 +17289,7 @@ "deprecation_active": false, "display_args": ["--[no-]bandit-skip"], "env_var": "PANTS_BANDIT_SKIP", - "help": "Don't use Bandit when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use Bandit when running `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--bandit-skip", "--no-bandit-skip"], @@ -17351,7 +17351,7 @@ "deprecation_active": false, "display_args": ["--[no-]bandit-export"], "env_var": "PANTS_BANDIT_EXPORT", - "help": "If true, export a virtual environment with Bandit when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with Bandit when running `/home/josh/work/scie-pants/dist/pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--bandit-export", "--no-bandit-export"], @@ -17491,7 +17491,7 @@ "deprecation_active": false, "display_args": ["--black-lockfile="], "env_var": "PANTS_BLACK_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.12.1/src/python/pants/backend/python/lint/black/black.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=black`.\n\nAs explained at https://www.pantsbuild.org/v2.12/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.12.1/src/python/pants/backend/python/lint/black/black.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=black`.\n\nAs explained at https://www.pantsbuild.org/v2.12/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--black-lockfile"], @@ -17644,7 +17644,7 @@ "deprecation_active": false, "display_args": ["--[no-]black-skip"], "env_var": "PANTS_BLACK_SKIP", - "help": "Don't use Black when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use Black when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--black-skip", "--no-black-skip"], @@ -17706,7 +17706,7 @@ "deprecation_active": false, "display_args": ["--[no-]black-export"], "env_var": "PANTS_BLACK_EXPORT", - "help": "If true, export a virtual environment with Black when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with Black when running `/home/josh/work/scie-pants/dist/pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--black-export", "--no-black-export"], @@ -17928,7 +17928,7 @@ "deprecation_active": false, "display_args": ["--[no-]buf-format-skip"], "env_var": "PANTS_BUF_FORMAT_SKIP", - "help": "Don't use Buf when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use Buf when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--buf-format-skip", "--no-buf-format-skip"], @@ -17959,7 +17959,7 @@ "deprecation_active": false, "display_args": ["--[no-]buf-lint-skip"], "env_var": "PANTS_BUF_LINT_SKIP", - "help": "Don't use Buf when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use Buf when running `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--buf-lint-skip", "--no-buf-lint-skip"], @@ -18203,7 +18203,7 @@ "deprecation_active": false, "display_args": ["--cli-alias=\"{'key1': val1, 'key2': val2, ...}\""], "env_var": "PANTS_CLI_ALIAS", - "help": "Register command line aliases.\n\nExample:\n\n [cli.alias]\n green = \"fmt lint check\"\n all-changed = \"--changed-since=HEAD --changed-dependees=transitive\"\n\nThis would allow you to run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 green all-changed`, which is shorthand for `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt lint check --changed-since=HEAD --changed-dependees=transitive`.\n\nNotice: this option must be placed in a config file (e.g. `pants.toml` or `pantsrc`) to have any effect.", + "help": "Register command line aliases.\n\nExample:\n\n [cli.alias]\n green = \"fmt lint check\"\n all-changed = \"--changed-since=HEAD --changed-dependees=transitive\"\n\nThis would allow you to run `/home/josh/work/scie-pants/dist/pants green all-changed`, which is shorthand for `/home/josh/work/scie-pants/dist/pants fmt lint check --changed-since=HEAD --changed-dependees=transitive`.\n\nNotice: this option must be placed in a config file (e.g. `pants.toml` or `pantsrc`) to have any effect.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--cli-alias"], @@ -18589,7 +18589,7 @@ "deprecation_active": false, "display_args": ["--coverage-py-lockfile="], "env_var": "PANTS_COVERAGE_PY_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.12.1/src/python/pants/backend/python/subsystems/coverage_py.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=coverage-py`.\n\nAs explained at https://www.pantsbuild.org/v2.12/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.12.1/src/python/pants/backend/python/subsystems/coverage_py.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=coverage-py`.\n\nAs explained at https://www.pantsbuild.org/v2.12/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--coverage-py-lockfile"], @@ -19276,7 +19276,7 @@ "deprecation_active": false, "display_args": ["--docformatter-lockfile="], "env_var": "PANTS_DOCFORMATTER_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.12.1/src/python/pants/backend/python/lint/docformatter/docformatter.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=docformatter`.\n\nAs explained at https://www.pantsbuild.org/v2.12/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.12.1/src/python/pants/backend/python/lint/docformatter/docformatter.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=docformatter`.\n\nAs explained at https://www.pantsbuild.org/v2.12/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--docformatter-lockfile"], @@ -19366,7 +19366,7 @@ "deprecation_active": false, "display_args": ["--[no-]docformatter-skip"], "env_var": "PANTS_DOCFORMATTER_SKIP", - "help": "Don't use docformatter when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use docformatter when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -19433,7 +19433,7 @@ "deprecation_active": false, "display_args": ["--[no-]docformatter-export"], "env_var": "PANTS_DOCFORMATTER_EXPORT", - "help": "If true, export a virtual environment with docformatter when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with docformatter when running `/home/josh/work/scie-pants/dist/pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -19766,7 +19766,7 @@ "--docker-run-args=\"[, , ...]\"" ], "env_var": "PANTS_DOCKER_RUN_ARGS", - "help": "Additional arguments to use for `docker run` invocations.\n\nExample:\n\n $ /home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 run --docker-run-args=\"-p 127.0.0.1:80:8080/tcp --name demo\" src/example:image -- [image entrypoint args]\n\nTo provide the top-level options to the `docker` client, use `[docker].env_vars` to configure the [Environment variables](https://docs.docker.com/engine/reference/commandline/cli/#environment-variables) as appropriate.\n\nThe arguments for the image entrypoint may be passed on the command line after a double dash (`--`), or using the `--run-args` option.\n\nDefaults to `--interactive --tty` when stdout is connected to a terminal.", + "help": "Additional arguments to use for `docker run` invocations.\n\nExample:\n\n $ /home/josh/work/scie-pants/dist/pants run --docker-run-args=\"-p 127.0.0.1:80:8080/tcp --name demo\" src/example:image -- [image entrypoint args]\n\nTo provide the top-level options to the `docker` client, use `[docker].env_vars` to configure the [Environment variables](https://docs.docker.com/engine/reference/commandline/cli/#environment-variables) as appropriate.\n\nThe arguments for the image entrypoint may be passed on the command line after a double dash (`--`), or using the `--run-args` option.\n\nDefaults to `--interactive --tty` when stdout is connected to a terminal.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--docker-run-args"], @@ -19906,7 +19906,7 @@ "deprecation_active": false, "display_args": ["--dockerfile-parser-lockfile="], "env_var": "PANTS_DOCKERFILE_PARSER_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.12.1/src/python/pants/backend/docker/subsystems/dockerfile.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=dockerfile-parser`.\n\nAs explained at https://www.pantsbuild.org/v2.12/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.12.1/src/python/pants/backend/docker/subsystems/dockerfile.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=dockerfile-parser`.\n\nAs explained at https://www.pantsbuild.org/v2.12/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--dockerfile-parser-lockfile"], @@ -20174,7 +20174,7 @@ "--experimental-bsp-runner-env-vars=\"['', '', ...]\"" ], "env_var": "PANTS_EXPERIMENTAL_BSP_RUNNER_ENV_VARS", - "help": "Environment variables to set in the BSP runner script when setting up BSP in a repository. Entries are either strings in the form `ENV_VAR=value` to set an explicit value; or just `ENV_VAR` to copy the value from Pants' own environment when the experimental-bsp goal was run.\n\nThis option only takes effect when the BSP runner script is written. If the option changes, you must run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 experimental-bsp` again to write a new copy of the BSP runner script.\n\nNote: The environment variables passed to the Pants BSP server will be those set for your IDE and not your shell. For example, on macOS, the IDE is generally launched by `launchd` after clicking on a Dock icon, and not from the shell. Thus, any environment variables set for your shell will likely not be seen by the Pants BSP server. At the very least, on macOS consider writing an explicit PATH into the BSP runner script via this option.", + "help": "Environment variables to set in the BSP runner script when setting up BSP in a repository. Entries are either strings in the form `ENV_VAR=value` to set an explicit value; or just `ENV_VAR` to copy the value from Pants' own environment when the experimental-bsp goal was run.\n\nThis option only takes effect when the BSP runner script is written. If the option changes, you must run `/home/josh/work/scie-pants/dist/pants experimental-bsp` again to write a new copy of the BSP runner script.\n\nNote: The environment variables passed to the Pants BSP server will be those set for your IDE and not your shell. For example, on macOS, the IDE is generally launched by `launchd` after clicking on a Dock icon, and not from the shell. Thus, any environment variables set for your shell will likely not be seen by the Pants BSP server. At the very least, on macOS consider writing an explicit PATH into the BSP runner script via this option.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--experimental-bsp-runner-env-vars"], @@ -20699,7 +20699,7 @@ "deprecation_active": false, "display_args": ["--flake8-lockfile="], "env_var": "PANTS_FLAKE8_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.12.1/src/python/pants/backend/python/lint/flake8/flake8.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=flake8`.\n\nAs explained at https://www.pantsbuild.org/v2.12/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.12.1/src/python/pants/backend/python/lint/flake8/flake8.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=flake8`.\n\nAs explained at https://www.pantsbuild.org/v2.12/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--flake8-lockfile"], @@ -20885,7 +20885,7 @@ "deprecation_active": false, "display_args": ["--[no-]flake8-skip"], "env_var": "PANTS_FLAKE8_SKIP", - "help": "Don't use Flake8 when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use Flake8 when running `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--flake8-skip", "--no-flake8-skip"], @@ -20947,7 +20947,7 @@ "deprecation_active": false, "display_args": ["--[no-]flake8-export"], "env_var": "PANTS_FLAKE8_EXPORT", - "help": "If true, export a virtual environment with Flake8 when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with Flake8 when running `/home/josh/work/scie-pants/dist/pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--flake8-export", "--no-flake8-export"], @@ -21062,7 +21062,7 @@ "deprecation_active": false, "display_args": ["--generate-lockfiles-custom-command="], "env_var": "PANTS_GENERATE_LOCKFILES_CUSTOM_COMMAND", - "help": "If set, lockfile headers will say to run this command to regenerate the lockfile, rather than running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=` like normal.", + "help": "If set, lockfile headers will say to run this command to regenerate the lockfile, rather than running `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=` like normal.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--generate-lockfiles-custom-command"], @@ -21092,7 +21092,7 @@ "--generate-lockfiles-resolve=\"['', '', ...]\"" ], "env_var": "PANTS_GENERATE_LOCKFILES_RESOLVE", - "help": "Only generate lockfiles for the specified resolve(s).\n\nResolves are the logical names for the different lockfiles used in your project. For your own code's dependencies, these come from the option `[python].resolves`. For tool lockfiles, resolve names are the options scope for that tool such as `black`, `pytest`, and `mypy-protobuf`.\n\nFor example, you can run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=black --resolve=pytest --resolve=data-science` to only generate lockfiles for those two tools and your resolve named `data-science`.\n\nIf you specify an invalid resolve name, like 'fake', Pants will output all possible values.\n\nIf not specified, Pants will generate lockfiles for all resolves.", + "help": "Only generate lockfiles for the specified resolve(s).\n\nResolves are the logical names for the different lockfiles used in your project. For your own code's dependencies, these come from the option `[python].resolves`. For tool lockfiles, resolve names are the options scope for that tool such as `black`, `pytest`, and `mypy-protobuf`.\n\nFor example, you can run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=black --resolve=pytest --resolve=data-science` to only generate lockfiles for those two tools and your resolve named `data-science`.\n\nIf you specify an invalid resolve name, like 'fake', Pants will output all possible values.\n\nIf not specified, Pants will generate lockfiles for all resolves.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--generate-lockfiles-resolve"], @@ -21179,7 +21179,7 @@ "deprecation_active": false, "display_args": ["--[no-]gofmt-skip"], "env_var": "PANTS_GOFMT_SKIP", - "help": "Don't use gofmt when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use gofmt when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--gofmt-skip", "--no-gofmt-skip"], @@ -21397,7 +21397,7 @@ "deprecation_active": false, "display_args": ["--google-java-format-lockfile="], "env_var": "PANTS_GOOGLE_JAVA_FORMAT_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.12.1/src/python/pants/backend/java/lint/google_java_format/google_java_format.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=google-java-format`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.12.1/src/python/pants/backend/java/lint/google_java_format/google_java_format.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=google-java-format`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--google-java-format-lockfile"], @@ -21430,7 +21430,7 @@ "deprecation_active": false, "display_args": ["--[no-]google-java-format-skip"], "env_var": "PANTS_GOOGLE_JAVA_FORMAT_SKIP", - "help": "Don't use Google Java Format when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use Google Java Format when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -21944,7 +21944,7 @@ "deprecation_active": false, "display_args": ["--[no-]hadolint-skip"], "env_var": "PANTS_HADOLINT_SKIP", - "help": "Don't use Hadolint when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use Hadolint when running `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--hadolint-skip", "--no-hadolint-skip"], @@ -22622,7 +22622,7 @@ "deprecation_active": false, "display_args": ["--ipython-lockfile="], "env_var": "PANTS_IPYTHON_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.12.1/src/python/pants/backend/python/subsystems/ipython.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=ipython`.\n\nAs explained at https://www.pantsbuild.org/v2.12/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.12.1/src/python/pants/backend/python/subsystems/ipython.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=ipython`.\n\nAs explained at https://www.pantsbuild.org/v2.12/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--ipython-lockfile"], @@ -22852,7 +22852,7 @@ "deprecation_active": false, "display_args": ["--isort-lockfile="], "env_var": "PANTS_ISORT_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.12.1/src/python/pants/backend/python/lint/isort/isort.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=isort`.\n\nAs explained at https://www.pantsbuild.org/v2.12/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.12.1/src/python/pants/backend/python/lint/isort/isort.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=isort`.\n\nAs explained at https://www.pantsbuild.org/v2.12/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--isort-lockfile"], @@ -23012,7 +23012,7 @@ "deprecation_active": false, "display_args": ["--[no-]isort-skip"], "env_var": "PANTS_ISORT_SKIP", - "help": "Don't use isort when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use isort when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--isort-skip", "--no-isort-skip"], @@ -23074,7 +23074,7 @@ "deprecation_active": false, "display_args": ["--[no-]isort-export"], "env_var": "PANTS_ISORT_EXPORT", - "help": "If true, export a virtual environment with isort when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with isort when running `/home/josh/work/scie-pants/dist/pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--isort-export", "--no-isort-export"], @@ -23377,7 +23377,7 @@ "deprecation_active": false, "display_args": ["--junit-lockfile="], "env_var": "PANTS_JUNIT_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.12.1/src/python/pants/jvm/test/junit.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=junit`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.12.1/src/python/pants/jvm/test/junit.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=junit`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--junit-lockfile"], @@ -23920,7 +23920,7 @@ "deprecation_active": false, "display_args": ["--ktlint-lockfile="], "env_var": "PANTS_KTLINT_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.12.1/src/python/pants/backend/kotlin/lint/ktlint/ktlint.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=ktlint`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.12.1/src/python/pants/backend/kotlin/lint/ktlint/ktlint.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=ktlint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--ktlint-lockfile"], @@ -23953,7 +23953,7 @@ "deprecation_active": false, "display_args": ["--[no-]ktlint-skip"], "env_var": "PANTS_KTLINT_SKIP", - "help": "Don't use Ktlint when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use Ktlint when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--ktlint-skip", "--no-ktlint-skip"], @@ -24091,7 +24091,7 @@ "deprecation_active": false, "display_args": ["--lambdex-lockfile="], "env_var": "PANTS_LAMBDEX_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.12.1/src/python/pants/backend/python/subsystems/lambdex.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=lambdex`.\n\nAs explained at https://www.pantsbuild.org/v2.12/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.12.1/src/python/pants/backend/python/subsystems/lambdex.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=lambdex`.\n\nAs explained at https://www.pantsbuild.org/v2.12/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--lambdex-lockfile"], @@ -24460,7 +24460,7 @@ "deprecation_active": false, "display_args": ["--mypy-lockfile="], "env_var": "PANTS_MYPY_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.12.1/src/python/pants/backend/python/typecheck/mypy/mypy.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=mypy`.\n\nAs explained at https://www.pantsbuild.org/v2.12/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.12.1/src/python/pants/backend/python/typecheck/mypy/mypy.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=mypy`.\n\nAs explained at https://www.pantsbuild.org/v2.12/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--mypy-lockfile"], @@ -24679,7 +24679,7 @@ "deprecation_active": false, "display_args": ["--[no-]mypy-skip"], "env_var": "PANTS_MYPY_SKIP", - "help": "Don't use MyPy when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 check`.", + "help": "Don't use MyPy when running `/home/josh/work/scie-pants/dist/pants check`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--mypy-skip", "--no-mypy-skip"], @@ -24741,7 +24741,7 @@ "deprecation_active": false, "display_args": ["--[no-]mypy-export"], "env_var": "PANTS_MYPY_EXPORT", - "help": "If true, export a virtual environment with MyPy when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with MyPy when running `/home/josh/work/scie-pants/dist/pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--mypy-export", "--no-mypy-export"], @@ -24879,7 +24879,7 @@ "deprecation_active": false, "display_args": ["--mypy-protobuf-lockfile="], "env_var": "PANTS_MYPY_PROTOBUF_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.12.1/src/python/pants/backend/codegen/protobuf/python/mypy_protobuf.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=mypy-protobuf`.\n\nAs explained at https://www.pantsbuild.org/v2.12/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.12.1/src/python/pants/backend/codegen/protobuf/python/mypy_protobuf.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=mypy-protobuf`.\n\nAs explained at https://www.pantsbuild.org/v2.12/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--mypy-protobuf-lockfile"], @@ -25975,7 +25975,7 @@ "deprecation_active": false, "display_args": ["--pylint-lockfile="], "env_var": "PANTS_PYLINT_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.12.1/src/python/pants/backend/python/lint/pylint/pylint.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=pylint`.\n\nAs explained at https://www.pantsbuild.org/v2.12/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.12.1/src/python/pants/backend/python/lint/pylint/pylint.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=pylint`.\n\nAs explained at https://www.pantsbuild.org/v2.12/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pylint-lockfile"], @@ -26161,7 +26161,7 @@ "deprecation_active": false, "display_args": ["--[no-]pylint-skip"], "env_var": "PANTS_PYLINT_SKIP", - "help": "Don't use Pylint when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use Pylint when running `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pylint-skip", "--no-pylint-skip"], @@ -26223,7 +26223,7 @@ "deprecation_active": false, "display_args": ["--[no-]pylint-export"], "env_var": "PANTS_PYLINT_EXPORT", - "help": "If true, export a virtual environment with Pylint when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with Pylint when running `/home/josh/work/scie-pants/dist/pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pylint-export", "--no-pylint-export"], @@ -26527,7 +26527,7 @@ "deprecation_active": false, "display_args": ["--pytest-lockfile="], "env_var": "PANTS_PYTEST_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.12.1/src/python/pants/backend/python/subsystems/pytest.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=pytest`.\n\nAs explained at https://www.pantsbuild.org/v2.12/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.12.1/src/python/pants/backend/python/subsystems/pytest.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=pytest`.\n\nAs explained at https://www.pantsbuild.org/v2.12/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pytest-lockfile"], @@ -26828,7 +26828,7 @@ "deprecation_active": false, "display_args": ["--[no-]pytest-export"], "env_var": "PANTS_PYTEST_EXPORT", - "help": "If true, export a virtual environment with Pytest when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with Pytest when running `/home/josh/work/scie-pants/dist/pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pytest-export", "--no-pytest-export"], @@ -26985,7 +26985,7 @@ "--python-resolves=\"{'key1': val1, 'key2': val2, ...}\"" ], "env_var": "PANTS_PYTHON_RESOLVES", - "help": "A mapping of logical names to lockfile paths used in your project.\n\nMany organizations only need a single resolve for their whole project, which is a good default and often the simplest thing to do. However, you may need multiple resolves, such as if you use two conflicting versions of a requirement in your repository.\n\nIf you only need a single resolve, run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles` to generate the lockfile.\n\nIf you need multiple resolves:\n\n 1. Via this option, define multiple resolve names and their lockfile paths. The names should be meaningful to your repository, such as `data-science` or `pants-plugins`.\n 2. Set the default with `[python].default_resolve`.\n 3. Update your `python_requirement` targets with the `resolve` field to declare which resolve they should be available in. They default to `[python].default_resolve`, so you only need to update targets that you want in non-default resolves. (Often you'll set this via the `python_requirements` or `poetry_requirements` target generators)\n 4. Run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles` to generate the lockfiles. If the results aren't what you'd expect, adjust the prior step.\n 5. Update any targets like `python_source` / `python_sources`, `python_test` / `python_tests`, and `pex_binary` which need to set a non-default resolve with the `resolve` field.\n\nIf a target can work with multiple resolves, you can either use the `parametrize` mechanism or manually create a distinct target per resolve. See https://www.pantsbuild.org/v2.12/docs/targets for information about `parametrize`.\n\nFor example:\n\n python_sources(\n resolve=parametrize(\"data-science\", \"web-app\"),\n )\n\nYou can name the lockfile paths what you would like; Pants does not expect a certain file extension or location.\n\nOnly applies if `[python].enable_resolves` is true.", + "help": "A mapping of logical names to lockfile paths used in your project.\n\nMany organizations only need a single resolve for their whole project, which is a good default and often the simplest thing to do. However, you may need multiple resolves, such as if you use two conflicting versions of a requirement in your repository.\n\nIf you only need a single resolve, run `/home/josh/work/scie-pants/dist/pants generate-lockfiles` to generate the lockfile.\n\nIf you need multiple resolves:\n\n 1. Via this option, define multiple resolve names and their lockfile paths. The names should be meaningful to your repository, such as `data-science` or `pants-plugins`.\n 2. Set the default with `[python].default_resolve`.\n 3. Update your `python_requirement` targets with the `resolve` field to declare which resolve they should be available in. They default to `[python].default_resolve`, so you only need to update targets that you want in non-default resolves. (Often you'll set this via the `python_requirements` or `poetry_requirements` target generators)\n 4. Run `/home/josh/work/scie-pants/dist/pants generate-lockfiles` to generate the lockfiles. If the results aren't what you'd expect, adjust the prior step.\n 5. Update any targets like `python_source` / `python_sources`, `python_test` / `python_tests`, and `pex_binary` which need to set a non-default resolve with the `resolve` field.\n\nIf a target can work with multiple resolves, you can either use the `parametrize` mechanism or manually create a distinct target per resolve. See https://www.pantsbuild.org/v2.12/docs/targets for information about `parametrize`.\n\nFor example:\n\n python_sources(\n resolve=parametrize(\"data-science\", \"web-app\"),\n )\n\nYou can name the lockfile paths what you would like; Pants does not expect a certain file extension or location.\n\nOnly applies if `[python].enable_resolves` is true.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--python-resolves"], @@ -27117,7 +27117,7 @@ "deprecation_active": false, "display_args": ["--python-lockfile-generator="], "env_var": "PANTS_PYTHON_LOCKFILE_GENERATOR", - "help": "Whether to use Pex or Poetry with the `generate-lockfiles` goal.\n\nPoetry does not support these features:\n\n 1) `[python-repos]` for custom indexes/cheeseshops.\n 2) VCS (Git) requirements.\n 3) `[GLOBAL].ca_certs_path`.\n\nIf you use any of these features, you should use Pex.\n\nSeveral users have also had issues with how Poetry's lockfile generation handles environment markers for transitive dependencies; certain dependencies end up with nonsensical environment markers which cause the dependency to not be installed, then for Pants/Pex to complain the dependency is missing, even though it's in the lockfile. There is a workaround: for `[python].resolves`, manually create a `python_requirement` target for the problematic transitive dependencies so that they are seen as direct requirements, rather than transitive. For tool lockfiles, add the problematic transitive dependency to `[tool].extra_requirements`, e.g. `[isort].extra_requirements`. Then, regenerate the lockfile(s) with the `generate-lockfiles` goal. Alternatively, use Pex for generation.\n\nFinally, installing from a Poetry-generated lockfile is slower than installing from a Pex lockfile. When using a Pex lockfile, Pants will only install the subset needed for the current task.\n\nHowever, Pex lockfile generation is a new feature. Given how vast the Python packaging ecosystem is, it is possible you may experience edge cases / bugs we haven't yet covered. Bug reports are appreciated! https://github.com/pantsbuild/pants/issues/new/choose\n\nNote that while Pex generates locks in a proprietary JSON format, you can use the `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export` goal for Pants to create a virtual environment for interoperability with tools like IDEs.", + "help": "Whether to use Pex or Poetry with the `generate-lockfiles` goal.\n\nPoetry does not support these features:\n\n 1) `[python-repos]` for custom indexes/cheeseshops.\n 2) VCS (Git) requirements.\n 3) `[GLOBAL].ca_certs_path`.\n\nIf you use any of these features, you should use Pex.\n\nSeveral users have also had issues with how Poetry's lockfile generation handles environment markers for transitive dependencies; certain dependencies end up with nonsensical environment markers which cause the dependency to not be installed, then for Pants/Pex to complain the dependency is missing, even though it's in the lockfile. There is a workaround: for `[python].resolves`, manually create a `python_requirement` target for the problematic transitive dependencies so that they are seen as direct requirements, rather than transitive. For tool lockfiles, add the problematic transitive dependency to `[tool].extra_requirements`, e.g. `[isort].extra_requirements`. Then, regenerate the lockfile(s) with the `generate-lockfiles` goal. Alternatively, use Pex for generation.\n\nFinally, installing from a Poetry-generated lockfile is slower than installing from a Pex lockfile. When using a Pex lockfile, Pants will only install the subset needed for the current task.\n\nHowever, Pex lockfile generation is a new feature. Given how vast the Python packaging ecosystem is, it is possible you may experience edge cases / bugs we haven't yet covered. Bug reports are appreciated! https://github.com/pantsbuild/pants/issues/new/choose\n\nNote that while Pex generates locks in a proprietary JSON format, you can use the `/home/josh/work/scie-pants/dist/pants export` goal for Pants to create a virtual environment for interoperability with tools like IDEs.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--python-lockfile-generator"], @@ -27780,7 +27780,7 @@ "deprecation_active": false, "display_args": ["--[no-]python-infer-inits"], "env_var": "PANTS_PYTHON_INFER_INITS", - "help": "Infer a target's dependencies on any `__init__.py` files in the packages it is located in (recursively upward in the directory structure).\n\nEven if this is disabled, Pants will still include any ancestor `__init__.py` files, only they will not be 'proper' dependencies, e.g. they will not show up in `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` and their own dependencies will not be used.\n\nIf you have empty `__init__.py` files, it's safe to leave this option off; otherwise, you should enable this option.", + "help": "Infer a target's dependencies on any `__init__.py` files in the packages it is located in (recursively upward in the directory structure).\n\nEven if this is disabled, Pants will still include any ancestor `__init__.py` files, only they will not be 'proper' dependencies, e.g. they will not show up in `/home/josh/work/scie-pants/dist/pants dependencies` and their own dependencies will not be used.\n\nIf you have empty `__init__.py` files, it's safe to leave this option off; otherwise, you should enable this option.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -28341,7 +28341,7 @@ "deprecation_active": false, "display_args": ["--pyupgrade-lockfile="], "env_var": "PANTS_PYUPGRADE_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.12.1/src/python/pants/backend/python/lint/pyupgrade/pyupgrade.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=pyupgrade`.\n\nAs explained at https://www.pantsbuild.org/v2.12/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.12.1/src/python/pants/backend/python/lint/pyupgrade/pyupgrade.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=pyupgrade`.\n\nAs explained at https://www.pantsbuild.org/v2.12/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pyupgrade-lockfile"], @@ -28431,7 +28431,7 @@ "deprecation_active": false, "display_args": ["--[no-]pyupgrade-skip"], "env_var": "PANTS_PYUPGRADE_SKIP", - "help": "Don't use pyupgrade when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use pyupgrade when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pyupgrade-skip", "--no-pyupgrade-skip"], @@ -28495,7 +28495,7 @@ "deprecation_active": false, "display_args": ["--[no-]pyupgrade-export"], "env_var": "PANTS_PYUPGRADE_EXPORT", - "help": "If true, export a virtual environment with pyupgrade when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with pyupgrade when running `/home/josh/work/scie-pants/dist/pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -29089,7 +29089,7 @@ "deprecation_active": false, "display_args": ["--scalafmt-lockfile="], "env_var": "PANTS_SCALAFMT_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.12.1/src/python/pants/backend/scala/lint/scalafmt/scalafmt.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalafmt`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.12.1/src/python/pants/backend/scala/lint/scalafmt/scalafmt.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=scalafmt`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalafmt-lockfile"], @@ -29122,7 +29122,7 @@ "deprecation_active": false, "display_args": ["--[no-]scalafmt-skip"], "env_var": "PANTS_SCALAFMT_SKIP", - "help": "Don't use scalafmt when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use scalafmt when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalafmt-skip", "--no-scalafmt-skip"], @@ -29225,7 +29225,7 @@ "deprecation_active": false, "display_args": ["--scalapb-lockfile="], "env_var": "PANTS_SCALAPB_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.12.1/src/python/pants/backend/codegen/protobuf/scala/scalapbc.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalapb`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.12.1/src/python/pants/backend/codegen/protobuf/scala/scalapbc.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=scalapb`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalapb-lockfile"], @@ -29361,7 +29361,7 @@ "deprecation_active": false, "display_args": ["--scalatest-lockfile="], "env_var": "PANTS_SCALATEST_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.12.1/src/python/pants/backend/scala/subsystems/scalatest.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalatest`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.12.1/src/python/pants/backend/scala/subsystems/scalatest.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=scalatest`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalatest-lockfile"], @@ -29810,7 +29810,7 @@ "deprecation_active": false, "display_args": ["--setuptools-lockfile="], "env_var": "PANTS_SETUPTOOLS_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.12.1/src/python/pants/backend/python/subsystems/setuptools.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=setuptools`.\n\nAs explained at https://www.pantsbuild.org/v2.12/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.12.1/src/python/pants/backend/python/subsystems/setuptools.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=setuptools`.\n\nAs explained at https://www.pantsbuild.org/v2.12/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--setuptools-lockfile"], @@ -30153,7 +30153,7 @@ "deprecation_active": false, "display_args": ["--[no-]shellcheck-skip"], "env_var": "PANTS_SHELLCHECK_SKIP", - "help": "Don't use Shellcheck when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use Shellcheck when running `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--shellcheck-skip", "--no-shellcheck-skip"], @@ -30447,7 +30447,7 @@ "deprecation_active": false, "display_args": ["--[no-]shfmt-skip"], "env_var": "PANTS_SHFMT_SKIP", - "help": "Don't use shfmt when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use shfmt when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--shfmt-skip", "--no-shfmt-skip"], @@ -30977,7 +30977,7 @@ "deprecation_active": false, "display_args": ["--[no-]terraform-fmt-skip"], "env_var": "PANTS_TERRAFORM_FMT_SKIP", - "help": "Don't use `terraform fmt` when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use `terraform fmt` when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -31122,7 +31122,7 @@ "deprecation_active": false, "display_args": ["--terraform-hcl2-parser-lockfile="], "env_var": "PANTS_TERRAFORM_HCL2_PARSER_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.12.1/src/python/pants/backend/terraform/hcl2.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=terraform-hcl2-parser`.\n\nAs explained at https://www.pantsbuild.org/v2.12/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.12.1/src/python/pants/backend/terraform/hcl2.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=terraform-hcl2-parser`.\n\nAs explained at https://www.pantsbuild.org/v2.12/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--terraform-hcl2-parser-lockfile"], @@ -31165,7 +31165,7 @@ "deprecation_active": false, "display_args": ["--[no-]terraform-validate-skip"], "env_var": "PANTS_TERRAFORM_VALIDATE_SKIP", - "help": "Don't use `terraform validate` when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 check`.", + "help": "Don't use `terraform validate` when running `/home/josh/work/scie-pants/dist/pants check`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -31647,7 +31647,7 @@ "deprecation_active": false, "display_args": ["--twine-lockfile="], "env_var": "PANTS_TWINE_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.12.1/src/python/pants/backend/python/subsystems/twine.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=twine`.\n\nAs explained at https://www.pantsbuild.org/v2.12/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.12.1/src/python/pants/backend/python/subsystems/twine.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=twine`.\n\nAs explained at https://www.pantsbuild.org/v2.12/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--twine-lockfile"], @@ -31831,7 +31831,7 @@ "deprecation_active": false, "display_args": ["--[no-]twine-skip"], "env_var": "PANTS_TWINE_SKIP", - "help": "Don't use Twine when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 publish`.", + "help": "Don't use Twine when running `/home/josh/work/scie-pants/dist/pants publish`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--twine-skip", "--no-twine-skip"], @@ -32195,7 +32195,7 @@ "deprecation_active": false, "display_args": ["--yapf-lockfile="], "env_var": "PANTS_YAPF_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.12.1/src/python/pants/backend/python/lint/yapf/yapf.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=yapf`.\n\nAs explained at https://www.pantsbuild.org/v2.12/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.12.1/src/python/pants/backend/python/lint/yapf/yapf.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=yapf`.\n\nAs explained at https://www.pantsbuild.org/v2.12/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--yapf-lockfile"], @@ -32348,7 +32348,7 @@ "deprecation_active": false, "display_args": ["--[no-]yapf-skip"], "env_var": "PANTS_YAPF_SKIP", - "help": "Don't use yapf when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use yapf when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--yapf-skip", "--no-yapf-skip"], @@ -32410,7 +32410,7 @@ "deprecation_active": false, "display_args": ["--[no-]yapf-export"], "env_var": "PANTS_YAPF_EXPORT", - "help": "If true, export a virtual environment with yapf when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with yapf when running `/home/josh/work/scie-pants/dist/pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--yapf-export", "--no-yapf-export"], diff --git a/versioned_docs/version-2.12/reference/subsystems/autoflake.mdx b/versioned_docs/version-2.12/reference/subsystems/autoflake.mdx index ba544c582..449760aa3 100644 --- a/versioned_docs/version-2.12/reference/subsystems/autoflake.mdx +++ b/versioned_docs/version-2.12/reference/subsystems/autoflake.mdx @@ -25,7 +25,7 @@ Config section: `[autoflake]` default_repr={`False`} > -Don't use Autoflake when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use Autoflake when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. @@ -49,7 +49,7 @@ Arguments to pass directly to Autoflake, e.g. `--autoflake-args='--target-versio default_repr={`True`} > -If true, export a virtual environment with Autoflake when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`. +If true, export a virtual environment with Autoflake when running `/home/josh/work/scie-pants/dist/pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. @@ -107,7 +107,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=autoflake`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=autoflake`. As explained at https://www.pantsbuild.org/v2.12/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.12/reference/subsystems/bandit.mdx b/versioned_docs/version-2.12/reference/subsystems/bandit.mdx index 2eed6f4a6..9d77159a1 100644 --- a/versioned_docs/version-2.12/reference/subsystems/bandit.mdx +++ b/versioned_docs/version-2.12/reference/subsystems/bandit.mdx @@ -25,7 +25,7 @@ Config section: `[bandit]` default_repr={`False`} > -Don't use Bandit when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use Bandit when running `/home/josh/work/scie-pants/dist/pants lint`. @@ -49,7 +49,7 @@ Arguments to pass directly to Bandit, e.g. `--bandit-args='--skip B101,B308 --co default_repr={`True`} > -If true, export a virtual environment with Bandit when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`. +If true, export a virtual environment with Bandit when running `/home/josh/work/scie-pants/dist/pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. @@ -95,7 +95,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=bandit`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=bandit`. As explained at https://www.pantsbuild.org/v2.12/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.12/reference/subsystems/black.mdx b/versioned_docs/version-2.12/reference/subsystems/black.mdx index 747b6c521..d35bdc64f 100644 --- a/versioned_docs/version-2.12/reference/subsystems/black.mdx +++ b/versioned_docs/version-2.12/reference/subsystems/black.mdx @@ -25,7 +25,7 @@ Config section: `[black]` default_repr={`False`} > -Don't use Black when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use Black when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. @@ -49,7 +49,7 @@ Arguments to pass directly to Black, e.g. `--black-args='--target-version=py37 - default_repr={`True`} > -If true, export a virtual environment with Black when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`. +If true, export a virtual environment with Black when running `/home/josh/work/scie-pants/dist/pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. @@ -107,7 +107,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=black`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=black`. As explained at https://www.pantsbuild.org/v2.12/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.12/reference/subsystems/buf.mdx b/versioned_docs/version-2.12/reference/subsystems/buf.mdx index fa1f09d61..dcb757042 100644 --- a/versioned_docs/version-2.12/reference/subsystems/buf.mdx +++ b/versioned_docs/version-2.12/reference/subsystems/buf.mdx @@ -25,7 +25,7 @@ Config section: `[buf]` default_repr={`False`} > -Don't use Buf when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use Buf when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. @@ -37,7 +37,7 @@ Don't use Buf when running `/home/josh/work/scie-pants/dist/scie-pants-linu default_repr={`False`} > -Don't use Buf when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use Buf when running `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.12/reference/subsystems/cli.mdx b/versioned_docs/version-2.12/reference/subsystems/cli.mdx index 3612faf24..8c2253b82 100644 --- a/versioned_docs/version-2.12/reference/subsystems/cli.mdx +++ b/versioned_docs/version-2.12/reference/subsystems/cli.mdx @@ -35,7 +35,7 @@ green = "fmt lint check" all-changed = "--changed-since=HEAD --changed-dependees=transitive" ``` -This would allow you to run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 green all-changed`, which is shorthand for `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt lint check --changed-since=HEAD --changed-dependees=transitive`. +This would allow you to run `/home/josh/work/scie-pants/dist/pants green all-changed`, which is shorthand for `/home/josh/work/scie-pants/dist/pants fmt lint check --changed-since=HEAD --changed-dependees=transitive`. Notice: this option must be placed in a config file (e.g. `pants.toml` or `pantsrc`) to have any effect. diff --git a/versioned_docs/version-2.12/reference/subsystems/coverage-py.mdx b/versioned_docs/version-2.12/reference/subsystems/coverage-py.mdx index 6a393a0ea..6e54fe1ff 100644 --- a/versioned_docs/version-2.12/reference/subsystems/coverage-py.mdx +++ b/versioned_docs/version-2.12/reference/subsystems/coverage-py.mdx @@ -130,7 +130,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=coverage-py`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=coverage-py`. As explained at https://www.pantsbuild.org/v2.12/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.12/reference/subsystems/docformatter.mdx b/versioned_docs/version-2.12/reference/subsystems/docformatter.mdx index 6ae7c2a67..15f1faa0a 100644 --- a/versioned_docs/version-2.12/reference/subsystems/docformatter.mdx +++ b/versioned_docs/version-2.12/reference/subsystems/docformatter.mdx @@ -25,7 +25,7 @@ Config section: `[docformatter]` default_repr={`False`} > -Don't use docformatter when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use docformatter when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. @@ -49,7 +49,7 @@ Arguments to pass directly to docformatter, e.g. `--docformatter-args='--wrap-su default_repr={`True`} > -If true, export a virtual environment with docformatter when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`. +If true, export a virtual environment with docformatter when running `/home/josh/work/scie-pants/dist/pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. @@ -107,7 +107,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=docformatter`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=docformatter`. As explained at https://www.pantsbuild.org/v2.12/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.12/reference/subsystems/docker.mdx b/versioned_docs/version-2.12/reference/subsystems/docker.mdx index 73bfe68f3..9e930e245 100644 --- a/versioned_docs/version-2.12/reference/subsystems/docker.mdx +++ b/versioned_docs/version-2.12/reference/subsystems/docker.mdx @@ -160,7 +160,7 @@ Additional arguments to use for `docker run` invocations. Example: ``` -$ /home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 run --docker-run-args="-p 127.0.0.1:80:8080/tcp --name demo" src/example:image -- [image entrypoint args] +$ /home/josh/work/scie-pants/dist/pants run --docker-run-args="-p 127.0.0.1:80:8080/tcp --name demo" src/example:image -- [image entrypoint args] ``` To provide the top-level options to the `docker` client, use `[docker].env_vars` to configure the [Environment variables](https://docs.docker.com/engine/reference/commandline/cli/#environment-variables) as appropriate. diff --git a/versioned_docs/version-2.12/reference/subsystems/dockerfile-parser.mdx b/versioned_docs/version-2.12/reference/subsystems/dockerfile-parser.mdx index d4f1c88b8..af556bfbe 100644 --- a/versioned_docs/version-2.12/reference/subsystems/dockerfile-parser.mdx +++ b/versioned_docs/version-2.12/reference/subsystems/dockerfile-parser.mdx @@ -71,7 +71,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=dockerfile-parser`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=dockerfile-parser`. As explained at https://www.pantsbuild.org/v2.12/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.12/reference/subsystems/flake8.mdx b/versioned_docs/version-2.12/reference/subsystems/flake8.mdx index 23ec0892c..065d707c0 100644 --- a/versioned_docs/version-2.12/reference/subsystems/flake8.mdx +++ b/versioned_docs/version-2.12/reference/subsystems/flake8.mdx @@ -25,7 +25,7 @@ Config section: `[flake8]` default_repr={`False`} > -Don't use Flake8 when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use Flake8 when running `/home/josh/work/scie-pants/dist/pants lint`. @@ -49,7 +49,7 @@ Arguments to pass directly to Flake8, e.g. `--flake8-args='--ignore E123,W456 -- default_repr={`True`} > -If true, export a virtual environment with Flake8 when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`. +If true, export a virtual environment with Flake8 when running `/home/josh/work/scie-pants/dist/pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. @@ -95,7 +95,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=flake8`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=flake8`. As explained at https://www.pantsbuild.org/v2.12/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.12/reference/subsystems/gofmt.mdx b/versioned_docs/version-2.12/reference/subsystems/gofmt.mdx index 01c96bcf2..a4ae242b4 100644 --- a/versioned_docs/version-2.12/reference/subsystems/gofmt.mdx +++ b/versioned_docs/version-2.12/reference/subsystems/gofmt.mdx @@ -25,7 +25,7 @@ Config section: `[gofmt]` default_repr={`False`} > -Don't use gofmt when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use gofmt when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.12/reference/subsystems/google-java-format.mdx b/versioned_docs/version-2.12/reference/subsystems/google-java-format.mdx index d0896a325..76dce0d5c 100644 --- a/versioned_docs/version-2.12/reference/subsystems/google-java-format.mdx +++ b/versioned_docs/version-2.12/reference/subsystems/google-java-format.mdx @@ -25,7 +25,7 @@ Config section: `[google-java-format]` default_repr={`False`} > -Don't use Google Java Format when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use Google Java Format when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. @@ -79,7 +79,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.12.1/src/python/pants/backend/java/lint/google_java_format/google_java_format.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=google-java-format`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=google-java-format`. diff --git a/versioned_docs/version-2.12/reference/subsystems/hadolint.mdx b/versioned_docs/version-2.12/reference/subsystems/hadolint.mdx index a9f5100e1..b870dadd7 100644 --- a/versioned_docs/version-2.12/reference/subsystems/hadolint.mdx +++ b/versioned_docs/version-2.12/reference/subsystems/hadolint.mdx @@ -25,7 +25,7 @@ Config section: `[hadolint]` default_repr={`False`} > -Don't use Hadolint when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use Hadolint when running `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.12/reference/subsystems/ipython.mdx b/versioned_docs/version-2.12/reference/subsystems/ipython.mdx index e035026e5..4988627f5 100644 --- a/versioned_docs/version-2.12/reference/subsystems/ipython.mdx +++ b/versioned_docs/version-2.12/reference/subsystems/ipython.mdx @@ -59,7 +59,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=ipython`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=ipython`. As explained at https://www.pantsbuild.org/v2.12/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.12/reference/subsystems/isort.mdx b/versioned_docs/version-2.12/reference/subsystems/isort.mdx index 6c55d6d20..50bbb03b3 100644 --- a/versioned_docs/version-2.12/reference/subsystems/isort.mdx +++ b/versioned_docs/version-2.12/reference/subsystems/isort.mdx @@ -25,7 +25,7 @@ Config section: `[isort]` default_repr={`False`} > -Don't use isort when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use isort when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. @@ -49,7 +49,7 @@ Arguments to pass directly to isort, e.g. `--isort-args='--case-sensitive --trai default_repr={`True`} > -If true, export a virtual environment with isort when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`. +If true, export a virtual environment with isort when running `/home/josh/work/scie-pants/dist/pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. @@ -107,7 +107,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=isort`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=isort`. As explained at https://www.pantsbuild.org/v2.12/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.12/reference/subsystems/junit.mdx b/versioned_docs/version-2.12/reference/subsystems/junit.mdx index 1cab411d8..37b37c9c1 100644 --- a/versioned_docs/version-2.12/reference/subsystems/junit.mdx +++ b/versioned_docs/version-2.12/reference/subsystems/junit.mdx @@ -67,7 +67,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.12.1/src/python/pants/jvm/test/junit.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=junit`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=junit`. diff --git a/versioned_docs/version-2.12/reference/subsystems/ktlint.mdx b/versioned_docs/version-2.12/reference/subsystems/ktlint.mdx index 87a39bed7..44a0b0105 100644 --- a/versioned_docs/version-2.12/reference/subsystems/ktlint.mdx +++ b/versioned_docs/version-2.12/reference/subsystems/ktlint.mdx @@ -25,7 +25,7 @@ Config section: `[ktlint]` default_repr={`False`} > -Don't use Ktlint when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use Ktlint when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. @@ -67,7 +67,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.12.1/src/python/pants/backend/kotlin/lint/ktlint/ktlint.lock for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=ktlint`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=ktlint`. diff --git a/versioned_docs/version-2.12/reference/subsystems/lambdex.mdx b/versioned_docs/version-2.12/reference/subsystems/lambdex.mdx index e5b60c276..6b1a94cad 100644 --- a/versioned_docs/version-2.12/reference/subsystems/lambdex.mdx +++ b/versioned_docs/version-2.12/reference/subsystems/lambdex.mdx @@ -71,7 +71,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=lambdex`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=lambdex`. As explained at https://www.pantsbuild.org/v2.12/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.12/reference/subsystems/mypy-protobuf.mdx b/versioned_docs/version-2.12/reference/subsystems/mypy-protobuf.mdx index ff0b465b7..d37a9ba60 100644 --- a/versioned_docs/version-2.12/reference/subsystems/mypy-protobuf.mdx +++ b/versioned_docs/version-2.12/reference/subsystems/mypy-protobuf.mdx @@ -71,7 +71,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=mypy-protobuf`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=mypy-protobuf`. As explained at https://www.pantsbuild.org/v2.12/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.12/reference/subsystems/mypy.mdx b/versioned_docs/version-2.12/reference/subsystems/mypy.mdx index 290ff98fd..d773d71cc 100644 --- a/versioned_docs/version-2.12/reference/subsystems/mypy.mdx +++ b/versioned_docs/version-2.12/reference/subsystems/mypy.mdx @@ -25,7 +25,7 @@ Config section: `[mypy]` default_repr={`False`} > -Don't use MyPy when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 check`. +Don't use MyPy when running `/home/josh/work/scie-pants/dist/pants check`. @@ -49,7 +49,7 @@ Arguments to pass directly to MyPy, e.g. `--mypy-args='--python-version 3.7 --di default_repr={`True`} > -If true, export a virtual environment with MyPy when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`. +If true, export a virtual environment with MyPy when running `/home/josh/work/scie-pants/dist/pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. @@ -107,7 +107,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=mypy`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=mypy`. As explained at https://www.pantsbuild.org/v2.12/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.12/reference/subsystems/pylint.mdx b/versioned_docs/version-2.12/reference/subsystems/pylint.mdx index c86d5538e..671c1381a 100644 --- a/versioned_docs/version-2.12/reference/subsystems/pylint.mdx +++ b/versioned_docs/version-2.12/reference/subsystems/pylint.mdx @@ -25,7 +25,7 @@ Config section: `[pylint]` default_repr={`False`} > -Don't use Pylint when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use Pylint when running `/home/josh/work/scie-pants/dist/pants lint`. @@ -49,7 +49,7 @@ Arguments to pass directly to Pylint, e.g. `--pylint-args='--ignore=foo.py,bar.p default_repr={`True`} > -If true, export a virtual environment with Pylint when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`. +If true, export a virtual environment with Pylint when running `/home/josh/work/scie-pants/dist/pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. @@ -95,7 +95,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=pylint`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=pylint`. As explained at https://www.pantsbuild.org/v2.12/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.12/reference/subsystems/pytest.mdx b/versioned_docs/version-2.12/reference/subsystems/pytest.mdx index fb7a10a86..4702eabda 100644 --- a/versioned_docs/version-2.12/reference/subsystems/pytest.mdx +++ b/versioned_docs/version-2.12/reference/subsystems/pytest.mdx @@ -49,7 +49,7 @@ Enable test target timeouts. If timeouts are enabled then test targets with a ti default_repr={`True`} > -If true, export a virtual environment with Pytest when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`. +If true, export a virtual environment with Pytest when running `/home/josh/work/scie-pants/dist/pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. @@ -95,7 +95,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=pytest`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=pytest`. As explained at https://www.pantsbuild.org/v2.12/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.12/reference/subsystems/python-infer.mdx b/versioned_docs/version-2.12/reference/subsystems/python-infer.mdx index 8e5c417d5..32f8f6bf1 100644 --- a/versioned_docs/version-2.12/reference/subsystems/python-infer.mdx +++ b/versioned_docs/version-2.12/reference/subsystems/python-infer.mdx @@ -91,7 +91,7 @@ If --assets is True, treat valid-looking strings with at least this many forward Infer a target's dependencies on any `__init__.py` files in the packages it is located in (recursively upward in the directory structure). -Even if this is disabled, Pants will still include any ancestor `__init__.py` files, only they will not be 'proper' dependencies, e.g. they will not show up in `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` and their own dependencies will not be used. +Even if this is disabled, Pants will still include any ancestor `__init__.py` files, only they will not be 'proper' dependencies, e.g. they will not show up in `/home/josh/work/scie-pants/dist/pants dependencies` and their own dependencies will not be used. If you have empty `__init__.py` files, it's safe to leave this option off; otherwise, you should enable this option. diff --git a/versioned_docs/version-2.12/reference/subsystems/python.mdx b/versioned_docs/version-2.12/reference/subsystems/python.mdx index 690668e74..627e03e72 100644 --- a/versioned_docs/version-2.12/reference/subsystems/python.mdx +++ b/versioned_docs/version-2.12/reference/subsystems/python.mdx @@ -123,14 +123,14 @@ A mapping of logical names to lockfile paths used in your project. Many organizations only need a single resolve for their whole project, which is a good default and often the simplest thing to do. However, you may need multiple resolves, such as if you use two conflicting versions of a requirement in your repository. -If you only need a single resolve, run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles` to generate the lockfile. +If you only need a single resolve, run `/home/josh/work/scie-pants/dist/pants generate-lockfiles` to generate the lockfile. If you need multiple resolves: 1. Via this option, define multiple resolve names and their lockfile paths. The names should be meaningful to your repository, such as `data-science` or `pants-plugins`. 2. Set the default with `[python].default_resolve`. 3. Update your `python_requirement` targets with the `resolve` field to declare which resolve they should be available in. They default to `[python].default_resolve`, so you only need to update targets that you want in non-default resolves. (Often you'll set this via the `python_requirements` or `poetry_requirements` target generators) -4. Run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles` to generate the lockfiles. If the results aren't what you'd expect, adjust the prior step. +4. Run `/home/josh/work/scie-pants/dist/pants generate-lockfiles` to generate the lockfiles. If the results aren't what you'd expect, adjust the prior step. 5. Update any targets like `python_source` / `python_sources`, `python_test` / `python_tests`, and `pex_binary` which need to set a non-default resolve with the `resolve` field. If a target can work with multiple resolves, you can either use the `parametrize` mechanism or manually create a distinct target per resolve. See https://www.pantsbuild.org/v2.12/docs/targets for information about `parametrize`. @@ -225,7 +225,7 @@ Finally, installing from a Poetry-generated lockfile is slower than installing f However, Pex lockfile generation is a new feature. Given how vast the Python packaging ecosystem is, it is possible you may experience edge cases / bugs we haven't yet covered. Bug reports are appreciated! https://github.com/pantsbuild/pants/issues/new/choose -Note that while Pex generates locks in a proprietary JSON format, you can use the `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export` goal for Pants to create a virtual environment for interoperability with tools like IDEs. +Note that while Pex generates locks in a proprietary JSON format, you can use the `/home/josh/work/scie-pants/dist/pants export` goal for Pants to create a virtual environment for interoperability with tools like IDEs. diff --git a/versioned_docs/version-2.12/reference/subsystems/pyupgrade.mdx b/versioned_docs/version-2.12/reference/subsystems/pyupgrade.mdx index e1740a5b4..e00a6fad5 100644 --- a/versioned_docs/version-2.12/reference/subsystems/pyupgrade.mdx +++ b/versioned_docs/version-2.12/reference/subsystems/pyupgrade.mdx @@ -25,7 +25,7 @@ Config section: `[pyupgrade]` default_repr={`False`} > -Don't use pyupgrade when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use pyupgrade when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. @@ -49,7 +49,7 @@ Arguments to pass directly to pyupgrade, e.g. `--pyupgrade-args='--py39-plus --k default_repr={`True`} > -If true, export a virtual environment with pyupgrade when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`. +If true, export a virtual environment with pyupgrade when running `/home/josh/work/scie-pants/dist/pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. @@ -107,7 +107,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=pyupgrade`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=pyupgrade`. As explained at https://www.pantsbuild.org/v2.12/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.12/reference/subsystems/scalafmt.mdx b/versioned_docs/version-2.12/reference/subsystems/scalafmt.mdx index a9007a171..af5ef24e6 100644 --- a/versioned_docs/version-2.12/reference/subsystems/scalafmt.mdx +++ b/versioned_docs/version-2.12/reference/subsystems/scalafmt.mdx @@ -25,7 +25,7 @@ Config section: `[scalafmt]` default_repr={`False`} > -Don't use scalafmt when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use scalafmt when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. @@ -67,7 +67,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.12.1/src/python/pants/backend/scala/lint/scalafmt/scalafmt.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalafmt`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=scalafmt`. diff --git a/versioned_docs/version-2.12/reference/subsystems/scalapb.mdx b/versioned_docs/version-2.12/reference/subsystems/scalapb.mdx index 3df6fee70..a890240b4 100644 --- a/versioned_docs/version-2.12/reference/subsystems/scalapb.mdx +++ b/versioned_docs/version-2.12/reference/subsystems/scalapb.mdx @@ -69,7 +69,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.12.1/src/python/pants/backend/codegen/protobuf/scala/scalapbc.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalapb`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=scalapb`. diff --git a/versioned_docs/version-2.12/reference/subsystems/scalatest.mdx b/versioned_docs/version-2.12/reference/subsystems/scalatest.mdx index 930a52f81..b96b05395 100644 --- a/versioned_docs/version-2.12/reference/subsystems/scalatest.mdx +++ b/versioned_docs/version-2.12/reference/subsystems/scalatest.mdx @@ -69,7 +69,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.12.1/src/python/pants/backend/scala/subsystems/scalatest.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalatest`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=scalatest`. diff --git a/versioned_docs/version-2.12/reference/subsystems/setuptools.mdx b/versioned_docs/version-2.12/reference/subsystems/setuptools.mdx index fa4e1719a..1af1d6636 100644 --- a/versioned_docs/version-2.12/reference/subsystems/setuptools.mdx +++ b/versioned_docs/version-2.12/reference/subsystems/setuptools.mdx @@ -59,7 +59,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=setuptools`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=setuptools`. As explained at https://www.pantsbuild.org/v2.12/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.12/reference/subsystems/shellcheck.mdx b/versioned_docs/version-2.12/reference/subsystems/shellcheck.mdx index ebd4b675a..125927845 100644 --- a/versioned_docs/version-2.12/reference/subsystems/shellcheck.mdx +++ b/versioned_docs/version-2.12/reference/subsystems/shellcheck.mdx @@ -25,7 +25,7 @@ Config section: `[shellcheck]` default_repr={`False`} > -Don't use Shellcheck when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use Shellcheck when running `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.12/reference/subsystems/shfmt.mdx b/versioned_docs/version-2.12/reference/subsystems/shfmt.mdx index 2ef68b13b..70d98a7ef 100644 --- a/versioned_docs/version-2.12/reference/subsystems/shfmt.mdx +++ b/versioned_docs/version-2.12/reference/subsystems/shfmt.mdx @@ -25,7 +25,7 @@ Config section: `[shfmt]` default_repr={`False`} > -Don't use shfmt when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use shfmt when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.12/reference/subsystems/terraform-fmt.mdx b/versioned_docs/version-2.12/reference/subsystems/terraform-fmt.mdx index 0ea670e77..92c3c6ec7 100644 --- a/versioned_docs/version-2.12/reference/subsystems/terraform-fmt.mdx +++ b/versioned_docs/version-2.12/reference/subsystems/terraform-fmt.mdx @@ -25,7 +25,7 @@ Config section: `[terraform-fmt]` default_repr={`False`} > -Don't use `terraform fmt` when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use `terraform fmt` when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.12/reference/subsystems/terraform-hcl2-parser.mdx b/versioned_docs/version-2.12/reference/subsystems/terraform-hcl2-parser.mdx index 4f37b73b1..7c1c0ba34 100644 --- a/versioned_docs/version-2.12/reference/subsystems/terraform-hcl2-parser.mdx +++ b/versioned_docs/version-2.12/reference/subsystems/terraform-hcl2-parser.mdx @@ -71,7 +71,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=terraform-hcl2-parser`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=terraform-hcl2-parser`. As explained at https://www.pantsbuild.org/v2.12/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.12/reference/subsystems/terraform-validate.mdx b/versioned_docs/version-2.12/reference/subsystems/terraform-validate.mdx index 0756cde83..89fa2bb81 100644 --- a/versioned_docs/version-2.12/reference/subsystems/terraform-validate.mdx +++ b/versioned_docs/version-2.12/reference/subsystems/terraform-validate.mdx @@ -25,7 +25,7 @@ Config section: `[terraform-validate]` default_repr={`False`} > -Don't use `terraform validate` when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 check`. +Don't use `terraform validate` when running `/home/josh/work/scie-pants/dist/pants check`. diff --git a/versioned_docs/version-2.12/reference/subsystems/twine.mdx b/versioned_docs/version-2.12/reference/subsystems/twine.mdx index 66c4e868f..ace727edd 100644 --- a/versioned_docs/version-2.12/reference/subsystems/twine.mdx +++ b/versioned_docs/version-2.12/reference/subsystems/twine.mdx @@ -25,7 +25,7 @@ Config section: `[twine]` default_repr={`False`} > -Don't use Twine when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 publish`. +Don't use Twine when running `/home/josh/work/scie-pants/dist/pants publish`. @@ -93,7 +93,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=twine`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=twine`. As explained at https://www.pantsbuild.org/v2.12/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.12/reference/subsystems/yapf.mdx b/versioned_docs/version-2.12/reference/subsystems/yapf.mdx index 4c0b08d7a..3ac5f5c9c 100644 --- a/versioned_docs/version-2.12/reference/subsystems/yapf.mdx +++ b/versioned_docs/version-2.12/reference/subsystems/yapf.mdx @@ -25,7 +25,7 @@ Config section: `[yapf]` default_repr={`False`} > -Don't use yapf when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use yapf when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. @@ -51,7 +51,7 @@ Certain arguments, specifically `--recursive`, `--in-place`, and `--parallel`, w default_repr={`True`} > -If true, export a virtual environment with yapf when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`. +If true, export a virtual environment with yapf when running `/home/josh/work/scie-pants/dist/pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. @@ -109,7 +109,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=yapf`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=yapf`. As explained at https://www.pantsbuild.org/v2.12/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.12/reference/targets/archive.mdx b/versioned_docs/version-2.12/reference/targets/archive.mdx index eee2b5712..801685458 100644 --- a/versioned_docs/version-2.12/reference/targets/archive.mdx +++ b/versioned_docs/version-2.12/reference/targets/archive.mdx @@ -24,7 +24,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -52,7 +52,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. @@ -65,11 +65,11 @@ Warning: setting this value risks naming collisions with other package targets y default_repr={`None`} > -Addresses to any targets that can be built with `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, e.g. `["project:app"]`. +Addresses to any targets that can be built with `/home/josh/work/scie-pants/dist/pants package`, e.g. `["project:app"]`. -Pants will build the assets as if you had run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`. It will include the results in your archive using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). +Pants will build the assets as if you had run `/home/josh/work/scie-pants/dist/pants package`. It will include the results in your archive using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). -You can include anything that can be built by `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or even another `archive`. +You can include anything that can be built by `/home/josh/work/scie-pants/dist/pants package`, e.g. a `pex_binary`, `python_awslambda`, or even another `archive`. diff --git a/versioned_docs/version-2.12/reference/targets/deploy_jar.mdx b/versioned_docs/version-2.12/reference/targets/deploy_jar.mdx index 7c8d1c9ab..0b9d3ae36 100644 --- a/versioned_docs/version-2.12/reference/targets/deploy_jar.mdx +++ b/versioned_docs/version-2.12/reference/targets/deploy_jar.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.experimental.java` @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -52,9 +52,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -73,7 +73,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. diff --git a/versioned_docs/version-2.12/reference/targets/docker_image.mdx b/versioned_docs/version-2.12/reference/targets/docker_image.mdx index 1aef1349e..09104c98c 100644 --- a/versioned_docs/version-2.12/reference/targets/docker_image.mdx +++ b/versioned_docs/version-2.12/reference/targets/docker_image.mdx @@ -39,7 +39,7 @@ Backend: `pants.backend.docker` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -52,7 +52,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -78,9 +78,9 @@ Use `[docker].build_args` to set default build args for all images. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -275,7 +275,7 @@ See [Docker documentation](https://docs.docker.com/develop/develop-images/build_ default_repr={`False`} > -If set to true, do not push this image to registries when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 publish`. +If set to true, do not push this image to registries when running `/home/josh/work/scie-pants/dist/pants publish`. diff --git a/versioned_docs/version-2.12/reference/targets/experimental_run_shell_command.mdx b/versioned_docs/version-2.12/reference/targets/experimental_run_shell_command.mdx index 5040ea950..1f0a43fea 100644 --- a/versioned_docs/version-2.12/reference/targets/experimental_run_shell_command.mdx +++ b/versioned_docs/version-2.12/reference/targets/experimental_run_shell_command.mdx @@ -37,7 +37,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -50,7 +50,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -63,9 +63,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.12/reference/targets/experimental_shell_command.mdx b/versioned_docs/version-2.12/reference/targets/experimental_shell_command.mdx index b3ee87cba..5f8a608fe 100644 --- a/versioned_docs/version-2.12/reference/targets/experimental_shell_command.mdx +++ b/versioned_docs/version-2.12/reference/targets/experimental_shell_command.mdx @@ -41,7 +41,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -54,7 +54,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -67,9 +67,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.12/reference/targets/file.mdx b/versioned_docs/version-2.12/reference/targets/file.mdx index b665a513b..5ec078d49 100644 --- a/versioned_docs/version-2.12/reference/targets/file.mdx +++ b/versioned_docs/version-2.12/reference/targets/file.mdx @@ -26,7 +26,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -52,9 +52,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.12/reference/targets/files.mdx b/versioned_docs/version-2.12/reference/targets/files.mdx index 44bf04439..8a72dd869 100644 --- a/versioned_docs/version-2.12/reference/targets/files.mdx +++ b/versioned_docs/version-2.12/reference/targets/files.mdx @@ -24,7 +24,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -94,9 +94,9 @@ You can specify the same file name in multiple keys, so long as you don't o Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.12/reference/targets/go_binary.mdx b/versioned_docs/version-2.12/reference/targets/go_binary.mdx index 3f172d7d0..26351b1ff 100644 --- a/versioned_docs/version-2.12/reference/targets/go_binary.mdx +++ b/versioned_docs/version-2.12/reference/targets/go_binary.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.go` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -52,7 +52,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. diff --git a/versioned_docs/version-2.12/reference/targets/go_mod.mdx b/versioned_docs/version-2.12/reference/targets/go_mod.mdx index 605db3545..caeac0e75 100644 --- a/versioned_docs/version-2.12/reference/targets/go_mod.mdx +++ b/versioned_docs/version-2.12/reference/targets/go_mod.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.go` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.12/reference/targets/go_package.mdx b/versioned_docs/version-2.12/reference/targets/go_package.mdx index b487e7430..2af5b9b4e 100644 --- a/versioned_docs/version-2.12/reference/targets/go_package.mdx +++ b/versioned_docs/version-2.12/reference/targets/go_package.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.experimental.go` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -52,9 +52,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.12/reference/targets/go_third_party_package.mdx b/versioned_docs/version-2.12/reference/targets/go_third_party_package.mdx index 95de7aaa0..449c60662 100644 --- a/versioned_docs/version-2.12/reference/targets/go_third_party_package.mdx +++ b/versioned_docs/version-2.12/reference/targets/go_third_party_package.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.go` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -54,9 +54,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.12/reference/targets/helm_artifact.mdx b/versioned_docs/version-2.12/reference/targets/helm_artifact.mdx index 62850ffdf..33546af67 100644 --- a/versioned_docs/version-2.12/reference/targets/helm_artifact.mdx +++ b/versioned_docs/version-2.12/reference/targets/helm_artifact.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.helm` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.12/reference/targets/helm_chart.mdx b/versioned_docs/version-2.12/reference/targets/helm_chart.mdx index bf178093d..a7b9c38fd 100644 --- a/versioned_docs/version-2.12/reference/targets/helm_chart.mdx +++ b/versioned_docs/version-2.12/reference/targets/helm_chart.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.helm` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -76,9 +76,9 @@ Example: `sources=['example.ext', 'test_*.ext', '!test_ignore.ext']`. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -99,7 +99,7 @@ If undefined, this will use the path to the BUILD file, For example, `src/charts Regardless of whether you use the default or set this field, the path will end with Helms's file format of `-.tgz`, where `chart_name` and `chart_version` are the values extracted from the Chart.yaml file. So, using the default for this field, the target `src/charts/mychart:tgt_name` might have a final path like `src.charts.mychart/tgt_name/mychart-0.1.0.tgz`. -When running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. @@ -170,7 +170,7 @@ The above example shows two valid `registry` options: using an alias to a config default_repr={`False`} > -If set to true, do not push this helm chart to registries when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 publish`. +If set to true, do not push this helm chart to registries when running `/home/josh/work/scie-pants/dist/pants publish`. diff --git a/versioned_docs/version-2.12/reference/targets/helm_unittest_test.mdx b/versioned_docs/version-2.12/reference/targets/helm_unittest_test.mdx index 580053cc5..71e19e790 100644 --- a/versioned_docs/version-2.12/reference/targets/helm_unittest_test.mdx +++ b/versioned_docs/version-2.12/reference/targets/helm_unittest_test.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.helm` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -63,9 +63,9 @@ Path is relative to the BUILD file's directory, e.g. `source='example.ext'` Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.12/reference/targets/helm_unittest_tests.mdx b/versioned_docs/version-2.12/reference/targets/helm_unittest_tests.mdx index 24da30fc4..93bbc0d3d 100644 --- a/versioned_docs/version-2.12/reference/targets/helm_unittest_tests.mdx +++ b/versioned_docs/version-2.12/reference/targets/helm_unittest_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.helm` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -65,9 +65,9 @@ Example: `sources=['example.ext', 'test_*.ext', '!test_ignore.ext']`. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -84,9 +84,9 @@ You may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:l Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.12/reference/targets/java_source.mdx b/versioned_docs/version-2.12/reference/targets/java_source.mdx index b4a06b4c0..2ae5c1798 100644 --- a/versioned_docs/version-2.12/reference/targets/java_source.mdx +++ b/versioned_docs/version-2.12/reference/targets/java_source.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.java` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.12/reference/targets/java_sources.mdx b/versioned_docs/version-2.12/reference/targets/java_sources.mdx index 3a8ce1e8a..105d565d8 100644 --- a/versioned_docs/version-2.12/reference/targets/java_sources.mdx +++ b/versioned_docs/version-2.12/reference/targets/java_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.java` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -77,9 +77,9 @@ If true, don't run Google Java Format on this target's code. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.12/reference/targets/junit_test.mdx b/versioned_docs/version-2.12/reference/targets/junit_test.mdx index 95bb9241b..351f3a438 100644 --- a/versioned_docs/version-2.12/reference/targets/junit_test.mdx +++ b/versioned_docs/version-2.12/reference/targets/junit_test.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.java` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -63,9 +63,9 @@ Path is relative to the BUILD file's directory, e.g. `source='example.ext'` Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.12/reference/targets/junit_tests.mdx b/versioned_docs/version-2.12/reference/targets/junit_tests.mdx index c464cfff3..c486d9b2c 100644 --- a/versioned_docs/version-2.12/reference/targets/junit_tests.mdx +++ b/versioned_docs/version-2.12/reference/targets/junit_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.java` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -65,9 +65,9 @@ Example: `sources=['example.ext', 'test_*.ext', '!test_ignore.ext']`. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.12/reference/targets/jvm_artifact.mdx b/versioned_docs/version-2.12/reference/targets/jvm_artifact.mdx index b092f847f..57c626586 100644 --- a/versioned_docs/version-2.12/reference/targets/jvm_artifact.mdx +++ b/versioned_docs/version-2.12/reference/targets/jvm_artifact.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.java` @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.12/reference/targets/jvm_war.mdx b/versioned_docs/version-2.12/reference/targets/jvm_war.mdx index 8a4d283ea..86d63d31d 100644 --- a/versioned_docs/version-2.12/reference/targets/jvm_war.mdx +++ b/versioned_docs/version-2.12/reference/targets/jvm_war.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.java` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -74,9 +74,9 @@ A list of addresses to `resources` and `files` targets with content to place in Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -106,7 +106,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. diff --git a/versioned_docs/version-2.12/reference/targets/kotlin_source.mdx b/versioned_docs/version-2.12/reference/targets/kotlin_source.mdx index f13c0d02d..65088bdae 100644 --- a/versioned_docs/version-2.12/reference/targets/kotlin_source.mdx +++ b/versioned_docs/version-2.12/reference/targets/kotlin_source.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.kotlin` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.12/reference/targets/kotlin_sources.mdx b/versioned_docs/version-2.12/reference/targets/kotlin_sources.mdx index 0af994996..1eceb6d79 100644 --- a/versioned_docs/version-2.12/reference/targets/kotlin_sources.mdx +++ b/versioned_docs/version-2.12/reference/targets/kotlin_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.kotlin` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -77,9 +77,9 @@ If true, don't run Ktlint on this target's code. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.12/reference/targets/kotlinc_plugin.mdx b/versioned_docs/version-2.12/reference/targets/kotlinc_plugin.mdx index 936aa994f..5facbbddf 100644 --- a/versioned_docs/version-2.12/reference/targets/kotlinc_plugin.mdx +++ b/versioned_docs/version-2.12/reference/targets/kotlinc_plugin.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.kotlin` @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.12/reference/targets/pants_requirements.mdx b/versioned_docs/version-2.12/reference/targets/pants_requirements.mdx index d02ea13c5..486c52006 100644 --- a/versioned_docs/version-2.12/reference/targets/pants_requirements.mdx +++ b/versioned_docs/version-2.12/reference/targets/pants_requirements.mdx @@ -30,7 +30,7 @@ Backend: `pants.backend.plugin_development` @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.12/reference/targets/pex_binaries.mdx b/versioned_docs/version-2.12/reference/targets/pex_binaries.mdx index 219e3edf0..6827cf08f 100644 --- a/versioned_docs/version-2.12/reference/targets/pex_binaries.mdx +++ b/versioned_docs/version-2.12/reference/targets/pex_binaries.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -132,9 +132,9 @@ All dependencies must share the same value for their `resolve` field. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.12/reference/targets/pex_binary.mdx b/versioned_docs/version-2.12/reference/targets/pex_binary.mdx index d728c837b..47013de29 100644 --- a/versioned_docs/version-2.12/reference/targets/pex_binary.mdx +++ b/versioned_docs/version-2.12/reference/targets/pex_binary.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -86,9 +86,9 @@ All dependencies must share the same value for their `resolve` field. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -326,7 +326,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. diff --git a/versioned_docs/version-2.12/reference/targets/pipenv_requirements.mdx b/versioned_docs/version-2.12/reference/targets/pipenv_requirements.mdx index e87501d1a..1a319f31a 100644 --- a/versioned_docs/version-2.12/reference/targets/pipenv_requirements.mdx +++ b/versioned_docs/version-2.12/reference/targets/pipenv_requirements.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.12/reference/targets/poetry_requirements.mdx b/versioned_docs/version-2.12/reference/targets/poetry_requirements.mdx index 4d8346512..344c86b2f 100644 --- a/versioned_docs/version-2.12/reference/targets/poetry_requirements.mdx +++ b/versioned_docs/version-2.12/reference/targets/poetry_requirements.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.12/reference/targets/protobuf_source.mdx b/versioned_docs/version-2.12/reference/targets/protobuf_source.mdx index e63f44e92..6e6a0e673 100644 --- a/versioned_docs/version-2.12/reference/targets/protobuf_source.mdx +++ b/versioned_docs/version-2.12/reference/targets/protobuf_source.mdx @@ -27,7 +27,7 @@ Backend: `pants.backend.codegen.protobuf.python Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -40,7 +40,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -53,9 +53,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.12/reference/targets/protobuf_sources.mdx b/versioned_docs/version-2.12/reference/targets/protobuf_sources.mdx index b8caef643..4b448fd9a 100644 --- a/versioned_docs/version-2.12/reference/targets/protobuf_sources.mdx +++ b/versioned_docs/version-2.12/reference/targets/protobuf_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.codegen.protobuf.python Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -205,9 +205,9 @@ Whether to generate gRPC code or not. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.12/reference/targets/pyoxidizer_binary.mdx b/versioned_docs/version-2.12/reference/targets/pyoxidizer_binary.mdx index 55fc782c6..e7e8b10c2 100644 --- a/versioned_docs/version-2.12/reference/targets/pyoxidizer_binary.mdx +++ b/versioned_docs/version-2.12/reference/targets/pyoxidizer_binary.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.python.pac Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -58,7 +58,7 @@ If undefined, this will use the path to the BUILD file, followed by the target n Regardless of whether you use the default or set this field, the path will end with PyOxidizer's file format of `/{debug,release}/install/`, where `platform` is a Rust platform triplet like `aarch-64-apple-darwin` and `binary_name` is the `name` of the `pyoxidizer_target`. So, using the default for this field, the target `src/python/project:bin` might have a final path like `src.python.project/bin/aarch-64-apple-darwin/release/bin`. -When running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. diff --git a/versioned_docs/version-2.12/reference/targets/python_awslambda.mdx b/versioned_docs/version-2.12/reference/targets/python_awslambda.mdx index 3a98f3b2c..36df4c59a 100644 --- a/versioned_docs/version-2.12/reference/targets/python_awslambda.mdx +++ b/versioned_docs/version-2.12/reference/targets/python_awslambda.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.awslambda.python` @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -54,7 +54,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. @@ -69,9 +69,9 @@ Warning: setting this value risks naming collisions with other package targets y Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.12/reference/targets/python_distribution.mdx b/versioned_docs/version-2.12/reference/targets/python_distribution.mdx index 3b8ecea62..23dbe75ce 100644 --- a/versioned_docs/version-2.12/reference/targets/python_distribution.mdx +++ b/versioned_docs/version-2.12/reference/targets/python_distribution.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -52,9 +52,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -89,7 +89,7 @@ Note that Pants will assume that any value that either starts with `:` or has `/ Pants will attempt to infer dependencies, which you can confirm by running: ``` -/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies +/home/josh/work/scie-pants/dist/pants dependencies ``` diff --git a/versioned_docs/version-2.12/reference/targets/python_google_cloud_function.mdx b/versioned_docs/version-2.12/reference/targets/python_google_cloud_function.mdx index 3a4643124..8dc79bad5 100644 --- a/versioned_docs/version-2.12/reference/targets/python_google_cloud_function.mdx +++ b/versioned_docs/version-2.12/reference/targets/python_google_cloud_function.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.google_cloud_function.p Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -54,7 +54,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. @@ -69,9 +69,9 @@ Warning: setting this value risks naming collisions with other package targets y Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.12/reference/targets/python_requirement.mdx b/versioned_docs/version-2.12/reference/targets/python_requirement.mdx index 2a6e4cb1b..8ce8a552a 100644 --- a/versioned_docs/version-2.12/reference/targets/python_requirement.mdx +++ b/versioned_docs/version-2.12/reference/targets/python_requirement.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -54,9 +54,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.12/reference/targets/python_requirements.mdx b/versioned_docs/version-2.12/reference/targets/python_requirements.mdx index 2691c18c2..6fba0b9aa 100644 --- a/versioned_docs/version-2.12/reference/targets/python_requirements.mdx +++ b/versioned_docs/version-2.12/reference/targets/python_requirements.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.12/reference/targets/python_source.mdx b/versioned_docs/version-2.12/reference/targets/python_source.mdx index 23e08cd04..4be4c0f2b 100644 --- a/versioned_docs/version-2.12/reference/targets/python_source.mdx +++ b/versioned_docs/version-2.12/reference/targets/python_source.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -69,9 +69,9 @@ See https://www.pantsbuild.org/v2.12/docs/python-interpreter-compatibility for h Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.12/reference/targets/python_sources.mdx b/versioned_docs/version-2.12/reference/targets/python_sources.mdx index 7382716ce..a3d53dfba 100644 --- a/versioned_docs/version-2.12/reference/targets/python_sources.mdx +++ b/versioned_docs/version-2.12/reference/targets/python_sources.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -231,9 +231,9 @@ All dependencies must share the same value for their `resolve` field. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.12/reference/targets/python_test.mdx b/versioned_docs/version-2.12/reference/targets/python_test.mdx index 59e2b2989..31b967a81 100644 --- a/versioned_docs/version-2.12/reference/targets/python_test.mdx +++ b/versioned_docs/version-2.12/reference/targets/python_test.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -54,9 +54,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -99,11 +99,11 @@ If unset, will default to `[pytest].timeout_default`; if that option is also uns default_repr={`None`} > -Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run. +Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/pants package` goal and whose resulting artifacts should be included in the test run. -Pants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). +Pants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). -You can include anything that can be built by `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`. +You can include anything that can be built by `/home/josh/work/scie-pants/dist/pants package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`. @@ -157,9 +157,9 @@ If true, don't run this target's tests. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.12/reference/targets/python_test_utils.mdx b/versioned_docs/version-2.12/reference/targets/python_test_utils.mdx index df1bf4e33..f1fd7ff27 100644 --- a/versioned_docs/version-2.12/reference/targets/python_test_utils.mdx +++ b/versioned_docs/version-2.12/reference/targets/python_test_utils.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -231,9 +231,9 @@ All dependencies must share the same value for their `resolve` field. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.12/reference/targets/python_tests.mdx b/versioned_docs/version-2.12/reference/targets/python_tests.mdx index e5742aba8..a14d40baa 100644 --- a/versioned_docs/version-2.12/reference/targets/python_tests.mdx +++ b/versioned_docs/version-2.12/reference/targets/python_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -214,9 +214,9 @@ If true, don't run MyPy on this target's code. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -259,11 +259,11 @@ If unset, will default to `[pytest].timeout_default`; if that option is also uns default_repr={`None`} > -Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run. +Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/pants package` goal and whose resulting artifacts should be included in the test run. -Pants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). +Pants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). -You can include anything that can be built by `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`. +You can include anything that can be built by `/home/josh/work/scie-pants/dist/pants package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`. diff --git a/versioned_docs/version-2.12/reference/targets/relocated_files.mdx b/versioned_docs/version-2.12/reference/targets/relocated_files.mdx index 73ed0c422..b920f40cd 100644 --- a/versioned_docs/version-2.12/reference/targets/relocated_files.mdx +++ b/versioned_docs/version-2.12/reference/targets/relocated_files.mdx @@ -61,7 +61,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -74,7 +74,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.12/reference/targets/resource.mdx b/versioned_docs/version-2.12/reference/targets/resource.mdx index 47715df4b..02758c417 100644 --- a/versioned_docs/version-2.12/reference/targets/resource.mdx +++ b/versioned_docs/version-2.12/reference/targets/resource.mdx @@ -26,7 +26,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -52,9 +52,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.12/reference/targets/resources.mdx b/versioned_docs/version-2.12/reference/targets/resources.mdx index 957047c7a..1ad5aa6c8 100644 --- a/versioned_docs/version-2.12/reference/targets/resources.mdx +++ b/versioned_docs/version-2.12/reference/targets/resources.mdx @@ -24,7 +24,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -94,9 +94,9 @@ You can specify the same file name in multiple keys, so long as you don't o Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.12/reference/targets/scala_junit_test.mdx b/versioned_docs/version-2.12/reference/targets/scala_junit_test.mdx index abe50db4f..2c8dfe272 100644 --- a/versioned_docs/version-2.12/reference/targets/scala_junit_test.mdx +++ b/versioned_docs/version-2.12/reference/targets/scala_junit_test.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.scala` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.12/reference/targets/scala_junit_tests.mdx b/versioned_docs/version-2.12/reference/targets/scala_junit_tests.mdx index 149017822..01d9da13c 100644 --- a/versioned_docs/version-2.12/reference/targets/scala_junit_tests.mdx +++ b/versioned_docs/version-2.12/reference/targets/scala_junit_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.scala` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -65,9 +65,9 @@ Example: `sources=['example.ext', 'test_*.ext', '!test_ignore.ext']`. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.12/reference/targets/scala_source.mdx b/versioned_docs/version-2.12/reference/targets/scala_source.mdx index de0bda358..c4d84b636 100644 --- a/versioned_docs/version-2.12/reference/targets/scala_source.mdx +++ b/versioned_docs/version-2.12/reference/targets/scala_source.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.scala` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.12/reference/targets/scala_sources.mdx b/versioned_docs/version-2.12/reference/targets/scala_sources.mdx index 1f474d351..390af530e 100644 --- a/versioned_docs/version-2.12/reference/targets/scala_sources.mdx +++ b/versioned_docs/version-2.12/reference/targets/scala_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.scala` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -77,9 +77,9 @@ If true, don't run `scalafmt` on this target's code. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.12/reference/targets/scalac_plugin.mdx b/versioned_docs/version-2.12/reference/targets/scalac_plugin.mdx index 53c633e66..2d5fa0e60 100644 --- a/versioned_docs/version-2.12/reference/targets/scalac_plugin.mdx +++ b/versioned_docs/version-2.12/reference/targets/scalac_plugin.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.scala` @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.12/reference/targets/scalatest_test.mdx b/versioned_docs/version-2.12/reference/targets/scalatest_test.mdx index 996519a7c..7d8d793bb 100644 --- a/versioned_docs/version-2.12/reference/targets/scalatest_test.mdx +++ b/versioned_docs/version-2.12/reference/targets/scalatest_test.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.scala` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.12/reference/targets/scalatest_tests.mdx b/versioned_docs/version-2.12/reference/targets/scalatest_tests.mdx index 1f93c4be6..cc16fff85 100644 --- a/versioned_docs/version-2.12/reference/targets/scalatest_tests.mdx +++ b/versioned_docs/version-2.12/reference/targets/scalatest_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.scala` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -65,9 +65,9 @@ Example: `sources=['example.ext', 'test_*.ext', '!test_ignore.ext']`. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.12/reference/targets/shell_source.mdx b/versioned_docs/version-2.12/reference/targets/shell_source.mdx index 6b2142fb0..0f6d14c3a 100644 --- a/versioned_docs/version-2.12/reference/targets/shell_source.mdx +++ b/versioned_docs/version-2.12/reference/targets/shell_source.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.12/reference/targets/shell_sources.mdx b/versioned_docs/version-2.12/reference/targets/shell_sources.mdx index 768c9cfa8..26dd00b37 100644 --- a/versioned_docs/version-2.12/reference/targets/shell_sources.mdx +++ b/versioned_docs/version-2.12/reference/targets/shell_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -118,9 +118,9 @@ If true, don't run shfmt on this target's code. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.12/reference/targets/shunit2_test.mdx b/versioned_docs/version-2.12/reference/targets/shunit2_test.mdx index 4d571d5eb..22c2e3615 100644 --- a/versioned_docs/version-2.12/reference/targets/shunit2_test.mdx +++ b/versioned_docs/version-2.12/reference/targets/shunit2_test.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -67,9 +67,9 @@ Path is relative to the BUILD file's directory, e.g. `source='example.ext'` Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -119,11 +119,11 @@ Which shell to run the tests with. If unspecified, Pants will look for a shebang default_repr={`None`} > -Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run. +Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/pants package` goal and whose resulting artifacts should be included in the test run. -Pants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). +Pants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). -You can include anything that can be built by `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`. +You can include anything that can be built by `/home/josh/work/scie-pants/dist/pants package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`. diff --git a/versioned_docs/version-2.12/reference/targets/shunit2_tests.mdx b/versioned_docs/version-2.12/reference/targets/shunit2_tests.mdx index d7d62f03e..e00aac8f5 100644 --- a/versioned_docs/version-2.12/reference/targets/shunit2_tests.mdx +++ b/versioned_docs/version-2.12/reference/targets/shunit2_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -118,9 +118,9 @@ If true, don't run shfmt on this target's code. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -170,11 +170,11 @@ Which shell to run the tests with. If unspecified, Pants will look for a shebang default_repr={`None`} > -Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run. +Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/pants package` goal and whose resulting artifacts should be included in the test run. -Pants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). +Pants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). -You can include anything that can be built by `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`. +You can include anything that can be built by `/home/josh/work/scie-pants/dist/pants package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`. diff --git a/versioned_docs/version-2.12/reference/targets/target.mdx b/versioned_docs/version-2.12/reference/targets/target.mdx index 05343d61a..aba6af9e3 100644 --- a/versioned_docs/version-2.12/reference/targets/target.mdx +++ b/versioned_docs/version-2.12/reference/targets/target.mdx @@ -26,7 +26,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -52,9 +52,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.12/reference/targets/terraform_module.mdx b/versioned_docs/version-2.12/reference/targets/terraform_module.mdx index 4a762c9e7..26f8f2a47 100644 --- a/versioned_docs/version-2.12/reference/targets/terraform_module.mdx +++ b/versioned_docs/version-2.12/reference/targets/terraform_module.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.terraform` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -54,9 +54,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.12/reference/targets/thrift_source.mdx b/versioned_docs/version-2.12/reference/targets/thrift_source.mdx index bd5ccea4c..12753d0ab 100644 --- a/versioned_docs/version-2.12/reference/targets/thrift_source.mdx +++ b/versioned_docs/version-2.12/reference/targets/thrift_source.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.codegen.thrift.apache.p Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -52,9 +52,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.12/reference/targets/thrift_sources.mdx b/versioned_docs/version-2.12/reference/targets/thrift_sources.mdx index c69fef779..084509c09 100644 --- a/versioned_docs/version-2.12/reference/targets/thrift_sources.mdx +++ b/versioned_docs/version-2.12/reference/targets/thrift_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.codegen.thrift.apache.p Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -109,9 +109,9 @@ All dependencies must share the same value for their `resolve` field. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.12/docs/targets#target-addresses and https://www.pantsbuild.org/v2.12/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.13/reference/global-options.mdx b/versioned_docs/version-2.13/reference/global-options.mdx index 753e342a5..1da6a0de5 100644 --- a/versioned_docs/version-2.13/reference/global-options.mdx +++ b/versioned_docs/version-2.13/reference/global-options.mdx @@ -220,13 +220,13 @@ Run goals continuously as file changes are detected. default_repr={`True`} > -If true, Pants will use the old, deprecated semantics for directory arguments like `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 test dir`: directories are shorthand for the target `dir:dir`, i.e. the target that leaves off `name=`. +If true, Pants will use the old, deprecated semantics for directory arguments like `/home/josh/work/scie-pants/dist/pants test dir`: directories are shorthand for the target `dir:dir`, i.e. the target that leaves off `name=`. -If false, Pants will use the new semantics: directory arguments will match all files and targets in the directory, e.g. `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 test dir` will run all tests in `dir`. +If false, Pants will use the new semantics: directory arguments will match all files and targets in the directory, e.g. `/home/josh/work/scie-pants/dist/pants test dir` will run all tests in `dir`. The new semantics will become the default in Pants 2.14, and the old semantics will be removed in 2.15. -This also impacts the behavior of the `tailor` goal. If this option is true, `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 tailor` without additional arguments will run over the whole project, and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 tailor dir` will run over `dir` and all recursive sub-directories. If false, you must specify arguments, like `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 tailor ::` to run over the whole project; specifying a directory will only add targets for that directory. +This also impacts the behavior of the `tailor` goal. If this option is true, `/home/josh/work/scie-pants/dist/pants tailor` without additional arguments will run over the whole project, and `/home/josh/work/scie-pants/dist/pants tailor dir` will run over `dir` and all recursive sub-directories. If false, you must specify arguments, like `/home/josh/work/scie-pants/dist/pants tailor ::` to run over the whole project; specifying a directory will only add targets for that directory. @@ -353,9 +353,9 @@ ignore_warnings = [ Use this Pants version. Note that Pants only uses this to verify that you are using the requested version, as Pants cannot dynamically change the version it is using once the program is already running. -If you use the `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64` script from https://www.pantsbuild.org/v2.13/docs/installation, however, changing the value in your `pants.toml` will cause the new version to be installed and run automatically. +If you use the `/home/josh/work/scie-pants/dist/pants` script from https://www.pantsbuild.org/v2.13/docs/installation, however, changing the value in your `pants.toml` will cause the new version to be installed and run automatically. -Run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --version` to check what is being used. +Run `/home/josh/work/scie-pants/dist/pants --version` to check what is being used. @@ -856,7 +856,7 @@ Whether or not to use nailgun to run JVM requests that are marked as supporting default_repr={`3`} > -The time in seconds to wait when gracefully shutting down an interactive process (such as one opened using `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 run`) before killing it. +The time in seconds to wait when gracefully shutting down an interactive process (such as one opened using `/home/josh/work/scie-pants/dist/pants run`) before killing it. diff --git a/versioned_docs/version-2.13/reference/goals/experimental-bsp.mdx b/versioned_docs/version-2.13/reference/goals/experimental-bsp.mdx index d6c922d3b..9601d9650 100644 --- a/versioned_docs/version-2.13/reference/goals/experimental-bsp.mdx +++ b/versioned_docs/version-2.13/reference/goals/experimental-bsp.mdx @@ -79,7 +79,7 @@ Run the Build Server Protocol server. Pants will receive BSP RPC requests via th Environment variables to set in the BSP runner script when setting up BSP in a repository. Entries are either strings in the form `ENV_VAR=value` to set an explicit value; or just `ENV_VAR` to copy the value from Pants' own environment when the experimental-bsp goal was run. -This option only takes effect when the BSP runner script is written. If the option changes, you must run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 experimental-bsp` again to write a new copy of the BSP runner script. +This option only takes effect when the BSP runner script is written. If the option changes, you must run `/home/josh/work/scie-pants/dist/pants experimental-bsp` again to write a new copy of the BSP runner script. Note: The environment variables passed to the Pants BSP server will be those set for your IDE and not your shell. For example, on macOS, the IDE is generally launched by `launchd` after clicking on a Dock icon, and not from the shell. Thus, any environment variables set for your shell will likely not be seen by the Pants BSP server. At the very least, on macOS consider writing an explicit PATH into the BSP runner script via this option. diff --git a/versioned_docs/version-2.13/reference/goals/generate-lockfiles.mdx b/versioned_docs/version-2.13/reference/goals/generate-lockfiles.mdx index b08aaff9a..90348459c 100644 --- a/versioned_docs/version-2.13/reference/goals/generate-lockfiles.mdx +++ b/versioned_docs/version-2.13/reference/goals/generate-lockfiles.mdx @@ -33,7 +33,7 @@ Only generate lockfiles for the specified resolve(s). Resolves are the logical names for the different lockfiles used in your project. For your own code's dependencies, these come from the option `[python].resolves`. For tool lockfiles, resolve names are the options scope for that tool such as `black`, `pytest`, and `mypy-protobuf`. -For example, you can run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=black --resolve=pytest --resolve=data-science` to only generate lockfiles for those two tools and your resolve named `data-science`. +For example, you can run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=black --resolve=pytest --resolve=data-science` to only generate lockfiles for those two tools and your resolve named `data-science`. If you specify an invalid resolve name, like 'fake', Pants will output all possible values. @@ -51,7 +51,7 @@ If not specified, Pants will generate lockfiles for all resolves. default_repr={`None`} > -If set, lockfile headers will say to run this command to regenerate the lockfile, rather than running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=` like normal. +If set, lockfile headers will say to run this command to regenerate the lockfile, rather than running `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=` like normal. diff --git a/versioned_docs/version-2.13/reference/goals/lint.mdx b/versioned_docs/version-2.13/reference/goals/lint.mdx index 982edaa1c..d7419e44f 100644 --- a/versioned_docs/version-2.13/reference/goals/lint.mdx +++ b/versioned_docs/version-2.13/reference/goals/lint.mdx @@ -47,7 +47,7 @@ You can repeat this option, e.g. `lint --only=flake8 --only=shellcheck` or `lint If true, skip running all formatters in check-only mode. -FYI: when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt lint ::`, there should be little performance benefit to using this flag. Pants will reuse the results from `fmt` when running `lint`. +FYI: when running `/home/josh/work/scie-pants/dist/pants fmt lint ::`, there should be little performance benefit to using this flag. Pants will reuse the results from `fmt` when running `lint`. diff --git a/versioned_docs/version-2.13/reference/help-all.json b/versioned_docs/version-2.13/reference/help-all.json index 0215099f9..e92211116 100644 --- a/versioned_docs/version-2.13/reference/help-all.json +++ b/versioned_docs/version-2.13/reference/help-all.json @@ -26989,7 +26989,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -26997,7 +26997,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -27005,7 +27005,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -27013,7 +27013,7 @@ { "alias": "packages", "default": null, - "description": "Addresses to any targets that can be built with `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, e.g. `[\"project:app\"]`.\n\nPants will build the assets as if you had run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`. It will include the results in your archive using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or even another `archive`.", + "description": "Addresses to any targets that can be built with `/home/josh/work/scie-pants/dist/pants package`, e.g. `[\"project:app\"]`.\n\nPants will build the assets as if you had run `/home/josh/work/scie-pants/dist/pants package`. It will include the results in your archive using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `/home/josh/work/scie-pants/dist/pants package`, e.g. a `pex_binary`, `python_awslambda`, or even another `archive`.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -27045,7 +27045,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -27053,7 +27053,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -27061,7 +27061,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -27069,7 +27069,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -27117,7 +27117,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -27125,7 +27125,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -27141,7 +27141,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -27221,7 +27221,7 @@ { "alias": "skip_push", "default": "False", - "description": "If set to true, do not push this image to registries when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 publish`.", + "description": "If set to true, do not push this image to registries when running `/home/josh/work/scie-pants/dist/pants publish`.", "provider": "", "required": false, "type_hint": "bool" @@ -27261,7 +27261,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -27269,7 +27269,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -27277,7 +27277,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -27309,7 +27309,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -27317,7 +27317,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -27325,7 +27325,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -27389,7 +27389,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -27397,7 +27397,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -27405,7 +27405,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -27429,7 +27429,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -27437,7 +27437,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -27461,7 +27461,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -27477,7 +27477,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -27485,7 +27485,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -27493,7 +27493,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -27525,7 +27525,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -27533,7 +27533,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -27549,7 +27549,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -27557,7 +27557,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -27565,7 +27565,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -27621,7 +27621,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -27629,7 +27629,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -27637,7 +27637,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -27661,7 +27661,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -27669,7 +27669,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -27717,7 +27717,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -27725,7 +27725,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -27749,7 +27749,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -27757,7 +27757,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built directory tree should be located.\n\nIf undefined, this will use the path to the BUILD file, For example, `src/charts/mychart:tgt_name` would be `src.charts.mychart/tgt_name/`.\n\nRegardless of whether you use the default or set this field, the path will end with Helms's file format of `-.tgz`, where `chart_name` and `chart_version` are the values extracted from the Chart.yaml file. So, using the default for this field, the target `src/charts/mychart:tgt_name` might have a final path like `src.charts.mychart/tgt_name/mychart-0.1.0.tgz`.\n\nWhen running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built directory tree should be located.\n\nIf undefined, this will use the path to the BUILD file, For example, `src/charts/mychart:tgt_name` would be `src.charts.mychart/tgt_name/`.\n\nRegardless of whether you use the default or set this field, the path will end with Helms's file format of `-.tgz`, where `chart_name` and `chart_version` are the values extracted from the Chart.yaml file. So, using the default for this field, the target `src/charts/mychart:tgt_name` might have a final path like `src.charts.mychart/tgt_name/mychart-0.1.0.tgz`.\n\nWhen running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -27789,7 +27789,7 @@ { "alias": "skip_push", "default": "False", - "description": "If set to true, do not push this Helm chart to registries when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 publish`.", + "description": "If set to true, do not push this Helm chart to registries when running `/home/josh/work/scie-pants/dist/pants publish`.", "provider": "", "required": false, "type_hint": "bool" @@ -27797,7 +27797,7 @@ { "alias": "skip_lint", "default": "False", - "description": "If set to true, do not run any linting in this Helm chart when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "description": "If set to true, do not run any linting in this Helm chart when running `/home/josh/work/scie-pants/dist/pants lint`.", "provider": "", "required": false, "type_hint": "bool" @@ -27813,7 +27813,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -27821,7 +27821,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -27837,7 +27837,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -27853,7 +27853,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -27861,7 +27861,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -27877,7 +27877,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -27885,7 +27885,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -27901,7 +27901,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -27909,7 +27909,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -27917,7 +27917,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -27973,7 +27973,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -27981,7 +27981,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -28005,7 +28005,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -28045,7 +28045,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -28053,7 +28053,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -28069,7 +28069,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -28109,7 +28109,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -28117,7 +28117,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -28133,7 +28133,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -28173,7 +28173,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -28181,7 +28181,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -28261,7 +28261,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -28269,7 +28269,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -28293,7 +28293,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -28309,7 +28309,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -28325,7 +28325,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -28333,7 +28333,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -28341,7 +28341,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -28397,7 +28397,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -28405,7 +28405,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -28421,7 +28421,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -28469,7 +28469,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -28477,7 +28477,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -28485,7 +28485,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -28549,7 +28549,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -28557,7 +28557,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -28581,7 +28581,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -28629,7 +28629,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -28637,7 +28637,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -28677,7 +28677,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -28685,7 +28685,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -28717,7 +28717,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -28725,7 +28725,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -28765,7 +28765,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -28893,7 +28893,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -28901,7 +28901,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -28925,7 +28925,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -29061,7 +29061,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -29077,7 +29077,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -29085,7 +29085,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -29141,7 +29141,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -29149,7 +29149,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -29205,7 +29205,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -29213,7 +29213,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -29221,7 +29221,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -29309,7 +29309,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -29317,7 +29317,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -29405,7 +29405,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -29421,7 +29421,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -29429,7 +29429,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -29437,7 +29437,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built directory tree should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:bin` would be `src.python.project/bin/`.\n\nRegardless of whether you use the default or set this field, the path will end with PyOxidizer's file format of `/{debug,release}/install/`, where `platform` is a Rust platform triplet like `aarch-64-apple-darwin` and `binary_name` is the `name` of the `pyoxidizer_target`. So, using the default for this field, the target `src/python/project:bin` might have a final path like `src.python.project/bin/aarch-64-apple-darwin/release/bin`.\n\nWhen running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built directory tree should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:bin` would be `src.python.project/bin/`.\n\nRegardless of whether you use the default or set this field, the path will end with PyOxidizer's file format of `/{debug,release}/install/`, where `platform` is a Rust platform triplet like `aarch-64-apple-darwin` and `binary_name` is the `name` of the `pyoxidizer_target`. So, using the default for this field, the target `src/python/project:bin` might have a final path like `src.python.project/bin/aarch-64-apple-darwin/release/bin`.\n\nWhen running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -29485,7 +29485,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -29493,7 +29493,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -29501,7 +29501,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -29509,7 +29509,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -29565,7 +29565,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -29573,7 +29573,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -29589,7 +29589,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -29597,7 +29597,7 @@ { "alias": "entry_points", "default": null, - "description": "Any entry points, such as `console_scripts` and `gui_scripts`.\n\nSpecify as a nested dictionary, with a dictionary for each type of entry point, e.g. `console_scripts` vs. `gui_scripts`. Each dictionary maps the entry point name to either a setuptools entry point (\"path.to.module:func\") or a Pants target address to a pex_binary target.\n\n Example:\n\n entry_points={\n \"console_scripts\": {\n \"my-script\": \"project.app:main\",\n \"another-script\": \"project/subdir:pex_binary_tgt\"\n }\n }\n\nNote that Pants will assume that any value that either starts with `:` or has `/` in it, is a target address to a pex_binary target. Otherwise, it will assume it's a setuptools entry point as defined by https://packaging.python.org/specifications/entry-points/#entry-points-specification. Use `//` as a prefix for target addresses if you need to disambiguate.\n\nPants will attempt to infer dependencies, which you can confirm by running:\n\n /home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies ", + "description": "Any entry points, such as `console_scripts` and `gui_scripts`.\n\nSpecify as a nested dictionary, with a dictionary for each type of entry point, e.g. `console_scripts` vs. `gui_scripts`. Each dictionary maps the entry point name to either a setuptools entry point (\"path.to.module:func\") or a Pants target address to a pex_binary target.\n\n Example:\n\n entry_points={\n \"console_scripts\": {\n \"my-script\": \"project.app:main\",\n \"another-script\": \"project/subdir:pex_binary_tgt\"\n }\n }\n\nNote that Pants will assume that any value that either starts with `:` or has `/` in it, is a target address to a pex_binary target. Otherwise, it will assume it's a setuptools entry point as defined by https://packaging.python.org/specifications/entry-points/#entry-points-specification. Use `//` as a prefix for target addresses if you need to disambiguate.\n\nPants will attempt to infer dependencies, which you can confirm by running:\n\n /home/josh/work/scie-pants/dist/pants dependencies ", "provider": "", "required": false, "type_hint": "Dict[str, Dict[str, str]] | None" @@ -29701,7 +29701,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -29709,7 +29709,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -29717,7 +29717,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -29725,7 +29725,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -29781,7 +29781,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -29789,7 +29789,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -29797,7 +29797,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -29845,7 +29845,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -29853,7 +29853,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -29909,7 +29909,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -29917,7 +29917,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -29933,7 +29933,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -30053,7 +30053,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -30061,7 +30061,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -30181,7 +30181,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -30205,7 +30205,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -30213,7 +30213,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -30221,7 +30221,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -30253,7 +30253,7 @@ { "alias": "runtime_package_dependencies", "default": null, - "description": "Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`.", + "description": "Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/pants package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `/home/josh/work/scie-pants/dist/pants package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -30285,7 +30285,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -30389,7 +30389,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -30397,7 +30397,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -30517,7 +30517,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -30541,7 +30541,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -30549,7 +30549,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -30653,7 +30653,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -30685,7 +30685,7 @@ { "alias": "runtime_package_dependencies", "default": null, - "description": "Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`.", + "description": "Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/pants package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `/home/josh/work/scie-pants/dist/pants package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -30725,7 +30725,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -30733,7 +30733,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -30773,7 +30773,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -30781,7 +30781,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -30789,7 +30789,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -30813,7 +30813,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -30821,7 +30821,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -30845,7 +30845,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -30861,7 +30861,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -30869,7 +30869,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -30877,7 +30877,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -30933,7 +30933,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -30941,7 +30941,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -30965,7 +30965,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -31013,7 +31013,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -31021,7 +31021,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -31029,7 +31029,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -31093,7 +31093,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -31101,7 +31101,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -31133,7 +31133,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -31181,7 +31181,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -31189,7 +31189,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -31221,7 +31221,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -31229,7 +31229,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -31237,7 +31237,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -31293,7 +31293,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -31301,7 +31301,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -31325,7 +31325,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -31373,7 +31373,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -31381,7 +31381,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -31389,7 +31389,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -31429,7 +31429,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -31437,7 +31437,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -31477,7 +31477,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -31493,7 +31493,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -31501,7 +31501,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -31517,7 +31517,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -31549,7 +31549,7 @@ { "alias": "runtime_package_dependencies", "default": null, - "description": "Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`.", + "description": "Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/pants package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `/home/josh/work/scie-pants/dist/pants package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -31581,7 +31581,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -31589,7 +31589,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -31629,7 +31629,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -31661,7 +31661,7 @@ { "alias": "runtime_package_dependencies", "default": null, - "description": "Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`.", + "description": "Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/pants package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `/home/josh/work/scie-pants/dist/pants package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -31677,7 +31677,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -31685,7 +31685,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -31693,7 +31693,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -31709,7 +31709,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -31717,7 +31717,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -31725,7 +31725,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -31749,7 +31749,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -31757,7 +31757,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -31765,7 +31765,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -31797,7 +31797,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -31805,7 +31805,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -31837,7 +31837,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -31853,7 +31853,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -31861,7 +31861,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -32198,7 +32198,7 @@ "deprecation_active": false, "display_args": ["--pants-version="], "env_var": "PANTS_VERSION", - "help": "Use this Pants version. Note that Pants only uses this to verify that you are using the requested version, as Pants cannot dynamically change the version it is using once the program is already running.\n\nIf you use the `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64` script from https://www.pantsbuild.org/v2.13/docs/installation, however, changing the value in your `pants.toml` will cause the new version to be installed and run automatically.\n\nRun `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --version` to check what is being used.", + "help": "Use this Pants version. Note that Pants only uses this to verify that you are using the requested version, as Pants cannot dynamically change the version it is using once the program is already running.\n\nIf you use the `/home/josh/work/scie-pants/dist/pants` script from https://www.pantsbuild.org/v2.13/docs/installation, however, changing the value in your `pants.toml` will cause the new version to be installed and run automatically.\n\nRun `/home/josh/work/scie-pants/dist/pants --version` to check what is being used.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pants-version"], @@ -32255,7 +32255,7 @@ { "details": "from env var PANTS_BIN_NAME", "rank": "ENVIRONMENT", - "value": "/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64" + "value": "/home/josh/work/scie-pants/dist/pants" } ] } @@ -33393,7 +33393,7 @@ "--process-execution-graceful-shutdown-timeout=" ], "env_var": "PANTS_PROCESS_EXECUTION_GRACEFUL_SHUTDOWN_TIMEOUT", - "help": "The time in seconds to wait when gracefully shutting down an interactive process (such as one opened using `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 run`) before killing it.", + "help": "The time in seconds to wait when gracefully shutting down an interactive process (such as one opened using `/home/josh/work/scie-pants/dist/pants run`) before killing it.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -34858,7 +34858,7 @@ "--[no-]use-deprecated-directory-cli-args-semantics" ], "env_var": "PANTS_USE_DEPRECATED_DIRECTORY_CLI_ARGS_SEMANTICS", - "help": "If true, Pants will use the old, deprecated semantics for directory arguments like `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 test dir`: directories are shorthand for the target `dir:dir`, i.e. the target that leaves off `name=`.\n\nIf false, Pants will use the new semantics: directory arguments will match all files and targets in the directory, e.g. `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 test dir` will run all tests in `dir`.\n\nThe new semantics will become the default in Pants 2.14, and the old semantics will be removed in 2.15.\n\nThis also impacts the behavior of the `tailor` goal. If this option is true, `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 tailor` without additional arguments will run over the whole project, and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 tailor dir` will run over `dir` and all recursive sub-directories. If false, you must specify arguments, like `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 tailor ::` to run over the whole project; specifying a directory will only add targets for that directory.", + "help": "If true, Pants will use the old, deprecated semantics for directory arguments like `/home/josh/work/scie-pants/dist/pants test dir`: directories are shorthand for the target `dir:dir`, i.e. the target that leaves off `name=`.\n\nIf false, Pants will use the new semantics: directory arguments will match all files and targets in the directory, e.g. `/home/josh/work/scie-pants/dist/pants test dir` will run all tests in `dir`.\n\nThe new semantics will become the default in Pants 2.14, and the old semantics will be removed in 2.15.\n\nThis also impacts the behavior of the `tailor` goal. If this option is true, `/home/josh/work/scie-pants/dist/pants tailor` without additional arguments will run over the whole project, and `/home/josh/work/scie-pants/dist/pants tailor dir` will run over `dir` and all recursive sub-directories. If false, you must specify arguments, like `/home/josh/work/scie-pants/dist/pants tailor ::` to run over the whole project; specifying a directory will only add targets for that directory.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -35322,7 +35322,7 @@ "deprecation_active": false, "display_args": ["--autoflake-lockfile="], "env_var": "PANTS_AUTOFLAKE_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/backend/python/lint/autoflake/autoflake.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=autoflake`.\n\nAs explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/backend/python/lint/autoflake/autoflake.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=autoflake`.\n\nAs explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--autoflake-lockfile"], @@ -35412,7 +35412,7 @@ "deprecation_active": false, "display_args": ["--[no-]autoflake-skip"], "env_var": "PANTS_AUTOFLAKE_SKIP", - "help": "Don't use Autoflake when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use Autoflake when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--autoflake-skip", "--no-autoflake-skip"], @@ -35476,7 +35476,7 @@ "deprecation_active": false, "display_args": ["--[no-]autoflake-export"], "env_var": "PANTS_AUTOFLAKE_EXPORT", - "help": "If true, export a virtual environment with Autoflake when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with Autoflake when running `/home/josh/work/scie-pants/dist/pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -35584,7 +35584,7 @@ "deprecation_active": false, "display_args": ["--bandit-lockfile="], "env_var": "PANTS_BANDIT_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/backend/python/lint/bandit/bandit.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=bandit`.\n\nAs explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/backend/python/lint/bandit/bandit.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=bandit`.\n\nAs explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--bandit-lockfile"], @@ -35700,7 +35700,7 @@ "deprecation_active": false, "display_args": ["--[no-]bandit-skip"], "env_var": "PANTS_BANDIT_SKIP", - "help": "Don't use Bandit when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use Bandit when running `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--bandit-skip", "--no-bandit-skip"], @@ -35762,7 +35762,7 @@ "deprecation_active": false, "display_args": ["--[no-]bandit-export"], "env_var": "PANTS_BANDIT_EXPORT", - "help": "If true, export a virtual environment with Bandit when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with Bandit when running `/home/josh/work/scie-pants/dist/pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--bandit-export", "--no-bandit-export"], @@ -35902,7 +35902,7 @@ "deprecation_active": false, "display_args": ["--black-lockfile="], "env_var": "PANTS_BLACK_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/backend/python/lint/black/black.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=black`.\n\nAs explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/backend/python/lint/black/black.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=black`.\n\nAs explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--black-lockfile"], @@ -36055,7 +36055,7 @@ "deprecation_active": false, "display_args": ["--[no-]black-skip"], "env_var": "PANTS_BLACK_SKIP", - "help": "Don't use Black when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use Black when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--black-skip", "--no-black-skip"], @@ -36117,7 +36117,7 @@ "deprecation_active": false, "display_args": ["--[no-]black-export"], "env_var": "PANTS_BLACK_EXPORT", - "help": "If true, export a virtual environment with Black when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with Black when running `/home/josh/work/scie-pants/dist/pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--black-export", "--no-black-export"], @@ -36339,7 +36339,7 @@ "deprecation_active": false, "display_args": ["--[no-]buf-format-skip"], "env_var": "PANTS_BUF_FORMAT_SKIP", - "help": "Don't use Buf when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use Buf when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--buf-format-skip", "--no-buf-format-skip"], @@ -36370,7 +36370,7 @@ "deprecation_active": false, "display_args": ["--[no-]buf-lint-skip"], "env_var": "PANTS_BUF_LINT_SKIP", - "help": "Don't use Buf when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use Buf when running `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--buf-lint-skip", "--no-buf-lint-skip"], @@ -36614,7 +36614,7 @@ "deprecation_active": false, "display_args": ["--cli-alias=\"{'key1': val1, 'key2': val2, ...}\""], "env_var": "PANTS_CLI_ALIAS", - "help": "Register command line aliases.\n\nExample:\n\n [cli.alias]\n green = \"fmt lint check\"\n all-changed = \"--changed-since=HEAD --changed-dependees=transitive\"\n\nThis would allow you to run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 green all-changed`, which is shorthand for `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt lint check --changed-since=HEAD --changed-dependees=transitive`.\n\nNotice: this option must be placed in a config file (e.g. `pants.toml` or `pantsrc`) to have any effect.", + "help": "Register command line aliases.\n\nExample:\n\n [cli.alias]\n green = \"fmt lint check\"\n all-changed = \"--changed-since=HEAD --changed-dependees=transitive\"\n\nThis would allow you to run `/home/josh/work/scie-pants/dist/pants green all-changed`, which is shorthand for `/home/josh/work/scie-pants/dist/pants fmt lint check --changed-since=HEAD --changed-dependees=transitive`.\n\nNotice: this option must be placed in a config file (e.g. `pants.toml` or `pantsrc`) to have any effect.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--cli-alias"], @@ -37000,7 +37000,7 @@ "deprecation_active": false, "display_args": ["--coverage-py-lockfile="], "env_var": "PANTS_COVERAGE_PY_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/backend/python/subsystems/coverage_py.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=coverage-py`.\n\nAs explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/backend/python/subsystems/coverage_py.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=coverage-py`.\n\nAs explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--coverage-py-lockfile"], @@ -37488,7 +37488,7 @@ "deprecation_active": false, "display_args": ["--debugpy-lockfile="], "env_var": "PANTS_DEBUGPY_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/backend/python/subsystems/debugpy.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=debugpy`.\n\nAs explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/backend/python/subsystems/debugpy.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=debugpy`.\n\nAs explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--debugpy-lockfile"], @@ -37990,7 +37990,7 @@ "deprecation_active": false, "display_args": ["--docformatter-lockfile="], "env_var": "PANTS_DOCFORMATTER_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/backend/python/lint/docformatter/docformatter.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=docformatter`.\n\nAs explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/backend/python/lint/docformatter/docformatter.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=docformatter`.\n\nAs explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--docformatter-lockfile"], @@ -38080,7 +38080,7 @@ "deprecation_active": false, "display_args": ["--[no-]docformatter-skip"], "env_var": "PANTS_DOCFORMATTER_SKIP", - "help": "Don't use docformatter when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use docformatter when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -38147,7 +38147,7 @@ "deprecation_active": false, "display_args": ["--[no-]docformatter-export"], "env_var": "PANTS_DOCFORMATTER_EXPORT", - "help": "If true, export a virtual environment with docformatter when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with docformatter when running `/home/josh/work/scie-pants/dist/pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -38511,7 +38511,7 @@ "--docker-run-args=\"[, , ...]\"" ], "env_var": "PANTS_DOCKER_RUN_ARGS", - "help": "Additional arguments to use for `docker run` invocations.\n\nExample:\n\n $ /home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 run --docker-run-args=\"-p 127.0.0.1:80:8080/tcp --name demo\" src/example:image -- [image entrypoint args]\n\nTo provide the top-level options to the `docker` client, use `[docker].env_vars` to configure the [Environment variables](https://docs.docker.com/engine/reference/commandline/cli/#environment-variables) as appropriate.\n\nThe arguments for the image entrypoint may be passed on the command line after a double dash (`--`), or using the `--run-args` option.\n\nDefaults to `--interactive --tty` when stdout is connected to a terminal.", + "help": "Additional arguments to use for `docker run` invocations.\n\nExample:\n\n $ /home/josh/work/scie-pants/dist/pants run --docker-run-args=\"-p 127.0.0.1:80:8080/tcp --name demo\" src/example:image -- [image entrypoint args]\n\nTo provide the top-level options to the `docker` client, use `[docker].env_vars` to configure the [Environment variables](https://docs.docker.com/engine/reference/commandline/cli/#environment-variables) as appropriate.\n\nThe arguments for the image entrypoint may be passed on the command line after a double dash (`--`), or using the `--run-args` option.\n\nDefaults to `--interactive --tty` when stdout is connected to a terminal.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--docker-run-args"], @@ -38651,7 +38651,7 @@ "deprecation_active": false, "display_args": ["--dockerfile-parser-lockfile="], "env_var": "PANTS_DOCKERFILE_PARSER_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/backend/docker/subsystems/dockerfile.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=dockerfile-parser`.\n\nAs explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/backend/docker/subsystems/dockerfile.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=dockerfile-parser`.\n\nAs explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--dockerfile-parser-lockfile"], @@ -38953,7 +38953,7 @@ "--experimental-bsp-runner-env-vars=\"['', '', ...]\"" ], "env_var": "PANTS_EXPERIMENTAL_BSP_RUNNER_ENV_VARS", - "help": "Environment variables to set in the BSP runner script when setting up BSP in a repository. Entries are either strings in the form `ENV_VAR=value` to set an explicit value; or just `ENV_VAR` to copy the value from Pants' own environment when the experimental-bsp goal was run.\n\nThis option only takes effect when the BSP runner script is written. If the option changes, you must run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 experimental-bsp` again to write a new copy of the BSP runner script.\n\nNote: The environment variables passed to the Pants BSP server will be those set for your IDE and not your shell. For example, on macOS, the IDE is generally launched by `launchd` after clicking on a Dock icon, and not from the shell. Thus, any environment variables set for your shell will likely not be seen by the Pants BSP server. At the very least, on macOS consider writing an explicit PATH into the BSP runner script via this option.", + "help": "Environment variables to set in the BSP runner script when setting up BSP in a repository. Entries are either strings in the form `ENV_VAR=value` to set an explicit value; or just `ENV_VAR` to copy the value from Pants' own environment when the experimental-bsp goal was run.\n\nThis option only takes effect when the BSP runner script is written. If the option changes, you must run `/home/josh/work/scie-pants/dist/pants experimental-bsp` again to write a new copy of the BSP runner script.\n\nNote: The environment variables passed to the Pants BSP server will be those set for your IDE and not your shell. For example, on macOS, the IDE is generally launched by `launchd` after clicking on a Dock icon, and not from the shell. Thus, any environment variables set for your shell will likely not be seen by the Pants BSP server. At the very least, on macOS consider writing an explicit PATH into the BSP runner script via this option.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--experimental-bsp-runner-env-vars"], @@ -39551,7 +39551,7 @@ "deprecation_active": false, "display_args": ["--flake8-lockfile="], "env_var": "PANTS_FLAKE8_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/backend/python/lint/flake8/flake8.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=flake8`.\n\nAs explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/backend/python/lint/flake8/flake8.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=flake8`.\n\nAs explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--flake8-lockfile"], @@ -39737,7 +39737,7 @@ "deprecation_active": false, "display_args": ["--[no-]flake8-skip"], "env_var": "PANTS_FLAKE8_SKIP", - "help": "Don't use Flake8 when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use Flake8 when running `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--flake8-skip", "--no-flake8-skip"], @@ -39799,7 +39799,7 @@ "deprecation_active": false, "display_args": ["--[no-]flake8-export"], "env_var": "PANTS_FLAKE8_EXPORT", - "help": "If true, export a virtual environment with Flake8 when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with Flake8 when running `/home/josh/work/scie-pants/dist/pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--flake8-export", "--no-flake8-export"], @@ -39914,7 +39914,7 @@ "deprecation_active": false, "display_args": ["--generate-lockfiles-custom-command="], "env_var": "PANTS_GENERATE_LOCKFILES_CUSTOM_COMMAND", - "help": "If set, lockfile headers will say to run this command to regenerate the lockfile, rather than running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=` like normal.", + "help": "If set, lockfile headers will say to run this command to regenerate the lockfile, rather than running `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=` like normal.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--generate-lockfiles-custom-command"], @@ -39944,7 +39944,7 @@ "--generate-lockfiles-resolve=\"['', '', ...]\"" ], "env_var": "PANTS_GENERATE_LOCKFILES_RESOLVE", - "help": "Only generate lockfiles for the specified resolve(s).\n\nResolves are the logical names for the different lockfiles used in your project. For your own code's dependencies, these come from the option `[python].resolves`. For tool lockfiles, resolve names are the options scope for that tool such as `black`, `pytest`, and `mypy-protobuf`.\n\nFor example, you can run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=black --resolve=pytest --resolve=data-science` to only generate lockfiles for those two tools and your resolve named `data-science`.\n\nIf you specify an invalid resolve name, like 'fake', Pants will output all possible values.\n\nIf not specified, Pants will generate lockfiles for all resolves.", + "help": "Only generate lockfiles for the specified resolve(s).\n\nResolves are the logical names for the different lockfiles used in your project. For your own code's dependencies, these come from the option `[python].resolves`. For tool lockfiles, resolve names are the options scope for that tool such as `black`, `pytest`, and `mypy-protobuf`.\n\nFor example, you can run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=black --resolve=pytest --resolve=data-science` to only generate lockfiles for those two tools and your resolve named `data-science`.\n\nIf you specify an invalid resolve name, like 'fake', Pants will output all possible values.\n\nIf not specified, Pants will generate lockfiles for all resolves.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--generate-lockfiles-resolve"], @@ -40031,7 +40031,7 @@ "deprecation_active": false, "display_args": ["--[no-]gofmt-skip"], "env_var": "PANTS_GOFMT_SKIP", - "help": "Don't use gofmt when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use gofmt when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--gofmt-skip", "--no-gofmt-skip"], @@ -40392,7 +40392,7 @@ "deprecation_active": false, "display_args": ["--google-java-format-lockfile="], "env_var": "PANTS_GOOGLE_JAVA_FORMAT_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/backend/java/lint/google_java_format/google_java_format.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=google-java-format`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/backend/java/lint/google_java_format/google_java_format.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=google-java-format`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--google-java-format-lockfile"], @@ -40458,7 +40458,7 @@ "deprecation_active": false, "display_args": ["--[no-]google-java-format-skip"], "env_var": "PANTS_GOOGLE_JAVA_FORMAT_SKIP", - "help": "Don't use Google Java Format when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use Google Java Format when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -40976,7 +40976,7 @@ "deprecation_active": false, "display_args": ["--[no-]hadolint-skip"], "env_var": "PANTS_HADOLINT_SKIP", - "help": "Don't use Hadolint when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use Hadolint when running `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--hadolint-skip", "--no-hadolint-skip"], @@ -41685,7 +41685,7 @@ "deprecation_active": false, "display_args": ["--ipython-lockfile="], "env_var": "PANTS_IPYTHON_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/backend/python/subsystems/ipython.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=ipython`.\n\nAs explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/backend/python/subsystems/ipython.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=ipython`.\n\nAs explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--ipython-lockfile"], @@ -41915,7 +41915,7 @@ "deprecation_active": false, "display_args": ["--isort-lockfile="], "env_var": "PANTS_ISORT_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/backend/python/lint/isort/isort.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=isort`.\n\nAs explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/backend/python/lint/isort/isort.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=isort`.\n\nAs explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--isort-lockfile"], @@ -42075,7 +42075,7 @@ "deprecation_active": false, "display_args": ["--[no-]isort-skip"], "env_var": "PANTS_ISORT_SKIP", - "help": "Don't use isort when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use isort when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--isort-skip", "--no-isort-skip"], @@ -42137,7 +42137,7 @@ "deprecation_active": false, "display_args": ["--[no-]isort-export"], "env_var": "PANTS_ISORT_EXPORT", - "help": "If true, export a virtual environment with isort when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with isort when running `/home/josh/work/scie-pants/dist/pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--isort-export", "--no-isort-export"], @@ -42440,7 +42440,7 @@ "deprecation_active": false, "display_args": ["--junit-lockfile="], "env_var": "PANTS_JUNIT_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/jvm/test/junit.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=junit`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/jvm/test/junit.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=junit`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--junit-lockfile"], @@ -43052,7 +43052,7 @@ "deprecation_active": false, "display_args": ["--ktlint-lockfile="], "env_var": "PANTS_KTLINT_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/backend/kotlin/lint/ktlint/ktlint.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=ktlint`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/backend/kotlin/lint/ktlint/ktlint.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=ktlint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--ktlint-lockfile"], @@ -43116,7 +43116,7 @@ "deprecation_active": false, "display_args": ["--[no-]ktlint-skip"], "env_var": "PANTS_KTLINT_SKIP", - "help": "Don't use Ktlint when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use Ktlint when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--ktlint-skip", "--no-ktlint-skip"], @@ -43254,7 +43254,7 @@ "deprecation_active": false, "display_args": ["--lambdex-lockfile="], "env_var": "PANTS_LAMBDEX_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/backend/python/subsystems/lambdex.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=lambdex`.\n\nAs explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/backend/python/subsystems/lambdex.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=lambdex`.\n\nAs explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--lambdex-lockfile"], @@ -43417,7 +43417,7 @@ "deprecation_active": false, "display_args": ["--[no-]lint-skip-formatters"], "env_var": "PANTS_LINT_SKIP_FORMATTERS", - "help": "If true, skip running all formatters in check-only mode.\n\nFYI: when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt lint ::`, there should be little performance benefit to using this flag. Pants will reuse the results from `fmt` when running `lint`.", + "help": "If true, skip running all formatters in check-only mode.\n\nFYI: when running `/home/josh/work/scie-pants/dist/pants fmt lint ::`, there should be little performance benefit to using this flag. Pants will reuse the results from `fmt` when running `lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -43660,7 +43660,7 @@ "deprecation_active": false, "display_args": ["--mypy-lockfile="], "env_var": "PANTS_MYPY_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/backend/python/typecheck/mypy/mypy.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=mypy`.\n\nAs explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/backend/python/typecheck/mypy/mypy.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=mypy`.\n\nAs explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--mypy-lockfile"], @@ -43879,7 +43879,7 @@ "deprecation_active": false, "display_args": ["--[no-]mypy-skip"], "env_var": "PANTS_MYPY_SKIP", - "help": "Don't use MyPy when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 check`.", + "help": "Don't use MyPy when running `/home/josh/work/scie-pants/dist/pants check`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--mypy-skip", "--no-mypy-skip"], @@ -43941,7 +43941,7 @@ "deprecation_active": false, "display_args": ["--[no-]mypy-export"], "env_var": "PANTS_MYPY_EXPORT", - "help": "If true, export a virtual environment with MyPy when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with MyPy when running `/home/josh/work/scie-pants/dist/pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--mypy-export", "--no-mypy-export"], @@ -44079,7 +44079,7 @@ "deprecation_active": false, "display_args": ["--mypy-protobuf-lockfile="], "env_var": "PANTS_MYPY_PROTOBUF_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/backend/codegen/protobuf/python/mypy_protobuf.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=mypy-protobuf`.\n\nAs explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/backend/codegen/protobuf/python/mypy_protobuf.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=mypy-protobuf`.\n\nAs explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--mypy-protobuf-lockfile"], @@ -45208,7 +45208,7 @@ "deprecation_active": false, "display_args": ["--pylint-lockfile="], "env_var": "PANTS_PYLINT_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/backend/python/lint/pylint/pylint.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=pylint`.\n\nAs explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/backend/python/lint/pylint/pylint.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=pylint`.\n\nAs explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pylint-lockfile"], @@ -45394,7 +45394,7 @@ "deprecation_active": false, "display_args": ["--[no-]pylint-skip"], "env_var": "PANTS_PYLINT_SKIP", - "help": "Don't use Pylint when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use Pylint when running `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pylint-skip", "--no-pylint-skip"], @@ -45456,7 +45456,7 @@ "deprecation_active": false, "display_args": ["--[no-]pylint-export"], "env_var": "PANTS_PYLINT_EXPORT", - "help": "If true, export a virtual environment with Pylint when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with Pylint when running `/home/josh/work/scie-pants/dist/pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pylint-export", "--no-pylint-export"], @@ -45760,7 +45760,7 @@ "deprecation_active": false, "display_args": ["--pytest-lockfile="], "env_var": "PANTS_PYTEST_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/backend/python/subsystems/pytest.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=pytest`.\n\nAs explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/backend/python/subsystems/pytest.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=pytest`.\n\nAs explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pytest-lockfile"], @@ -46061,7 +46061,7 @@ "deprecation_active": false, "display_args": ["--[no-]pytest-export"], "env_var": "PANTS_PYTEST_EXPORT", - "help": "If true, export a virtual environment with Pytest when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with Pytest when running `/home/josh/work/scie-pants/dist/pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pytest-export", "--no-pytest-export"], @@ -46218,7 +46218,7 @@ "--python-resolves=\"{'key1': val1, 'key2': val2, ...}\"" ], "env_var": "PANTS_PYTHON_RESOLVES", - "help": "A mapping of logical names to lockfile paths used in your project.\n\nMany organizations only need a single resolve for their whole project, which is a good default and often the simplest thing to do. However, you may need multiple resolves, such as if you use two conflicting versions of a requirement in your repository.\n\nIf you only need a single resolve, run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles` to generate the lockfile.\n\nIf you need multiple resolves:\n\n 1. Via this option, define multiple resolve names and their lockfile paths. The names should be meaningful to your repository, such as `data-science` or `pants-plugins`.\n 2. Set the default with `[python].default_resolve`.\n 3. Update your `python_requirement` targets with the `resolve` field to declare which resolve they should be available in. They default to `[python].default_resolve`, so you only need to update targets that you want in non-default resolves. (Often you'll set this via the `python_requirements` or `poetry_requirements` target generators)\n 4. Run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles` to generate the lockfiles. If the results aren't what you'd expect, adjust the prior step.\n 5. Update any targets like `python_source` / `python_sources`, `python_test` / `python_tests`, and `pex_binary` which need to set a non-default resolve with the `resolve` field.\n\nIf a target can work with multiple resolves, you can either use the `parametrize` mechanism or manually create a distinct target per resolve. See https://www.pantsbuild.org/v2.13/docs/targets for information about `parametrize`.\n\nFor example:\n\n python_sources(\n resolve=parametrize(\"data-science\", \"web-app\"),\n )\n\nYou can name the lockfile paths what you would like; Pants does not expect a certain file extension or location.\n\nOnly applies if `[python].enable_resolves` is true.", + "help": "A mapping of logical names to lockfile paths used in your project.\n\nMany organizations only need a single resolve for their whole project, which is a good default and often the simplest thing to do. However, you may need multiple resolves, such as if you use two conflicting versions of a requirement in your repository.\n\nIf you only need a single resolve, run `/home/josh/work/scie-pants/dist/pants generate-lockfiles` to generate the lockfile.\n\nIf you need multiple resolves:\n\n 1. Via this option, define multiple resolve names and their lockfile paths. The names should be meaningful to your repository, such as `data-science` or `pants-plugins`.\n 2. Set the default with `[python].default_resolve`.\n 3. Update your `python_requirement` targets with the `resolve` field to declare which resolve they should be available in. They default to `[python].default_resolve`, so you only need to update targets that you want in non-default resolves. (Often you'll set this via the `python_requirements` or `poetry_requirements` target generators)\n 4. Run `/home/josh/work/scie-pants/dist/pants generate-lockfiles` to generate the lockfiles. If the results aren't what you'd expect, adjust the prior step.\n 5. Update any targets like `python_source` / `python_sources`, `python_test` / `python_tests`, and `pex_binary` which need to set a non-default resolve with the `resolve` field.\n\nIf a target can work with multiple resolves, you can either use the `parametrize` mechanism or manually create a distinct target per resolve. See https://www.pantsbuild.org/v2.13/docs/targets for information about `parametrize`.\n\nFor example:\n\n python_sources(\n resolve=parametrize(\"data-science\", \"web-app\"),\n )\n\nYou can name the lockfile paths what you would like; Pants does not expect a certain file extension or location.\n\nOnly applies if `[python].enable_resolves` is true.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--python-resolves"], @@ -46350,7 +46350,7 @@ "deprecation_active": false, "display_args": ["--python-lockfile-generator="], "env_var": "PANTS_PYTHON_LOCKFILE_GENERATOR", - "help": "Whether to use Pex or Poetry with the `generate-lockfiles` goal.\n\nPoetry does not support these features:\n\n 1) `[python-repos]` for custom indexes/cheeseshops.\n 2) VCS (Git) requirements.\n 3) `[GLOBAL].ca_certs_path`.\n\nIf you use any of these features, you should use Pex.\n\nSeveral users have also had issues with how Poetry's lockfile generation handles environment markers for transitive dependencies; certain dependencies end up with nonsensical environment markers which cause the dependency to not be installed, then for Pants/Pex to complain the dependency is missing, even though it's in the lockfile. There is a workaround: for `[python].resolves`, manually create a `python_requirement` target for the problematic transitive dependencies so that they are seen as direct requirements, rather than transitive. For tool lockfiles, add the problematic transitive dependency to `[tool].extra_requirements`, e.g. `[isort].extra_requirements`. Then, regenerate the lockfile(s) with the `generate-lockfiles` goal. Alternatively, use Pex for generation.\n\nFinally, installing from a Poetry-generated lockfile is slower than installing from a Pex lockfile. When using a Pex lockfile, Pants will only install the subset needed for the current task.\n\nHowever, Pex lockfile generation is a new feature. Given how vast the Python packaging ecosystem is, it is possible you may experience edge cases / bugs we haven't yet covered. Bug reports are appreciated! https://github.com/pantsbuild/pants/issues/new/choose\n\nNote that while Pex generates locks in a proprietary JSON format, you can use the `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export` goal for Pants to create a virtual environment for interoperability with tools like IDEs.", + "help": "Whether to use Pex or Poetry with the `generate-lockfiles` goal.\n\nPoetry does not support these features:\n\n 1) `[python-repos]` for custom indexes/cheeseshops.\n 2) VCS (Git) requirements.\n 3) `[GLOBAL].ca_certs_path`.\n\nIf you use any of these features, you should use Pex.\n\nSeveral users have also had issues with how Poetry's lockfile generation handles environment markers for transitive dependencies; certain dependencies end up with nonsensical environment markers which cause the dependency to not be installed, then for Pants/Pex to complain the dependency is missing, even though it's in the lockfile. There is a workaround: for `[python].resolves`, manually create a `python_requirement` target for the problematic transitive dependencies so that they are seen as direct requirements, rather than transitive. For tool lockfiles, add the problematic transitive dependency to `[tool].extra_requirements`, e.g. `[isort].extra_requirements`. Then, regenerate the lockfile(s) with the `generate-lockfiles` goal. Alternatively, use Pex for generation.\n\nFinally, installing from a Poetry-generated lockfile is slower than installing from a Pex lockfile. When using a Pex lockfile, Pants will only install the subset needed for the current task.\n\nHowever, Pex lockfile generation is a new feature. Given how vast the Python packaging ecosystem is, it is possible you may experience edge cases / bugs we haven't yet covered. Bug reports are appreciated! https://github.com/pantsbuild/pants/issues/new/choose\n\nNote that while Pex generates locks in a proprietary JSON format, you can use the `/home/josh/work/scie-pants/dist/pants export` goal for Pants to create a virtual environment for interoperability with tools like IDEs.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--python-lockfile-generator"], @@ -47125,7 +47125,7 @@ "deprecation_active": false, "display_args": ["--python-infer-init-files="], "env_var": "PANTS_PYTHON_INFER_INIT_FILES", - "help": "Infer a target's dependencies on any `__init__.py` files in the packages it is located in (recursively upward in the directory structure).\n\nEven if this is set to `never` or `content_only`, Pants will still always include any ancestor `__init__.py` files in the sandbox. Only, they will not be \"proper\" dependencies, e.g. they will not show up in `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` and their own dependencies will not be used.\n\nBy default, Pants only adds a \"proper\" dependency if there is content in the `__init__.py` file. This makes sure that dependencies are added when likely necessary to build, while also avoiding adding unnecessary dependencies. While accurate, those unnecessary dependencies can complicate setting metadata like the `interpreter_constraints` and `resolve` fields.", + "help": "Infer a target's dependencies on any `__init__.py` files in the packages it is located in (recursively upward in the directory structure).\n\nEven if this is set to `never` or `content_only`, Pants will still always include any ancestor `__init__.py` files in the sandbox. Only, they will not be \"proper\" dependencies, e.g. they will not show up in `/home/josh/work/scie-pants/dist/pants dependencies` and their own dependencies will not be used.\n\nBy default, Pants only adds a \"proper\" dependency if there is content in the `__init__.py` file. This makes sure that dependencies are added when likely necessary to build, while also avoiding adding unnecessary dependencies. While accurate, those unnecessary dependencies can complicate setting metadata like the `interpreter_constraints` and `resolve` fields.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--python-infer-init-files"], @@ -47261,7 +47261,7 @@ "deprecation_active": true, "display_args": ["--[no-]python-infer-inits"], "env_var": "PANTS_PYTHON_INFER_INITS", - "help": "Infer a target's dependencies on any `__init__.py` files in the packages it is located in (recursively upward in the directory structure).\n\nEven if this is disabled, Pants will still include any ancestor `__init__.py` files, only they will not be 'proper' dependencies, e.g. they will not show up in `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` and their own dependencies will not be used.\n\nIf you have empty `__init__.py` files, it's safe to leave this option off; otherwise, you should enable this option.", + "help": "Infer a target's dependencies on any `__init__.py` files in the packages it is located in (recursively upward in the directory structure).\n\nEven if this is disabled, Pants will still include any ancestor `__init__.py` files, only they will not be 'proper' dependencies, e.g. they will not show up in `/home/josh/work/scie-pants/dist/pants dependencies` and their own dependencies will not be used.\n\nIf you have empty `__init__.py` files, it's safe to leave this option off; otherwise, you should enable this option.", "removal_hint": "Use the more powerful option `[python-infer].init_files`. For identical behavior, set to 'always'. Otherwise, we recommend the default of `content_only` (simply delete the option `[python-infer].inits` to trigger the default).", "removal_version": "2.14.0.dev1", "scoped_cmd_line_args": [ @@ -47718,7 +47718,7 @@ "deprecation_active": false, "display_args": ["--pyupgrade-lockfile="], "env_var": "PANTS_PYUPGRADE_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/backend/python/lint/pyupgrade/pyupgrade.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=pyupgrade`.\n\nAs explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/backend/python/lint/pyupgrade/pyupgrade.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=pyupgrade`.\n\nAs explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pyupgrade-lockfile"], @@ -47808,7 +47808,7 @@ "deprecation_active": false, "display_args": ["--[no-]pyupgrade-skip"], "env_var": "PANTS_PYUPGRADE_SKIP", - "help": "Don't use pyupgrade when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use pyupgrade when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pyupgrade-skip", "--no-pyupgrade-skip"], @@ -47872,7 +47872,7 @@ "deprecation_active": false, "display_args": ["--[no-]pyupgrade-export"], "env_var": "PANTS_PYUPGRADE_EXPORT", - "help": "If true, export a virtual environment with pyupgrade when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with pyupgrade when running `/home/josh/work/scie-pants/dist/pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -48614,7 +48614,7 @@ "deprecation_active": false, "display_args": ["--scalafmt-lockfile="], "env_var": "PANTS_SCALAFMT_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/backend/scala/lint/scalafmt/scalafmt.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalafmt`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/backend/scala/lint/scalafmt/scalafmt.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=scalafmt`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalafmt-lockfile"], @@ -48680,7 +48680,7 @@ "deprecation_active": false, "display_args": ["--[no-]scalafmt-skip"], "env_var": "PANTS_SCALAFMT_SKIP", - "help": "Don't use scalafmt when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use scalafmt when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalafmt-skip", "--no-scalafmt-skip"], @@ -48783,7 +48783,7 @@ "deprecation_active": false, "display_args": ["--scalapb-lockfile="], "env_var": "PANTS_SCALAPB_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/backend/codegen/protobuf/scala/scalapbc.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalapb`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/backend/codegen/protobuf/scala/scalapbc.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=scalapb`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalapb-lockfile"], @@ -48950,7 +48950,7 @@ "deprecation_active": false, "display_args": ["--scalatest-lockfile="], "env_var": "PANTS_SCALATEST_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/backend/scala/subsystems/scalatest.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalatest`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/backend/scala/subsystems/scalatest.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=scalatest`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalatest-lockfile"], @@ -49432,7 +49432,7 @@ "deprecation_active": false, "display_args": ["--setuptools-lockfile="], "env_var": "PANTS_SETUPTOOLS_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/backend/python/subsystems/setuptools.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=setuptools`.\n\nAs explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/backend/python/subsystems/setuptools.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=setuptools`.\n\nAs explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--setuptools-lockfile"], @@ -49571,7 +49571,7 @@ "deprecation_active": false, "display_args": ["--setuptools-scm-lockfile="], "env_var": "PANTS_SETUPTOOLS_SCM_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/backend/python/subsystems/setuptools_scm.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=setuptools-scm`.\n\nAs explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/backend/python/subsystems/setuptools_scm.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=setuptools-scm`.\n\nAs explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--setuptools-scm-lockfile"], @@ -50005,7 +50005,7 @@ "deprecation_active": false, "display_args": ["--[no-]shellcheck-skip"], "env_var": "PANTS_SHELLCHECK_SKIP", - "help": "Don't use Shellcheck when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use Shellcheck when running `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--shellcheck-skip", "--no-shellcheck-skip"], @@ -50299,7 +50299,7 @@ "deprecation_active": false, "display_args": ["--[no-]shfmt-skip"], "env_var": "PANTS_SHFMT_SKIP", - "help": "Don't use shfmt when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use shfmt when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--shfmt-skip", "--no-shfmt-skip"], @@ -50829,7 +50829,7 @@ "deprecation_active": false, "display_args": ["--[no-]terraform-fmt-skip"], "env_var": "PANTS_TERRAFORM_FMT_SKIP", - "help": "Don't use `terraform fmt` when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use `terraform fmt` when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -50974,7 +50974,7 @@ "deprecation_active": false, "display_args": ["--terraform-hcl2-parser-lockfile="], "env_var": "PANTS_TERRAFORM_HCL2_PARSER_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/backend/terraform/hcl2.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=terraform-hcl2-parser`.\n\nAs explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/backend/terraform/hcl2.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=terraform-hcl2-parser`.\n\nAs explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--terraform-hcl2-parser-lockfile"], @@ -51017,7 +51017,7 @@ "deprecation_active": false, "display_args": ["--[no-]terraform-validate-skip"], "env_var": "PANTS_TERRAFORM_VALIDATE_SKIP", - "help": "Don't use `terraform validate` when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 check`.", + "help": "Don't use `terraform validate` when running `/home/josh/work/scie-pants/dist/pants check`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -51569,7 +51569,7 @@ "deprecation_active": false, "display_args": ["--twine-lockfile="], "env_var": "PANTS_TWINE_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/backend/python/subsystems/twine.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=twine`.\n\nAs explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/backend/python/subsystems/twine.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=twine`.\n\nAs explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--twine-lockfile"], @@ -51753,7 +51753,7 @@ "deprecation_active": false, "display_args": ["--[no-]twine-skip"], "env_var": "PANTS_TWINE_SKIP", - "help": "Don't use Twine when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 publish`.", + "help": "Don't use Twine when running `/home/josh/work/scie-pants/dist/pants publish`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--twine-skip", "--no-twine-skip"], @@ -52079,7 +52079,7 @@ "deprecation_active": false, "display_args": ["--yapf-lockfile="], "env_var": "PANTS_YAPF_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/backend/python/lint/yapf/yapf.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=yapf`.\n\nAs explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/backend/python/lint/yapf/yapf.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=yapf`.\n\nAs explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--yapf-lockfile"], @@ -52232,7 +52232,7 @@ "deprecation_active": false, "display_args": ["--[no-]yapf-skip"], "env_var": "PANTS_YAPF_SKIP", - "help": "Don't use yapf when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use yapf when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--yapf-skip", "--no-yapf-skip"], @@ -52294,7 +52294,7 @@ "deprecation_active": false, "display_args": ["--[no-]yapf-export"], "env_var": "PANTS_YAPF_EXPORT", - "help": "If true, export a virtual environment with yapf when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with yapf when running `/home/josh/work/scie-pants/dist/pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--yapf-export", "--no-yapf-export"], diff --git a/versioned_docs/version-2.13/reference/subsystems/autoflake.mdx b/versioned_docs/version-2.13/reference/subsystems/autoflake.mdx index 8e0e78f85..e6910fbcf 100644 --- a/versioned_docs/version-2.13/reference/subsystems/autoflake.mdx +++ b/versioned_docs/version-2.13/reference/subsystems/autoflake.mdx @@ -25,7 +25,7 @@ Config section: `[autoflake]` default_repr={`False`} > -Don't use Autoflake when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use Autoflake when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. @@ -49,7 +49,7 @@ Arguments to pass directly to Autoflake, e.g. `--autoflake-args='--remove-all-un default_repr={`True`} > -If true, export a virtual environment with Autoflake when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`. +If true, export a virtual environment with Autoflake when running `/home/josh/work/scie-pants/dist/pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. @@ -107,7 +107,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=autoflake`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=autoflake`. As explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.13/reference/subsystems/bandit.mdx b/versioned_docs/version-2.13/reference/subsystems/bandit.mdx index 6d9f90c4d..aaec3cc50 100644 --- a/versioned_docs/version-2.13/reference/subsystems/bandit.mdx +++ b/versioned_docs/version-2.13/reference/subsystems/bandit.mdx @@ -25,7 +25,7 @@ Config section: `[bandit]` default_repr={`False`} > -Don't use Bandit when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use Bandit when running `/home/josh/work/scie-pants/dist/pants lint`. @@ -49,7 +49,7 @@ Arguments to pass directly to Bandit, e.g. `--bandit-args='--skip B101,B308 --co default_repr={`True`} > -If true, export a virtual environment with Bandit when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`. +If true, export a virtual environment with Bandit when running `/home/josh/work/scie-pants/dist/pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. @@ -95,7 +95,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=bandit`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=bandit`. As explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.13/reference/subsystems/black.mdx b/versioned_docs/version-2.13/reference/subsystems/black.mdx index d4d9c241c..e68351a64 100644 --- a/versioned_docs/version-2.13/reference/subsystems/black.mdx +++ b/versioned_docs/version-2.13/reference/subsystems/black.mdx @@ -25,7 +25,7 @@ Config section: `[black]` default_repr={`False`} > -Don't use Black when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use Black when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. @@ -49,7 +49,7 @@ Arguments to pass directly to Black, e.g. `--black-args='--target-version=py37 - default_repr={`True`} > -If true, export a virtual environment with Black when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`. +If true, export a virtual environment with Black when running `/home/josh/work/scie-pants/dist/pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. @@ -107,7 +107,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=black`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=black`. As explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.13/reference/subsystems/buf.mdx b/versioned_docs/version-2.13/reference/subsystems/buf.mdx index 437ec1660..2ebd9b399 100644 --- a/versioned_docs/version-2.13/reference/subsystems/buf.mdx +++ b/versioned_docs/version-2.13/reference/subsystems/buf.mdx @@ -25,7 +25,7 @@ Config section: `[buf]` default_repr={`False`} > -Don't use Buf when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use Buf when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. @@ -37,7 +37,7 @@ Don't use Buf when running `/home/josh/work/scie-pants/dist/scie-pants-linu default_repr={`False`} > -Don't use Buf when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use Buf when running `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.13/reference/subsystems/cli.mdx b/versioned_docs/version-2.13/reference/subsystems/cli.mdx index 3612faf24..8c2253b82 100644 --- a/versioned_docs/version-2.13/reference/subsystems/cli.mdx +++ b/versioned_docs/version-2.13/reference/subsystems/cli.mdx @@ -35,7 +35,7 @@ green = "fmt lint check" all-changed = "--changed-since=HEAD --changed-dependees=transitive" ``` -This would allow you to run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 green all-changed`, which is shorthand for `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt lint check --changed-since=HEAD --changed-dependees=transitive`. +This would allow you to run `/home/josh/work/scie-pants/dist/pants green all-changed`, which is shorthand for `/home/josh/work/scie-pants/dist/pants fmt lint check --changed-since=HEAD --changed-dependees=transitive`. Notice: this option must be placed in a config file (e.g. `pants.toml` or `pantsrc`) to have any effect. diff --git a/versioned_docs/version-2.13/reference/subsystems/coverage-py.mdx b/versioned_docs/version-2.13/reference/subsystems/coverage-py.mdx index e21042474..782fa04db 100644 --- a/versioned_docs/version-2.13/reference/subsystems/coverage-py.mdx +++ b/versioned_docs/version-2.13/reference/subsystems/coverage-py.mdx @@ -130,7 +130,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=coverage-py`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=coverage-py`. As explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.13/reference/subsystems/debugpy.mdx b/versioned_docs/version-2.13/reference/subsystems/debugpy.mdx index 2a4d32f01..069ceaa1f 100644 --- a/versioned_docs/version-2.13/reference/subsystems/debugpy.mdx +++ b/versioned_docs/version-2.13/reference/subsystems/debugpy.mdx @@ -81,7 +81,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=debugpy`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=debugpy`. As explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.13/reference/subsystems/docformatter.mdx b/versioned_docs/version-2.13/reference/subsystems/docformatter.mdx index 0ee734817..2af4e084a 100644 --- a/versioned_docs/version-2.13/reference/subsystems/docformatter.mdx +++ b/versioned_docs/version-2.13/reference/subsystems/docformatter.mdx @@ -25,7 +25,7 @@ Config section: `[docformatter]` default_repr={`False`} > -Don't use docformatter when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use docformatter when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. @@ -49,7 +49,7 @@ Arguments to pass directly to docformatter, e.g. `--docformatter-args='--wrap-su default_repr={`True`} > -If true, export a virtual environment with docformatter when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`. +If true, export a virtual environment with docformatter when running `/home/josh/work/scie-pants/dist/pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. @@ -107,7 +107,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=docformatter`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=docformatter`. As explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.13/reference/subsystems/docker.mdx b/versioned_docs/version-2.13/reference/subsystems/docker.mdx index 689815dc2..52b9434ff 100644 --- a/versioned_docs/version-2.13/reference/subsystems/docker.mdx +++ b/versioned_docs/version-2.13/reference/subsystems/docker.mdx @@ -166,7 +166,7 @@ Additional arguments to use for `docker run` invocations. Example: ``` -$ /home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 run --docker-run-args="-p 127.0.0.1:80:8080/tcp --name demo" src/example:image -- [image entrypoint args] +$ /home/josh/work/scie-pants/dist/pants run --docker-run-args="-p 127.0.0.1:80:8080/tcp --name demo" src/example:image -- [image entrypoint args] ``` To provide the top-level options to the `docker` client, use `[docker].env_vars` to configure the [Environment variables](https://docs.docker.com/engine/reference/commandline/cli/#environment-variables) as appropriate. diff --git a/versioned_docs/version-2.13/reference/subsystems/dockerfile-parser.mdx b/versioned_docs/version-2.13/reference/subsystems/dockerfile-parser.mdx index 93ca26ede..8a899831e 100644 --- a/versioned_docs/version-2.13/reference/subsystems/dockerfile-parser.mdx +++ b/versioned_docs/version-2.13/reference/subsystems/dockerfile-parser.mdx @@ -71,7 +71,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=dockerfile-parser`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=dockerfile-parser`. As explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.13/reference/subsystems/flake8.mdx b/versioned_docs/version-2.13/reference/subsystems/flake8.mdx index 1b675fd02..c37532eab 100644 --- a/versioned_docs/version-2.13/reference/subsystems/flake8.mdx +++ b/versioned_docs/version-2.13/reference/subsystems/flake8.mdx @@ -25,7 +25,7 @@ Config section: `[flake8]` default_repr={`False`} > -Don't use Flake8 when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use Flake8 when running `/home/josh/work/scie-pants/dist/pants lint`. @@ -49,7 +49,7 @@ Arguments to pass directly to Flake8, e.g. `--flake8-args='--ignore E123,W456 -- default_repr={`True`} > -If true, export a virtual environment with Flake8 when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`. +If true, export a virtual environment with Flake8 when running `/home/josh/work/scie-pants/dist/pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. @@ -95,7 +95,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=flake8`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=flake8`. As explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.13/reference/subsystems/gofmt.mdx b/versioned_docs/version-2.13/reference/subsystems/gofmt.mdx index 01c96bcf2..a4ae242b4 100644 --- a/versioned_docs/version-2.13/reference/subsystems/gofmt.mdx +++ b/versioned_docs/version-2.13/reference/subsystems/gofmt.mdx @@ -25,7 +25,7 @@ Config section: `[gofmt]` default_repr={`False`} > -Don't use gofmt when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use gofmt when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.13/reference/subsystems/google-java-format.mdx b/versioned_docs/version-2.13/reference/subsystems/google-java-format.mdx index 4993dbfa3..02db6bcec 100644 --- a/versioned_docs/version-2.13/reference/subsystems/google-java-format.mdx +++ b/versioned_docs/version-2.13/reference/subsystems/google-java-format.mdx @@ -25,7 +25,7 @@ Config section: `[google-java-format]` default_repr={`False`} > -Don't use Google Java Format when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use Google Java Format when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. @@ -79,7 +79,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/backend/java/lint/google_java_format/google_java_format.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=google-java-format`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=google-java-format`. diff --git a/versioned_docs/version-2.13/reference/subsystems/hadolint.mdx b/versioned_docs/version-2.13/reference/subsystems/hadolint.mdx index 960ff1ca3..2d71026b6 100644 --- a/versioned_docs/version-2.13/reference/subsystems/hadolint.mdx +++ b/versioned_docs/version-2.13/reference/subsystems/hadolint.mdx @@ -25,7 +25,7 @@ Config section: `[hadolint]` default_repr={`False`} > -Don't use Hadolint when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use Hadolint when running `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.13/reference/subsystems/ipython.mdx b/versioned_docs/version-2.13/reference/subsystems/ipython.mdx index 5912d30e5..43ee17b3d 100644 --- a/versioned_docs/version-2.13/reference/subsystems/ipython.mdx +++ b/versioned_docs/version-2.13/reference/subsystems/ipython.mdx @@ -59,7 +59,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=ipython`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=ipython`. As explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.13/reference/subsystems/isort.mdx b/versioned_docs/version-2.13/reference/subsystems/isort.mdx index ff4b937e9..c5af1c1f5 100644 --- a/versioned_docs/version-2.13/reference/subsystems/isort.mdx +++ b/versioned_docs/version-2.13/reference/subsystems/isort.mdx @@ -25,7 +25,7 @@ Config section: `[isort]` default_repr={`False`} > -Don't use isort when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use isort when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. @@ -49,7 +49,7 @@ Arguments to pass directly to isort, e.g. `--isort-args='--case-sensitive --trai default_repr={`True`} > -If true, export a virtual environment with isort when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`. +If true, export a virtual environment with isort when running `/home/josh/work/scie-pants/dist/pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. @@ -107,7 +107,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=isort`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=isort`. As explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.13/reference/subsystems/junit.mdx b/versioned_docs/version-2.13/reference/subsystems/junit.mdx index 46dd0e8b3..77cb09c4e 100644 --- a/versioned_docs/version-2.13/reference/subsystems/junit.mdx +++ b/versioned_docs/version-2.13/reference/subsystems/junit.mdx @@ -67,7 +67,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/jvm/test/junit.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=junit`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=junit`. diff --git a/versioned_docs/version-2.13/reference/subsystems/ktlint.mdx b/versioned_docs/version-2.13/reference/subsystems/ktlint.mdx index 34bd2d8ab..a02e1b836 100644 --- a/versioned_docs/version-2.13/reference/subsystems/ktlint.mdx +++ b/versioned_docs/version-2.13/reference/subsystems/ktlint.mdx @@ -25,7 +25,7 @@ Config section: `[ktlint]` default_repr={`False`} > -Don't use Ktlint when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use Ktlint when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. @@ -67,7 +67,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/backend/kotlin/lint/ktlint/ktlint.lock for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=ktlint`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=ktlint`. diff --git a/versioned_docs/version-2.13/reference/subsystems/lambdex.mdx b/versioned_docs/version-2.13/reference/subsystems/lambdex.mdx index 68d5ac935..0fd187b77 100644 --- a/versioned_docs/version-2.13/reference/subsystems/lambdex.mdx +++ b/versioned_docs/version-2.13/reference/subsystems/lambdex.mdx @@ -71,7 +71,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=lambdex`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=lambdex`. As explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.13/reference/subsystems/mypy-protobuf.mdx b/versioned_docs/version-2.13/reference/subsystems/mypy-protobuf.mdx index ebdde0783..708af5cf9 100644 --- a/versioned_docs/version-2.13/reference/subsystems/mypy-protobuf.mdx +++ b/versioned_docs/version-2.13/reference/subsystems/mypy-protobuf.mdx @@ -71,7 +71,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=mypy-protobuf`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=mypy-protobuf`. As explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.13/reference/subsystems/mypy.mdx b/versioned_docs/version-2.13/reference/subsystems/mypy.mdx index c4d8e52a5..b7c7409d3 100644 --- a/versioned_docs/version-2.13/reference/subsystems/mypy.mdx +++ b/versioned_docs/version-2.13/reference/subsystems/mypy.mdx @@ -25,7 +25,7 @@ Config section: `[mypy]` default_repr={`False`} > -Don't use MyPy when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 check`. +Don't use MyPy when running `/home/josh/work/scie-pants/dist/pants check`. @@ -49,7 +49,7 @@ Arguments to pass directly to MyPy, e.g. `--mypy-args='--python-version 3.7 --di default_repr={`True`} > -If true, export a virtual environment with MyPy when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`. +If true, export a virtual environment with MyPy when running `/home/josh/work/scie-pants/dist/pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. @@ -107,7 +107,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=mypy`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=mypy`. As explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.13/reference/subsystems/pylint.mdx b/versioned_docs/version-2.13/reference/subsystems/pylint.mdx index bbf86b07c..1c4eb7823 100644 --- a/versioned_docs/version-2.13/reference/subsystems/pylint.mdx +++ b/versioned_docs/version-2.13/reference/subsystems/pylint.mdx @@ -25,7 +25,7 @@ Config section: `[pylint]` default_repr={`False`} > -Don't use Pylint when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use Pylint when running `/home/josh/work/scie-pants/dist/pants lint`. @@ -49,7 +49,7 @@ Arguments to pass directly to Pylint, e.g. `--pylint-args='--ignore=foo.py,bar.p default_repr={`True`} > -If true, export a virtual environment with Pylint when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`. +If true, export a virtual environment with Pylint when running `/home/josh/work/scie-pants/dist/pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. @@ -95,7 +95,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=pylint`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=pylint`. As explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.13/reference/subsystems/pytest.mdx b/versioned_docs/version-2.13/reference/subsystems/pytest.mdx index 12f86e186..fa6a6f6b3 100644 --- a/versioned_docs/version-2.13/reference/subsystems/pytest.mdx +++ b/versioned_docs/version-2.13/reference/subsystems/pytest.mdx @@ -49,7 +49,7 @@ Enable test target timeouts. If timeouts are enabled then test targets with a ti default_repr={`True`} > -If true, export a virtual environment with Pytest when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`. +If true, export a virtual environment with Pytest when running `/home/josh/work/scie-pants/dist/pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. @@ -95,7 +95,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=pytest`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=pytest`. As explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.13/reference/subsystems/python-infer.mdx b/versioned_docs/version-2.13/reference/subsystems/python-infer.mdx index 0ae054acb..f48a7b122 100644 --- a/versioned_docs/version-2.13/reference/subsystems/python-infer.mdx +++ b/versioned_docs/version-2.13/reference/subsystems/python-infer.mdx @@ -94,7 +94,7 @@ If --assets is True, treat valid-looking strings with at least this many forward Infer a target's dependencies on any `__init__.py` files in the packages it is located in (recursively upward in the directory structure). -Even if this is set to `never` or `content_only`, Pants will still always include any ancestor `__init__.py` files in the sandbox. Only, they will not be "proper" dependencies, e.g. they will not show up in `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` and their own dependencies will not be used. +Even if this is set to `never` or `content_only`, Pants will still always include any ancestor `__init__.py` files in the sandbox. Only, they will not be "proper" dependencies, e.g. they will not show up in `/home/josh/work/scie-pants/dist/pants dependencies` and their own dependencies will not be used. By default, Pants only adds a "proper" dependency if there is content in the `__init__.py` file. This makes sure that dependencies are added when likely necessary to build, while also avoiding adding unnecessary dependencies. While accurate, those unnecessary dependencies can complicate setting metadata like the `interpreter_constraints` and `resolve` fields. @@ -159,7 +159,7 @@ None Infer a target's dependencies on any `__init__.py` files in the packages it is located in (recursively upward in the directory structure). -Even if this is disabled, Pants will still include any ancestor `__init__.py` files, only they will not be 'proper' dependencies, e.g. they will not show up in `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` and their own dependencies will not be used. +Even if this is disabled, Pants will still include any ancestor `__init__.py` files, only they will not be 'proper' dependencies, e.g. they will not show up in `/home/josh/work/scie-pants/dist/pants dependencies` and their own dependencies will not be used. If you have empty `__init__.py` files, it's safe to leave this option off; otherwise, you should enable this option. diff --git a/versioned_docs/version-2.13/reference/subsystems/python.mdx b/versioned_docs/version-2.13/reference/subsystems/python.mdx index 3fe3ac8f4..25d0d3910 100644 --- a/versioned_docs/version-2.13/reference/subsystems/python.mdx +++ b/versioned_docs/version-2.13/reference/subsystems/python.mdx @@ -135,14 +135,14 @@ A mapping of logical names to lockfile paths used in your project. Many organizations only need a single resolve for their whole project, which is a good default and often the simplest thing to do. However, you may need multiple resolves, such as if you use two conflicting versions of a requirement in your repository. -If you only need a single resolve, run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles` to generate the lockfile. +If you only need a single resolve, run `/home/josh/work/scie-pants/dist/pants generate-lockfiles` to generate the lockfile. If you need multiple resolves: 1. Via this option, define multiple resolve names and their lockfile paths. The names should be meaningful to your repository, such as `data-science` or `pants-plugins`. 2. Set the default with `[python].default_resolve`. 3. Update your `python_requirement` targets with the `resolve` field to declare which resolve they should be available in. They default to `[python].default_resolve`, so you only need to update targets that you want in non-default resolves. (Often you'll set this via the `python_requirements` or `poetry_requirements` target generators) -4. Run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles` to generate the lockfiles. If the results aren't what you'd expect, adjust the prior step. +4. Run `/home/josh/work/scie-pants/dist/pants generate-lockfiles` to generate the lockfiles. If the results aren't what you'd expect, adjust the prior step. 5. Update any targets like `python_source` / `python_sources`, `python_test` / `python_tests`, and `pex_binary` which need to set a non-default resolve with the `resolve` field. If a target can work with multiple resolves, you can either use the `parametrize` mechanism or manually create a distinct target per resolve. See https://www.pantsbuild.org/v2.13/docs/targets for information about `parametrize`. @@ -237,7 +237,7 @@ Finally, installing from a Poetry-generated lockfile is slower than installing f However, Pex lockfile generation is a new feature. Given how vast the Python packaging ecosystem is, it is possible you may experience edge cases / bugs we haven't yet covered. Bug reports are appreciated! https://github.com/pantsbuild/pants/issues/new/choose -Note that while Pex generates locks in a proprietary JSON format, you can use the `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export` goal for Pants to create a virtual environment for interoperability with tools like IDEs. +Note that while Pex generates locks in a proprietary JSON format, you can use the `/home/josh/work/scie-pants/dist/pants export` goal for Pants to create a virtual environment for interoperability with tools like IDEs. diff --git a/versioned_docs/version-2.13/reference/subsystems/pyupgrade.mdx b/versioned_docs/version-2.13/reference/subsystems/pyupgrade.mdx index 5a4c15b84..ecef9de78 100644 --- a/versioned_docs/version-2.13/reference/subsystems/pyupgrade.mdx +++ b/versioned_docs/version-2.13/reference/subsystems/pyupgrade.mdx @@ -25,7 +25,7 @@ Config section: `[pyupgrade]` default_repr={`False`} > -Don't use pyupgrade when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use pyupgrade when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. @@ -49,7 +49,7 @@ Arguments to pass directly to pyupgrade, e.g. `--pyupgrade-args='--py39-plus --k default_repr={`True`} > -If true, export a virtual environment with pyupgrade when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`. +If true, export a virtual environment with pyupgrade when running `/home/josh/work/scie-pants/dist/pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. @@ -107,7 +107,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=pyupgrade`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=pyupgrade`. As explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.13/reference/subsystems/scalafmt.mdx b/versioned_docs/version-2.13/reference/subsystems/scalafmt.mdx index 33e5ad324..98625ac53 100644 --- a/versioned_docs/version-2.13/reference/subsystems/scalafmt.mdx +++ b/versioned_docs/version-2.13/reference/subsystems/scalafmt.mdx @@ -25,7 +25,7 @@ Config section: `[scalafmt]` default_repr={`False`} > -Don't use scalafmt when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use scalafmt when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. @@ -67,7 +67,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/backend/scala/lint/scalafmt/scalafmt.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalafmt`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=scalafmt`. diff --git a/versioned_docs/version-2.13/reference/subsystems/scalapb.mdx b/versioned_docs/version-2.13/reference/subsystems/scalapb.mdx index 569c66a60..6ce5e2af5 100644 --- a/versioned_docs/version-2.13/reference/subsystems/scalapb.mdx +++ b/versioned_docs/version-2.13/reference/subsystems/scalapb.mdx @@ -69,7 +69,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/backend/codegen/protobuf/scala/scalapbc.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalapb`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=scalapb`. diff --git a/versioned_docs/version-2.13/reference/subsystems/scalatest.mdx b/versioned_docs/version-2.13/reference/subsystems/scalatest.mdx index 8a06eac61..6ac9178e4 100644 --- a/versioned_docs/version-2.13/reference/subsystems/scalatest.mdx +++ b/versioned_docs/version-2.13/reference/subsystems/scalatest.mdx @@ -69,7 +69,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/backend/scala/subsystems/scalatest.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalatest`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=scalatest`. diff --git a/versioned_docs/version-2.13/reference/subsystems/setuptools-scm.mdx b/versioned_docs/version-2.13/reference/subsystems/setuptools-scm.mdx index d73bcfe7b..1992d54ba 100644 --- a/versioned_docs/version-2.13/reference/subsystems/setuptools-scm.mdx +++ b/versioned_docs/version-2.13/reference/subsystems/setuptools-scm.mdx @@ -71,7 +71,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=setuptools-scm`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=setuptools-scm`. As explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.13/reference/subsystems/setuptools.mdx b/versioned_docs/version-2.13/reference/subsystems/setuptools.mdx index fed7a2fdf..db66c2de1 100644 --- a/versioned_docs/version-2.13/reference/subsystems/setuptools.mdx +++ b/versioned_docs/version-2.13/reference/subsystems/setuptools.mdx @@ -59,7 +59,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=setuptools`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=setuptools`. As explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.13/reference/subsystems/shellcheck.mdx b/versioned_docs/version-2.13/reference/subsystems/shellcheck.mdx index e328a7073..6ca6f17ec 100644 --- a/versioned_docs/version-2.13/reference/subsystems/shellcheck.mdx +++ b/versioned_docs/version-2.13/reference/subsystems/shellcheck.mdx @@ -25,7 +25,7 @@ Config section: `[shellcheck]` default_repr={`False`} > -Don't use Shellcheck when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use Shellcheck when running `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.13/reference/subsystems/shfmt.mdx b/versioned_docs/version-2.13/reference/subsystems/shfmt.mdx index 4d8ce135b..76f884959 100644 --- a/versioned_docs/version-2.13/reference/subsystems/shfmt.mdx +++ b/versioned_docs/version-2.13/reference/subsystems/shfmt.mdx @@ -25,7 +25,7 @@ Config section: `[shfmt]` default_repr={`False`} > -Don't use shfmt when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use shfmt when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.13/reference/subsystems/terraform-fmt.mdx b/versioned_docs/version-2.13/reference/subsystems/terraform-fmt.mdx index 0ea670e77..92c3c6ec7 100644 --- a/versioned_docs/version-2.13/reference/subsystems/terraform-fmt.mdx +++ b/versioned_docs/version-2.13/reference/subsystems/terraform-fmt.mdx @@ -25,7 +25,7 @@ Config section: `[terraform-fmt]` default_repr={`False`} > -Don't use `terraform fmt` when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use `terraform fmt` when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.13/reference/subsystems/terraform-hcl2-parser.mdx b/versioned_docs/version-2.13/reference/subsystems/terraform-hcl2-parser.mdx index aaa3a5677..e9b50b717 100644 --- a/versioned_docs/version-2.13/reference/subsystems/terraform-hcl2-parser.mdx +++ b/versioned_docs/version-2.13/reference/subsystems/terraform-hcl2-parser.mdx @@ -71,7 +71,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=terraform-hcl2-parser`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=terraform-hcl2-parser`. As explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.13/reference/subsystems/terraform-validate.mdx b/versioned_docs/version-2.13/reference/subsystems/terraform-validate.mdx index 0756cde83..89fa2bb81 100644 --- a/versioned_docs/version-2.13/reference/subsystems/terraform-validate.mdx +++ b/versioned_docs/version-2.13/reference/subsystems/terraform-validate.mdx @@ -25,7 +25,7 @@ Config section: `[terraform-validate]` default_repr={`False`} > -Don't use `terraform validate` when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 check`. +Don't use `terraform validate` when running `/home/josh/work/scie-pants/dist/pants check`. diff --git a/versioned_docs/version-2.13/reference/subsystems/twine.mdx b/versioned_docs/version-2.13/reference/subsystems/twine.mdx index ddc613615..1cb62c5b0 100644 --- a/versioned_docs/version-2.13/reference/subsystems/twine.mdx +++ b/versioned_docs/version-2.13/reference/subsystems/twine.mdx @@ -25,7 +25,7 @@ Config section: `[twine]` default_repr={`False`} > -Don't use Twine when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 publish`. +Don't use Twine when running `/home/josh/work/scie-pants/dist/pants publish`. @@ -93,7 +93,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=twine`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=twine`. As explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.13/reference/subsystems/yapf.mdx b/versioned_docs/version-2.13/reference/subsystems/yapf.mdx index 82fac82b9..7a731b94f 100644 --- a/versioned_docs/version-2.13/reference/subsystems/yapf.mdx +++ b/versioned_docs/version-2.13/reference/subsystems/yapf.mdx @@ -25,7 +25,7 @@ Config section: `[yapf]` default_repr={`False`} > -Don't use yapf when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use yapf when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. @@ -51,7 +51,7 @@ Certain arguments, specifically `--recursive`, `--in-place`, and `--parallel`, w default_repr={`True`} > -If true, export a virtual environment with yapf when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`. +If true, export a virtual environment with yapf when running `/home/josh/work/scie-pants/dist/pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. @@ -109,7 +109,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=yapf`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=yapf`. As explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via `generate-lockfiles` does not always work and you may want to manually generate the lockfile. You will want to set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.13/reference/targets/archive.mdx b/versioned_docs/version-2.13/reference/targets/archive.mdx index eee2b5712..801685458 100644 --- a/versioned_docs/version-2.13/reference/targets/archive.mdx +++ b/versioned_docs/version-2.13/reference/targets/archive.mdx @@ -24,7 +24,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -52,7 +52,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. @@ -65,11 +65,11 @@ Warning: setting this value risks naming collisions with other package targets y default_repr={`None`} > -Addresses to any targets that can be built with `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, e.g. `["project:app"]`. +Addresses to any targets that can be built with `/home/josh/work/scie-pants/dist/pants package`, e.g. `["project:app"]`. -Pants will build the assets as if you had run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`. It will include the results in your archive using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). +Pants will build the assets as if you had run `/home/josh/work/scie-pants/dist/pants package`. It will include the results in your archive using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). -You can include anything that can be built by `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or even another `archive`. +You can include anything that can be built by `/home/josh/work/scie-pants/dist/pants package`, e.g. a `pex_binary`, `python_awslambda`, or even another `archive`. diff --git a/versioned_docs/version-2.13/reference/targets/deploy_jar.mdx b/versioned_docs/version-2.13/reference/targets/deploy_jar.mdx index 3bc56356a..eb76ab9fd 100644 --- a/versioned_docs/version-2.13/reference/targets/deploy_jar.mdx +++ b/versioned_docs/version-2.13/reference/targets/deploy_jar.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.experimental.java` @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -52,9 +52,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -73,7 +73,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. diff --git a/versioned_docs/version-2.13/reference/targets/docker_image.mdx b/versioned_docs/version-2.13/reference/targets/docker_image.mdx index ebf379898..4e5720af9 100644 --- a/versioned_docs/version-2.13/reference/targets/docker_image.mdx +++ b/versioned_docs/version-2.13/reference/targets/docker_image.mdx @@ -39,7 +39,7 @@ Backend: `pants.backend.docker` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -52,7 +52,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -78,9 +78,9 @@ Use `[docker].build_args` to set default build args for all images. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -277,7 +277,7 @@ See [Docker documentation](https://docs.docker.com/develop/develop-images/build_ default_repr={`False`} > -If set to true, do not push this image to registries when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 publish`. +If set to true, do not push this image to registries when running `/home/josh/work/scie-pants/dist/pants publish`. diff --git a/versioned_docs/version-2.13/reference/targets/experimental_run_shell_command.mdx b/versioned_docs/version-2.13/reference/targets/experimental_run_shell_command.mdx index a004db519..3e572a380 100644 --- a/versioned_docs/version-2.13/reference/targets/experimental_run_shell_command.mdx +++ b/versioned_docs/version-2.13/reference/targets/experimental_run_shell_command.mdx @@ -37,7 +37,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -50,7 +50,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -63,9 +63,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.13/reference/targets/experimental_shell_command.mdx b/versioned_docs/version-2.13/reference/targets/experimental_shell_command.mdx index f8d1abc52..84765a90a 100644 --- a/versioned_docs/version-2.13/reference/targets/experimental_shell_command.mdx +++ b/versioned_docs/version-2.13/reference/targets/experimental_shell_command.mdx @@ -41,7 +41,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -54,7 +54,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -67,9 +67,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.13/reference/targets/file.mdx b/versioned_docs/version-2.13/reference/targets/file.mdx index bed55a15f..63b74bf52 100644 --- a/versioned_docs/version-2.13/reference/targets/file.mdx +++ b/versioned_docs/version-2.13/reference/targets/file.mdx @@ -26,7 +26,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -52,9 +52,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.13/reference/targets/files.mdx b/versioned_docs/version-2.13/reference/targets/files.mdx index 5ae3f9e00..aba528dd8 100644 --- a/versioned_docs/version-2.13/reference/targets/files.mdx +++ b/versioned_docs/version-2.13/reference/targets/files.mdx @@ -24,7 +24,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -91,9 +91,9 @@ You can specify the same file name in multiple keys, so long as you don't o Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.13/reference/targets/go_binary.mdx b/versioned_docs/version-2.13/reference/targets/go_binary.mdx index 3f172d7d0..26351b1ff 100644 --- a/versioned_docs/version-2.13/reference/targets/go_binary.mdx +++ b/versioned_docs/version-2.13/reference/targets/go_binary.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.go` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -52,7 +52,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. diff --git a/versioned_docs/version-2.13/reference/targets/go_mod.mdx b/versioned_docs/version-2.13/reference/targets/go_mod.mdx index 605db3545..caeac0e75 100644 --- a/versioned_docs/version-2.13/reference/targets/go_mod.mdx +++ b/versioned_docs/version-2.13/reference/targets/go_mod.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.go` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.13/reference/targets/go_package.mdx b/versioned_docs/version-2.13/reference/targets/go_package.mdx index 3807f780d..2b4539611 100644 --- a/versioned_docs/version-2.13/reference/targets/go_package.mdx +++ b/versioned_docs/version-2.13/reference/targets/go_package.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.experimental.go` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -52,9 +52,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.13/reference/targets/go_third_party_package.mdx b/versioned_docs/version-2.13/reference/targets/go_third_party_package.mdx index 8979cb205..96afb6488 100644 --- a/versioned_docs/version-2.13/reference/targets/go_third_party_package.mdx +++ b/versioned_docs/version-2.13/reference/targets/go_third_party_package.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.go` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -54,9 +54,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.13/reference/targets/helm_artifact.mdx b/versioned_docs/version-2.13/reference/targets/helm_artifact.mdx index 62850ffdf..33546af67 100644 --- a/versioned_docs/version-2.13/reference/targets/helm_artifact.mdx +++ b/versioned_docs/version-2.13/reference/targets/helm_artifact.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.helm` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.13/reference/targets/helm_chart.mdx b/versioned_docs/version-2.13/reference/targets/helm_chart.mdx index fdc2ca4d5..11fc4d080 100644 --- a/versioned_docs/version-2.13/reference/targets/helm_chart.mdx +++ b/versioned_docs/version-2.13/reference/targets/helm_chart.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.helm` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -76,9 +76,9 @@ Example: `sources=['values.yaml', 'templates/*.yaml', '!values_ignore.yaml']` Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -99,7 +99,7 @@ If undefined, this will use the path to the BUILD file, For example, `src/charts Regardless of whether you use the default or set this field, the path will end with Helms's file format of `-.tgz`, where `chart_name` and `chart_version` are the values extracted from the Chart.yaml file. So, using the default for this field, the target `src/charts/mychart:tgt_name` might have a final path like `src.charts.mychart/tgt_name/mychart-0.1.0.tgz`. -When running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. @@ -170,7 +170,7 @@ The above example shows two valid `registry` options: using an alias to a config default_repr={`False`} > -If set to true, do not push this Helm chart to registries when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 publish`. +If set to true, do not push this Helm chart to registries when running `/home/josh/work/scie-pants/dist/pants publish`. @@ -181,7 +181,7 @@ If set to true, do not push this Helm chart to registries when running `/home/jo default_repr={`False`} > -If set to true, do not run any linting in this Helm chart when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +If set to true, do not run any linting in this Helm chart when running `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.13/reference/targets/helm_unittest_test.mdx b/versioned_docs/version-2.13/reference/targets/helm_unittest_test.mdx index 0d646bff9..03e800bd9 100644 --- a/versioned_docs/version-2.13/reference/targets/helm_unittest_test.mdx +++ b/versioned_docs/version-2.13/reference/targets/helm_unittest_test.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.helm` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -63,9 +63,9 @@ Path is relative to the BUILD file's directory, e.g. `source='example.ext'` Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.13/reference/targets/helm_unittest_tests.mdx b/versioned_docs/version-2.13/reference/targets/helm_unittest_tests.mdx index 81d094c37..f045df82b 100644 --- a/versioned_docs/version-2.13/reference/targets/helm_unittest_tests.mdx +++ b/versioned_docs/version-2.13/reference/targets/helm_unittest_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.helm` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -65,9 +65,9 @@ Example: `sources=['*_test.yaml', '!ignore_test.yaml']` Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -84,9 +84,9 @@ You may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:l Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.13/reference/targets/java_source.mdx b/versioned_docs/version-2.13/reference/targets/java_source.mdx index 984f4a9a8..b6b64af14 100644 --- a/versioned_docs/version-2.13/reference/targets/java_source.mdx +++ b/versioned_docs/version-2.13/reference/targets/java_source.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.java` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.13/reference/targets/java_sources.mdx b/versioned_docs/version-2.13/reference/targets/java_sources.mdx index ebf5d7012..bf8b41677 100644 --- a/versioned_docs/version-2.13/reference/targets/java_sources.mdx +++ b/versioned_docs/version-2.13/reference/targets/java_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.java` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -77,9 +77,9 @@ If true, don't run Google Java Format on this target's code. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.13/reference/targets/junit_test.mdx b/versioned_docs/version-2.13/reference/targets/junit_test.mdx index 8ea8ae884..cbce10820 100644 --- a/versioned_docs/version-2.13/reference/targets/junit_test.mdx +++ b/versioned_docs/version-2.13/reference/targets/junit_test.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.java` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -63,9 +63,9 @@ Path is relative to the BUILD file's directory, e.g. `source='example.ext'` Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.13/reference/targets/junit_tests.mdx b/versioned_docs/version-2.13/reference/targets/junit_tests.mdx index 585c5d2f4..c65ed87f0 100644 --- a/versioned_docs/version-2.13/reference/targets/junit_tests.mdx +++ b/versioned_docs/version-2.13/reference/targets/junit_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.java` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -65,9 +65,9 @@ Example: `sources=['*Test.java', '!TestIgnore.java']` Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.13/reference/targets/jvm_artifact.mdx b/versioned_docs/version-2.13/reference/targets/jvm_artifact.mdx index 52f5730ba..18b53450b 100644 --- a/versioned_docs/version-2.13/reference/targets/jvm_artifact.mdx +++ b/versioned_docs/version-2.13/reference/targets/jvm_artifact.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.java` @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.13/reference/targets/jvm_war.mdx b/versioned_docs/version-2.13/reference/targets/jvm_war.mdx index 8c1095606..8e5278c97 100644 --- a/versioned_docs/version-2.13/reference/targets/jvm_war.mdx +++ b/versioned_docs/version-2.13/reference/targets/jvm_war.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.java` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -74,9 +74,9 @@ A list of addresses to `resources` and `files` targets with content to place in Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -106,7 +106,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. diff --git a/versioned_docs/version-2.13/reference/targets/kotlin_junit_test.mdx b/versioned_docs/version-2.13/reference/targets/kotlin_junit_test.mdx index fe3603072..e3f4b64b6 100644 --- a/versioned_docs/version-2.13/reference/targets/kotlin_junit_test.mdx +++ b/versioned_docs/version-2.13/reference/targets/kotlin_junit_test.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.kotlin` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.13/reference/targets/kotlin_junit_tests.mdx b/versioned_docs/version-2.13/reference/targets/kotlin_junit_tests.mdx index a54899931..0e0789a0a 100644 --- a/versioned_docs/version-2.13/reference/targets/kotlin_junit_tests.mdx +++ b/versioned_docs/version-2.13/reference/targets/kotlin_junit_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.kotlin` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -65,9 +65,9 @@ Example: `sources=['*Test.kt', '!TestIgnore.kt']` Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.13/reference/targets/kotlin_source.mdx b/versioned_docs/version-2.13/reference/targets/kotlin_source.mdx index 04909d755..0481bc87e 100644 --- a/versioned_docs/version-2.13/reference/targets/kotlin_source.mdx +++ b/versioned_docs/version-2.13/reference/targets/kotlin_source.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.kotlin` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.13/reference/targets/kotlin_sources.mdx b/versioned_docs/version-2.13/reference/targets/kotlin_sources.mdx index 313b4042e..b49896868 100644 --- a/versioned_docs/version-2.13/reference/targets/kotlin_sources.mdx +++ b/versioned_docs/version-2.13/reference/targets/kotlin_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.kotlin` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -77,9 +77,9 @@ If true, don't run Ktlint on this target's code. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.13/reference/targets/kotlinc_plugin.mdx b/versioned_docs/version-2.13/reference/targets/kotlinc_plugin.mdx index 936aa994f..5facbbddf 100644 --- a/versioned_docs/version-2.13/reference/targets/kotlinc_plugin.mdx +++ b/versioned_docs/version-2.13/reference/targets/kotlinc_plugin.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.kotlin` @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.13/reference/targets/pants_requirements.mdx b/versioned_docs/version-2.13/reference/targets/pants_requirements.mdx index 8c15ef1b1..b8f9710c3 100644 --- a/versioned_docs/version-2.13/reference/targets/pants_requirements.mdx +++ b/versioned_docs/version-2.13/reference/targets/pants_requirements.mdx @@ -30,7 +30,7 @@ Backend: `pants.backend.plugin_development` @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.13/reference/targets/pex_binaries.mdx b/versioned_docs/version-2.13/reference/targets/pex_binaries.mdx index 3391977b9..551ca3be4 100644 --- a/versioned_docs/version-2.13/reference/targets/pex_binaries.mdx +++ b/versioned_docs/version-2.13/reference/targets/pex_binaries.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -132,9 +132,9 @@ All dependencies must share the same value for their `resolve` field. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.13/reference/targets/pex_binary.mdx b/versioned_docs/version-2.13/reference/targets/pex_binary.mdx index 35bea3f72..9a54cc757 100644 --- a/versioned_docs/version-2.13/reference/targets/pex_binary.mdx +++ b/versioned_docs/version-2.13/reference/targets/pex_binary.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -86,9 +86,9 @@ All dependencies must share the same value for their `resolve` field. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -337,7 +337,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. diff --git a/versioned_docs/version-2.13/reference/targets/pipenv_requirements.mdx b/versioned_docs/version-2.13/reference/targets/pipenv_requirements.mdx index e87501d1a..1a319f31a 100644 --- a/versioned_docs/version-2.13/reference/targets/pipenv_requirements.mdx +++ b/versioned_docs/version-2.13/reference/targets/pipenv_requirements.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.13/reference/targets/poetry_requirements.mdx b/versioned_docs/version-2.13/reference/targets/poetry_requirements.mdx index 4d8346512..344c86b2f 100644 --- a/versioned_docs/version-2.13/reference/targets/poetry_requirements.mdx +++ b/versioned_docs/version-2.13/reference/targets/poetry_requirements.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.13/reference/targets/protobuf_source.mdx b/versioned_docs/version-2.13/reference/targets/protobuf_source.mdx index 8e9619efc..25dc8b8e1 100644 --- a/versioned_docs/version-2.13/reference/targets/protobuf_source.mdx +++ b/versioned_docs/version-2.13/reference/targets/protobuf_source.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.codegen.protobuf.python Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -54,9 +54,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.13/reference/targets/protobuf_sources.mdx b/versioned_docs/version-2.13/reference/targets/protobuf_sources.mdx index 52261ce4c..3645c8e72 100644 --- a/versioned_docs/version-2.13/reference/targets/protobuf_sources.mdx +++ b/versioned_docs/version-2.13/reference/targets/protobuf_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.codegen.protobuf.python Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -202,9 +202,9 @@ Whether to generate gRPC code or not. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.13/reference/targets/pyoxidizer_binary.mdx b/versioned_docs/version-2.13/reference/targets/pyoxidizer_binary.mdx index 61c0499d2..e98655bed 100644 --- a/versioned_docs/version-2.13/reference/targets/pyoxidizer_binary.mdx +++ b/versioned_docs/version-2.13/reference/targets/pyoxidizer_binary.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.python.pac Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -58,7 +58,7 @@ If undefined, this will use the path to the BUILD file, followed by the target n Regardless of whether you use the default or set this field, the path will end with PyOxidizer's file format of `/{debug,release}/install/`, where `platform` is a Rust platform triplet like `aarch-64-apple-darwin` and `binary_name` is the `name` of the `pyoxidizer_target`. So, using the default for this field, the target `src/python/project:bin` might have a final path like `src.python.project/bin/aarch-64-apple-darwin/release/bin`. -When running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. diff --git a/versioned_docs/version-2.13/reference/targets/python_awslambda.mdx b/versioned_docs/version-2.13/reference/targets/python_awslambda.mdx index a93af6797..51fd8a1ff 100644 --- a/versioned_docs/version-2.13/reference/targets/python_awslambda.mdx +++ b/versioned_docs/version-2.13/reference/targets/python_awslambda.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.awslambda.python` @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -54,7 +54,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. @@ -69,9 +69,9 @@ Warning: setting this value risks naming collisions with other package targets y Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.13/reference/targets/python_distribution.mdx b/versioned_docs/version-2.13/reference/targets/python_distribution.mdx index 3832e10ae..ac154a90a 100644 --- a/versioned_docs/version-2.13/reference/targets/python_distribution.mdx +++ b/versioned_docs/version-2.13/reference/targets/python_distribution.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -71,9 +71,9 @@ See https://www.pantsbuild.org/v2.13/docs/python-interpreter-compatibility for h Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -108,7 +108,7 @@ Note that Pants will assume that any value that either starts with `:` or has `/ Pants will attempt to infer dependencies, which you can confirm by running: ``` -/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies +/home/josh/work/scie-pants/dist/pants dependencies ``` diff --git a/versioned_docs/version-2.13/reference/targets/python_google_cloud_function.mdx b/versioned_docs/version-2.13/reference/targets/python_google_cloud_function.mdx index 40bfa0ed4..413e364e6 100644 --- a/versioned_docs/version-2.13/reference/targets/python_google_cloud_function.mdx +++ b/versioned_docs/version-2.13/reference/targets/python_google_cloud_function.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.google_cloud_function.p Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -54,7 +54,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. @@ -69,9 +69,9 @@ Warning: setting this value risks naming collisions with other package targets y Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.13/reference/targets/python_requirement.mdx b/versioned_docs/version-2.13/reference/targets/python_requirement.mdx index cf83e1766..7fd66659c 100644 --- a/versioned_docs/version-2.13/reference/targets/python_requirement.mdx +++ b/versioned_docs/version-2.13/reference/targets/python_requirement.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -54,9 +54,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.13/reference/targets/python_requirements.mdx b/versioned_docs/version-2.13/reference/targets/python_requirements.mdx index 2691c18c2..6fba0b9aa 100644 --- a/versioned_docs/version-2.13/reference/targets/python_requirements.mdx +++ b/versioned_docs/version-2.13/reference/targets/python_requirements.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.13/reference/targets/python_source.mdx b/versioned_docs/version-2.13/reference/targets/python_source.mdx index d0d909794..cb1361e63 100644 --- a/versioned_docs/version-2.13/reference/targets/python_source.mdx +++ b/versioned_docs/version-2.13/reference/targets/python_source.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -69,9 +69,9 @@ See https://www.pantsbuild.org/v2.13/docs/python-interpreter-compatibility for h Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.13/reference/targets/python_sources.mdx b/versioned_docs/version-2.13/reference/targets/python_sources.mdx index cd4829e01..62d48a5b7 100644 --- a/versioned_docs/version-2.13/reference/targets/python_sources.mdx +++ b/versioned_docs/version-2.13/reference/targets/python_sources.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -247,9 +247,9 @@ The latter mode is similar to creating, activating, and using a virtual environm Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.13/reference/targets/python_test.mdx b/versioned_docs/version-2.13/reference/targets/python_test.mdx index 1689dda22..92bf076de 100644 --- a/versioned_docs/version-2.13/reference/targets/python_test.mdx +++ b/versioned_docs/version-2.13/reference/targets/python_test.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -54,9 +54,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -118,11 +118,11 @@ If unset, will default to `[pytest].timeout_default`; if that option is also uns default_repr={`None`} > -Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run. +Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/pants package` goal and whose resulting artifacts should be included in the test run. -Pants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). +Pants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). -You can include anything that can be built by `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`. +You can include anything that can be built by `/home/josh/work/scie-pants/dist/pants package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`. @@ -176,9 +176,9 @@ If true, don't run this target's tests. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.13/reference/targets/python_test_utils.mdx b/versioned_docs/version-2.13/reference/targets/python_test_utils.mdx index 3899ae14f..2c84de3dd 100644 --- a/versioned_docs/version-2.13/reference/targets/python_test_utils.mdx +++ b/versioned_docs/version-2.13/reference/targets/python_test_utils.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -247,9 +247,9 @@ The latter mode is similar to creating, activating, and using a virtual environm Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.13/reference/targets/python_tests.mdx b/versioned_docs/version-2.13/reference/targets/python_tests.mdx index 3003c283a..1ce2664fe 100644 --- a/versioned_docs/version-2.13/reference/targets/python_tests.mdx +++ b/versioned_docs/version-2.13/reference/targets/python_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -211,9 +211,9 @@ If true, don't run MyPy on this target's code. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -275,11 +275,11 @@ If unset, will default to `[pytest].timeout_default`; if that option is also uns default_repr={`None`} > -Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run. +Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/pants package` goal and whose resulting artifacts should be included in the test run. -Pants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). +Pants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). -You can include anything that can be built by `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`. +You can include anything that can be built by `/home/josh/work/scie-pants/dist/pants package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`. diff --git a/versioned_docs/version-2.13/reference/targets/relocated_files.mdx b/versioned_docs/version-2.13/reference/targets/relocated_files.mdx index 73ed0c422..b920f40cd 100644 --- a/versioned_docs/version-2.13/reference/targets/relocated_files.mdx +++ b/versioned_docs/version-2.13/reference/targets/relocated_files.mdx @@ -61,7 +61,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -74,7 +74,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.13/reference/targets/resource.mdx b/versioned_docs/version-2.13/reference/targets/resource.mdx index df5cbedd5..f3f266a57 100644 --- a/versioned_docs/version-2.13/reference/targets/resource.mdx +++ b/versioned_docs/version-2.13/reference/targets/resource.mdx @@ -26,7 +26,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -52,9 +52,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.13/reference/targets/resources.mdx b/versioned_docs/version-2.13/reference/targets/resources.mdx index 5d82cf257..18612e4c6 100644 --- a/versioned_docs/version-2.13/reference/targets/resources.mdx +++ b/versioned_docs/version-2.13/reference/targets/resources.mdx @@ -24,7 +24,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -91,9 +91,9 @@ You can specify the same file name in multiple keys, so long as you don't o Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.13/reference/targets/scala_junit_test.mdx b/versioned_docs/version-2.13/reference/targets/scala_junit_test.mdx index 1484f5db9..785025062 100644 --- a/versioned_docs/version-2.13/reference/targets/scala_junit_test.mdx +++ b/versioned_docs/version-2.13/reference/targets/scala_junit_test.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.scala` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.13/reference/targets/scala_junit_tests.mdx b/versioned_docs/version-2.13/reference/targets/scala_junit_tests.mdx index 2cff3ef0f..1e5f1df20 100644 --- a/versioned_docs/version-2.13/reference/targets/scala_junit_tests.mdx +++ b/versioned_docs/version-2.13/reference/targets/scala_junit_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.scala` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -91,9 +91,9 @@ You can specify the same file name in multiple keys, so long as you don't o Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.13/reference/targets/scala_source.mdx b/versioned_docs/version-2.13/reference/targets/scala_source.mdx index e619c926f..ba88818e6 100644 --- a/versioned_docs/version-2.13/reference/targets/scala_source.mdx +++ b/versioned_docs/version-2.13/reference/targets/scala_source.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.scala` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.13/reference/targets/scala_sources.mdx b/versioned_docs/version-2.13/reference/targets/scala_sources.mdx index e6154e704..95db799b9 100644 --- a/versioned_docs/version-2.13/reference/targets/scala_sources.mdx +++ b/versioned_docs/version-2.13/reference/targets/scala_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.scala` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -103,9 +103,9 @@ If true, don't run `scalafmt` on this target's code. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.13/reference/targets/scalac_plugin.mdx b/versioned_docs/version-2.13/reference/targets/scalac_plugin.mdx index 53c633e66..2d5fa0e60 100644 --- a/versioned_docs/version-2.13/reference/targets/scalac_plugin.mdx +++ b/versioned_docs/version-2.13/reference/targets/scalac_plugin.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.scala` @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.13/reference/targets/scalatest_test.mdx b/versioned_docs/version-2.13/reference/targets/scalatest_test.mdx index 3cf31a59d..903f566b2 100644 --- a/versioned_docs/version-2.13/reference/targets/scalatest_test.mdx +++ b/versioned_docs/version-2.13/reference/targets/scalatest_test.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.scala` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.13/reference/targets/scalatest_tests.mdx b/versioned_docs/version-2.13/reference/targets/scalatest_tests.mdx index 88797d4da..a54f9c7c0 100644 --- a/versioned_docs/version-2.13/reference/targets/scalatest_tests.mdx +++ b/versioned_docs/version-2.13/reference/targets/scalatest_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.scala` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -91,9 +91,9 @@ You can specify the same file name in multiple keys, so long as you don't o Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.13/reference/targets/shell_source.mdx b/versioned_docs/version-2.13/reference/targets/shell_source.mdx index 5d680cb43..75dff950b 100644 --- a/versioned_docs/version-2.13/reference/targets/shell_source.mdx +++ b/versioned_docs/version-2.13/reference/targets/shell_source.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.13/reference/targets/shell_sources.mdx b/versioned_docs/version-2.13/reference/targets/shell_sources.mdx index d17d10110..1d612a26b 100644 --- a/versioned_docs/version-2.13/reference/targets/shell_sources.mdx +++ b/versioned_docs/version-2.13/reference/targets/shell_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -115,9 +115,9 @@ If true, don't run shfmt on this target's code. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.13/reference/targets/shunit2_test.mdx b/versioned_docs/version-2.13/reference/targets/shunit2_test.mdx index 3fd1637c2..f34cbe7eb 100644 --- a/versioned_docs/version-2.13/reference/targets/shunit2_test.mdx +++ b/versioned_docs/version-2.13/reference/targets/shunit2_test.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -67,9 +67,9 @@ Path is relative to the BUILD file's directory, e.g. `source='example.ext'` Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -119,11 +119,11 @@ Which shell to run the tests with. If unspecified, Pants will look for a shebang default_repr={`None`} > -Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run. +Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/pants package` goal and whose resulting artifacts should be included in the test run. -Pants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). +Pants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). -You can include anything that can be built by `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`. +You can include anything that can be built by `/home/josh/work/scie-pants/dist/pants package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`. diff --git a/versioned_docs/version-2.13/reference/targets/shunit2_tests.mdx b/versioned_docs/version-2.13/reference/targets/shunit2_tests.mdx index 06e8095f4..3698400f9 100644 --- a/versioned_docs/version-2.13/reference/targets/shunit2_tests.mdx +++ b/versioned_docs/version-2.13/reference/targets/shunit2_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -115,9 +115,9 @@ If true, don't run shfmt on this target's code. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -167,11 +167,11 @@ Which shell to run the tests with. If unspecified, Pants will look for a shebang default_repr={`None`} > -Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run. +Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/pants package` goal and whose resulting artifacts should be included in the test run. -Pants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). +Pants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). -You can include anything that can be built by `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`. +You can include anything that can be built by `/home/josh/work/scie-pants/dist/pants package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`. diff --git a/versioned_docs/version-2.13/reference/targets/target.mdx b/versioned_docs/version-2.13/reference/targets/target.mdx index a0a89ed34..8f92ef968 100644 --- a/versioned_docs/version-2.13/reference/targets/target.mdx +++ b/versioned_docs/version-2.13/reference/targets/target.mdx @@ -26,7 +26,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -52,9 +52,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.13/reference/targets/terraform_module.mdx b/versioned_docs/version-2.13/reference/targets/terraform_module.mdx index 3fca01783..3329e661b 100644 --- a/versioned_docs/version-2.13/reference/targets/terraform_module.mdx +++ b/versioned_docs/version-2.13/reference/targets/terraform_module.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.terraform` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -54,9 +54,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.13/reference/targets/thrift_source.mdx b/versioned_docs/version-2.13/reference/targets/thrift_source.mdx index b52d423ed..79e0da4dd 100644 --- a/versioned_docs/version-2.13/reference/targets/thrift_source.mdx +++ b/versioned_docs/version-2.13/reference/targets/thrift_source.mdx @@ -27,7 +27,7 @@ Backend: `pants.backend.codegen.thrift.apache.p Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -40,7 +40,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -53,9 +53,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.13/reference/targets/thrift_sources.mdx b/versioned_docs/version-2.13/reference/targets/thrift_sources.mdx index c19796d22..88278c020 100644 --- a/versioned_docs/version-2.13/reference/targets/thrift_sources.mdx +++ b/versioned_docs/version-2.13/reference/targets/thrift_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.codegen.thrift.apache.p Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -106,9 +106,9 @@ All dependencies must share the same value for their `resolve` field. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir:` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.13/docs/targets#target-addresses and https://www.pantsbuild.org/v2.13/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir:` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.13/reference/targets/vcs_version.mdx b/versioned_docs/version-2.13/reference/targets/vcs_version.mdx index 285e06274..411e377ea 100644 --- a/versioned_docs/version-2.13/reference/targets/vcs_version.mdx +++ b/versioned_docs/version-2.13/reference/targets/vcs_version.mdx @@ -30,7 +30,7 @@ Backend: `pants.backend.experimental.python` @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.14/reference/global-options.mdx b/versioned_docs/version-2.14/reference/global-options.mdx index c17e451fe..55529dd9e 100644 --- a/versioned_docs/version-2.14/reference/global-options.mdx +++ b/versioned_docs/version-2.14/reference/global-options.mdx @@ -319,9 +319,9 @@ ignore_warnings = [ Use this Pants version. Note that Pants only uses this to verify that you are using the requested version, as Pants cannot dynamically change the version it is using once the program is already running. -If you use the `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64` script from https://www.pantsbuild.org/v2.14/docs/installation, however, changing the value in your `pants.toml` will cause the new version to be installed and run automatically. +If you use the `/home/josh/work/scie-pants/dist/pants` script from https://www.pantsbuild.org/v2.14/docs/installation, however, changing the value in your `pants.toml` will cause the new version to be installed and run automatically. -Run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --version` to check what is being used. +Run `/home/josh/work/scie-pants/dist/pants --version` to check what is being used. @@ -822,7 +822,7 @@ Whether or not to use nailgun to run JVM requests that are marked as supporting default_repr={`3`} > -The time in seconds to wait when gracefully shutting down an interactive process (such as one opened using `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 run`) before killing it. +The time in seconds to wait when gracefully shutting down an interactive process (such as one opened using `/home/josh/work/scie-pants/dist/pants run`) before killing it. @@ -1261,14 +1261,14 @@ This may result in worse performance, but reduce the frequency of errors encount env_repr='PANTS_USE_DEPRECATED_DIRECTORY_CLI_ARGS_SEMANTICS' default_repr={`False`} removal_version='2.15.0.dev0' - removal_hint={'If `use_deprecated_directory_cli_args_semantics` is already set explicitly to `false`, simply delete the option from `pants.toml` because `false` is now the default.

If set to true, removing the option will cause directory arguments like `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 test project/dir` to now match all files and targets in the directory, whereas before it matched the target `project/dir:dir`. To keep the old semantics, use the explicit address syntax.'} + removal_hint={'If `use_deprecated_directory_cli_args_semantics` is already set explicitly to `false`, simply delete the option from `pants.toml` because `false` is now the default.

If set to true, removing the option will cause directory arguments like `/home/josh/work/scie-pants/dist/pants test project/dir` to now match all files and targets in the directory, whereas before it matched the target `project/dir:dir`. To keep the old semantics, use the explicit address syntax.'} > -If true, Pants will use the old, deprecated semantics for directory arguments like `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 test dir`: directories are shorthand for the target `dir:dir`, i.e. the target that leaves off `name=`. +If true, Pants will use the old, deprecated semantics for directory arguments like `/home/josh/work/scie-pants/dist/pants test dir`: directories are shorthand for the target `dir:dir`, i.e. the target that leaves off `name=`. -If false, Pants will use the new semantics: directory arguments will match all files and targets in the directory, e.g. `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 test dir` will run all tests in `dir`. +If false, Pants will use the new semantics: directory arguments will match all files and targets in the directory, e.g. `/home/josh/work/scie-pants/dist/pants test dir` will run all tests in `dir`. -This also impacts the behavior of the `tailor` goal. If this option is true, `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 tailor dir` will run over `dir` and all recursive sub-directories. If false, specifying a directory will only add targets for that directory. +This also impacts the behavior of the `tailor` goal. If this option is true, `/home/josh/work/scie-pants/dist/pants tailor dir` will run over `dir` and all recursive sub-directories. If false, specifying a directory will only add targets for that directory. diff --git a/versioned_docs/version-2.14/reference/goals/experimental-bsp.mdx b/versioned_docs/version-2.14/reference/goals/experimental-bsp.mdx index d6c922d3b..9601d9650 100644 --- a/versioned_docs/version-2.14/reference/goals/experimental-bsp.mdx +++ b/versioned_docs/version-2.14/reference/goals/experimental-bsp.mdx @@ -79,7 +79,7 @@ Run the Build Server Protocol server. Pants will receive BSP RPC requests via th Environment variables to set in the BSP runner script when setting up BSP in a repository. Entries are either strings in the form `ENV_VAR=value` to set an explicit value; or just `ENV_VAR` to copy the value from Pants' own environment when the experimental-bsp goal was run. -This option only takes effect when the BSP runner script is written. If the option changes, you must run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 experimental-bsp` again to write a new copy of the BSP runner script. +This option only takes effect when the BSP runner script is written. If the option changes, you must run `/home/josh/work/scie-pants/dist/pants experimental-bsp` again to write a new copy of the BSP runner script. Note: The environment variables passed to the Pants BSP server will be those set for your IDE and not your shell. For example, on macOS, the IDE is generally launched by `launchd` after clicking on a Dock icon, and not from the shell. Thus, any environment variables set for your shell will likely not be seen by the Pants BSP server. At the very least, on macOS consider writing an explicit PATH into the BSP runner script via this option. diff --git a/versioned_docs/version-2.14/reference/goals/generate-lockfiles.mdx b/versioned_docs/version-2.14/reference/goals/generate-lockfiles.mdx index b08aaff9a..90348459c 100644 --- a/versioned_docs/version-2.14/reference/goals/generate-lockfiles.mdx +++ b/versioned_docs/version-2.14/reference/goals/generate-lockfiles.mdx @@ -33,7 +33,7 @@ Only generate lockfiles for the specified resolve(s). Resolves are the logical names for the different lockfiles used in your project. For your own code's dependencies, these come from the option `[python].resolves`. For tool lockfiles, resolve names are the options scope for that tool such as `black`, `pytest`, and `mypy-protobuf`. -For example, you can run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=black --resolve=pytest --resolve=data-science` to only generate lockfiles for those two tools and your resolve named `data-science`. +For example, you can run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=black --resolve=pytest --resolve=data-science` to only generate lockfiles for those two tools and your resolve named `data-science`. If you specify an invalid resolve name, like 'fake', Pants will output all possible values. @@ -51,7 +51,7 @@ If not specified, Pants will generate lockfiles for all resolves. default_repr={`None`} > -If set, lockfile headers will say to run this command to regenerate the lockfile, rather than running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=` like normal. +If set, lockfile headers will say to run this command to regenerate the lockfile, rather than running `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=` like normal. diff --git a/versioned_docs/version-2.14/reference/goals/lint.mdx b/versioned_docs/version-2.14/reference/goals/lint.mdx index 2cda66e65..277889751 100644 --- a/versioned_docs/version-2.14/reference/goals/lint.mdx +++ b/versioned_docs/version-2.14/reference/goals/lint.mdx @@ -47,7 +47,7 @@ You can repeat this option, e.g. `lint --only=flake8 --only=shellcheck` or `lint If true, skip running all formatters in check-only mode. -FYI: when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt lint ::`, there should be little performance benefit to using this flag. Pants will reuse the results from `fmt` when running `lint`. +FYI: when running `/home/josh/work/scie-pants/dist/pants fmt lint ::`, there should be little performance benefit to using this flag. Pants will reuse the results from `fmt` when running `lint`. diff --git a/versioned_docs/version-2.14/reference/help-all.json b/versioned_docs/version-2.14/reference/help-all.json index 5ca4bcc25..9e63b8c3c 100644 --- a/versioned_docs/version-2.14/reference/help-all.json +++ b/versioned_docs/version-2.14/reference/help-all.json @@ -29585,7 +29585,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -29593,7 +29593,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -29601,7 +29601,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -29609,7 +29609,7 @@ { "alias": "packages", "default": null, - "description": "Addresses to any targets that can be built with `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, e.g. `[\"project:app\"]`.\n\nPants will build the assets as if you had run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`. It will include the results in your archive using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or even another `archive`.", + "description": "Addresses to any targets that can be built with `/home/josh/work/scie-pants/dist/pants package`, e.g. `[\"project:app\"]`.\n\nPants will build the assets as if you had run `/home/josh/work/scie-pants/dist/pants package`. It will include the results in your archive using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `/home/josh/work/scie-pants/dist/pants package`, e.g. a `pex_binary`, `python_awslambda`, or even another `archive`.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -29641,7 +29641,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -29649,7 +29649,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -29657,7 +29657,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -29665,7 +29665,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -29713,7 +29713,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -29721,7 +29721,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -29737,7 +29737,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -29817,7 +29817,7 @@ { "alias": "skip_push", "default": "False", - "description": "If set to true, do not push this image to registries when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 publish`.", + "description": "If set to true, do not push this image to registries when running `/home/josh/work/scie-pants/dist/pants publish`.", "provider": "", "required": false, "type_hint": "bool" @@ -29857,7 +29857,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -29865,7 +29865,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -29873,7 +29873,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -29905,7 +29905,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -29913,7 +29913,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -29921,7 +29921,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -29985,7 +29985,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -29993,7 +29993,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -30001,7 +30001,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -30025,7 +30025,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -30033,7 +30033,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -30057,7 +30057,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -30073,7 +30073,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -30081,7 +30081,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -30089,7 +30089,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -30121,7 +30121,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -30129,7 +30129,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -30145,7 +30145,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -30153,7 +30153,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -30161,7 +30161,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -30217,7 +30217,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -30225,7 +30225,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -30233,7 +30233,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -30257,7 +30257,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -30265,7 +30265,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -30313,7 +30313,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -30321,7 +30321,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -30345,7 +30345,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -30353,7 +30353,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built directory tree should be located.\n\nIf undefined, this will use the path to the BUILD file, For example, `src/charts/mychart:tgt_name` would be `src.charts.mychart/tgt_name/`.\n\nRegardless of whether you use the default or set this field, the path will end with Helms's file format of `-.tgz`, where `chart_name` and `chart_version` are the values extracted from the Chart.yaml file. So, using the default for this field, the target `src/charts/mychart:tgt_name` might have a final path like `src.charts.mychart/tgt_name/mychart-0.1.0.tgz`.\n\nWhen running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built directory tree should be located.\n\nIf undefined, this will use the path to the BUILD file, For example, `src/charts/mychart:tgt_name` would be `src.charts.mychart/tgt_name/`.\n\nRegardless of whether you use the default or set this field, the path will end with Helms's file format of `-.tgz`, where `chart_name` and `chart_version` are the values extracted from the Chart.yaml file. So, using the default for this field, the target `src/charts/mychart:tgt_name` might have a final path like `src.charts.mychart/tgt_name/mychart-0.1.0.tgz`.\n\nWhen running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -30385,7 +30385,7 @@ { "alias": "skip_push", "default": "False", - "description": "If set to true, do not push this Helm chart to registries when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 publish`.", + "description": "If set to true, do not push this Helm chart to registries when running `/home/josh/work/scie-pants/dist/pants publish`.", "provider": "", "required": false, "type_hint": "bool" @@ -30393,7 +30393,7 @@ { "alias": "skip_lint", "default": "False", - "description": "If set to true, do not run any linting in this Helm chart when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "description": "If set to true, do not run any linting in this Helm chart when running `/home/josh/work/scie-pants/dist/pants lint`.", "provider": "", "required": false, "type_hint": "bool" @@ -30409,7 +30409,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -30417,7 +30417,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -30433,7 +30433,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -30505,7 +30505,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -30513,7 +30513,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -30529,7 +30529,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -30561,7 +30561,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -30569,7 +30569,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -30585,7 +30585,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -30601,7 +30601,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -30633,7 +30633,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -30641,7 +30641,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -30649,7 +30649,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -30705,7 +30705,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -30713,7 +30713,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -30737,7 +30737,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -30777,7 +30777,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -30785,7 +30785,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -30817,7 +30817,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -30857,7 +30857,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -30865,7 +30865,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -30897,7 +30897,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -30937,7 +30937,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -30945,7 +30945,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -31025,7 +31025,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -31033,7 +31033,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -31057,7 +31057,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -31073,7 +31073,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -31089,7 +31089,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -31097,7 +31097,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -31105,7 +31105,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -31177,7 +31177,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -31185,7 +31185,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -31201,7 +31201,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -31265,7 +31265,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -31273,7 +31273,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -31281,7 +31281,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -31345,7 +31345,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -31353,7 +31353,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -31377,7 +31377,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -31425,7 +31425,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -31433,7 +31433,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -31473,7 +31473,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -31481,7 +31481,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -31513,7 +31513,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -31521,7 +31521,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -31561,7 +31561,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -31689,7 +31689,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -31697,7 +31697,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -31721,7 +31721,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -31857,7 +31857,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -31873,7 +31873,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -31881,7 +31881,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -31937,7 +31937,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -31945,7 +31945,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -32001,7 +32001,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -32009,7 +32009,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -32017,7 +32017,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -32113,7 +32113,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -32121,7 +32121,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -32217,7 +32217,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -32233,7 +32233,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -32241,7 +32241,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -32249,7 +32249,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built directory tree should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:bin` would be `src.python.project/bin/`.\n\nRegardless of whether you use the default or set this field, the path will end with PyOxidizer's file format of `/{debug,release}/install/`, where `platform` is a Rust platform triplet like `aarch-64-apple-darwin` and `binary_name` is the `name` of the `pyoxidizer_target`. So, using the default for this field, the target `src/python/project:bin` might have a final path like `src.python.project/bin/aarch-64-apple-darwin/release/bin`.\n\nWhen running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built directory tree should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:bin` would be `src.python.project/bin/`.\n\nRegardless of whether you use the default or set this field, the path will end with PyOxidizer's file format of `/{debug,release}/install/`, where `platform` is a Rust platform triplet like `aarch-64-apple-darwin` and `binary_name` is the `name` of the `pyoxidizer_target`. So, using the default for this field, the target `src/python/project:bin` might have a final path like `src.python.project/bin/aarch-64-apple-darwin/release/bin`.\n\nWhen running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -32297,7 +32297,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -32305,7 +32305,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -32313,7 +32313,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -32321,7 +32321,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -32377,7 +32377,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -32385,7 +32385,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -32401,7 +32401,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -32409,7 +32409,7 @@ { "alias": "entry_points", "default": null, - "description": "Any entry points, such as `console_scripts` and `gui_scripts`.\n\nSpecify as a nested dictionary, with a dictionary for each type of entry point, e.g. `console_scripts` vs. `gui_scripts`. Each dictionary maps the entry point name to either a setuptools entry point (\"path.to.module:func\") or a Pants target address to a pex_binary target.\n\n Example:\n\n entry_points={\n \"console_scripts\": {\n \"my-script\": \"project.app:main\",\n \"another-script\": \"project/subdir:pex_binary_tgt\"\n }\n }\n\nNote that Pants will assume that any value that either starts with `:` or has `/` in it, is a target address to a pex_binary target. Otherwise, it will assume it's a setuptools entry point as defined by https://packaging.python.org/specifications/entry-points/#entry-points-specification. Use `//` as a prefix for target addresses if you need to disambiguate.\n\nPants will attempt to infer dependencies, which you can confirm by running:\n\n /home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies ", + "description": "Any entry points, such as `console_scripts` and `gui_scripts`.\n\nSpecify as a nested dictionary, with a dictionary for each type of entry point, e.g. `console_scripts` vs. `gui_scripts`. Each dictionary maps the entry point name to either a setuptools entry point (\"path.to.module:func\") or a Pants target address to a pex_binary target.\n\n Example:\n\n entry_points={\n \"console_scripts\": {\n \"my-script\": \"project.app:main\",\n \"another-script\": \"project/subdir:pex_binary_tgt\"\n }\n }\n\nNote that Pants will assume that any value that either starts with `:` or has `/` in it, is a target address to a pex_binary target. Otherwise, it will assume it's a setuptools entry point as defined by https://packaging.python.org/specifications/entry-points/#entry-points-specification. Use `//` as a prefix for target addresses if you need to disambiguate.\n\nPants will attempt to infer dependencies, which you can confirm by running:\n\n /home/josh/work/scie-pants/dist/pants dependencies ", "provider": "", "required": false, "type_hint": "Dict[str, Dict[str, str]] | None" @@ -32513,7 +32513,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -32521,7 +32521,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -32529,7 +32529,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -32537,7 +32537,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -32593,7 +32593,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -32601,7 +32601,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -32617,7 +32617,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -32657,7 +32657,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -32665,7 +32665,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -32721,7 +32721,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -32729,7 +32729,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -32745,7 +32745,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -32865,7 +32865,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -32873,7 +32873,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -32993,7 +32993,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -33017,7 +33017,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -33025,7 +33025,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -33033,7 +33033,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -33073,7 +33073,7 @@ { "alias": "runtime_package_dependencies", "default": null, - "description": "Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`.", + "description": "Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/pants package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `/home/josh/work/scie-pants/dist/pants package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -33105,7 +33105,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -33209,7 +33209,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -33217,7 +33217,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -33337,7 +33337,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -33361,7 +33361,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -33369,7 +33369,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -33473,7 +33473,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -33513,7 +33513,7 @@ { "alias": "runtime_package_dependencies", "default": null, - "description": "Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`.", + "description": "Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/pants package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `/home/josh/work/scie-pants/dist/pants package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -33553,7 +33553,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -33561,7 +33561,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -33601,7 +33601,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -33609,7 +33609,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -33617,7 +33617,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -33641,7 +33641,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -33649,7 +33649,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -33673,7 +33673,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -33689,7 +33689,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -33697,7 +33697,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -33705,7 +33705,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -33777,7 +33777,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -33785,7 +33785,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -33817,7 +33817,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -33881,7 +33881,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -33889,7 +33889,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -33897,7 +33897,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -33961,7 +33961,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -33969,7 +33969,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -34001,7 +34001,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -34049,7 +34049,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -34057,7 +34057,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -34089,7 +34089,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -34097,7 +34097,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -34105,7 +34105,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -34177,7 +34177,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -34185,7 +34185,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -34209,7 +34209,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -34273,7 +34273,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -34281,7 +34281,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -34289,7 +34289,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -34329,7 +34329,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -34337,7 +34337,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -34377,7 +34377,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -34393,7 +34393,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -34401,7 +34401,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -34417,7 +34417,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -34449,7 +34449,7 @@ { "alias": "runtime_package_dependencies", "default": null, - "description": "Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`.", + "description": "Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/pants package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `/home/josh/work/scie-pants/dist/pants package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -34481,7 +34481,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -34489,7 +34489,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -34529,7 +34529,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -34561,7 +34561,7 @@ { "alias": "runtime_package_dependencies", "default": null, - "description": "Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`.", + "description": "Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/pants package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `/home/josh/work/scie-pants/dist/pants package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -34577,7 +34577,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -34585,7 +34585,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -34593,7 +34593,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -34609,7 +34609,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -34617,7 +34617,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -34625,7 +34625,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -34649,7 +34649,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -34657,7 +34657,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -34665,7 +34665,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -34697,7 +34697,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -34705,7 +34705,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -34737,7 +34737,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -34753,7 +34753,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -34761,7 +34761,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -35101,7 +35101,7 @@ "deprecation_active": false, "display_args": ["--pants-version="], "env_var": "PANTS_VERSION", - "help": "Use this Pants version. Note that Pants only uses this to verify that you are using the requested version, as Pants cannot dynamically change the version it is using once the program is already running.\n\nIf you use the `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64` script from https://www.pantsbuild.org/v2.14/docs/installation, however, changing the value in your `pants.toml` will cause the new version to be installed and run automatically.\n\nRun `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --version` to check what is being used.", + "help": "Use this Pants version. Note that Pants only uses this to verify that you are using the requested version, as Pants cannot dynamically change the version it is using once the program is already running.\n\nIf you use the `/home/josh/work/scie-pants/dist/pants` script from https://www.pantsbuild.org/v2.14/docs/installation, however, changing the value in your `pants.toml` will cause the new version to be installed and run automatically.\n\nRun `/home/josh/work/scie-pants/dist/pants --version` to check what is being used.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pants-version"], @@ -35158,7 +35158,7 @@ { "details": "from env var PANTS_BIN_NAME", "rank": "ENVIRONMENT", - "value": "/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64" + "value": "/home/josh/work/scie-pants/dist/pants" } ] } @@ -36296,7 +36296,7 @@ "--process-execution-graceful-shutdown-timeout=" ], "env_var": "PANTS_PROCESS_EXECUTION_GRACEFUL_SHUTDOWN_TIMEOUT", - "help": "The time in seconds to wait when gracefully shutting down an interactive process (such as one opened using `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 run`) before killing it.", + "help": "The time in seconds to wait when gracefully shutting down an interactive process (such as one opened using `/home/josh/work/scie-pants/dist/pants run`) before killing it.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -37800,8 +37800,8 @@ "--[no-]use-deprecated-directory-cli-args-semantics" ], "env_var": "PANTS_USE_DEPRECATED_DIRECTORY_CLI_ARGS_SEMANTICS", - "help": "If true, Pants will use the old, deprecated semantics for directory arguments like `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 test dir`: directories are shorthand for the target `dir:dir`, i.e. the target that leaves off `name=`.\n\nIf false, Pants will use the new semantics: directory arguments will match all files and targets in the directory, e.g. `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 test dir` will run all tests in `dir`.\n\nThis also impacts the behavior of the `tailor` goal. If this option is true, `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 tailor dir` will run over `dir` and all recursive sub-directories. If false, specifying a directory will only add targets for that directory.", - "removal_hint": "If `use_deprecated_directory_cli_args_semantics` is already set explicitly to `false`, simply delete the option from `pants.toml` because `false` is now the default.\n\nIf set to true, removing the option will cause directory arguments like `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 test project/dir` to now match all files and targets in the directory, whereas before it matched the target `project/dir:dir`. To keep the old semantics, use the explicit address syntax.", + "help": "If true, Pants will use the old, deprecated semantics for directory arguments like `/home/josh/work/scie-pants/dist/pants test dir`: directories are shorthand for the target `dir:dir`, i.e. the target that leaves off `name=`.\n\nIf false, Pants will use the new semantics: directory arguments will match all files and targets in the directory, e.g. `/home/josh/work/scie-pants/dist/pants test dir` will run all tests in `dir`.\n\nThis also impacts the behavior of the `tailor` goal. If this option is true, `/home/josh/work/scie-pants/dist/pants tailor dir` will run over `dir` and all recursive sub-directories. If false, specifying a directory will only add targets for that directory.", + "removal_hint": "If `use_deprecated_directory_cli_args_semantics` is already set explicitly to `false`, simply delete the option from `pants.toml` because `false` is now the default.\n\nIf set to true, removing the option will cause directory arguments like `/home/josh/work/scie-pants/dist/pants test project/dir` to now match all files and targets in the directory, whereas before it matched the target `project/dir:dir`. To keep the old semantics, use the explicit address syntax.", "removal_version": "2.15.0.dev0", "scoped_cmd_line_args": [ "--use-deprecated-directory-cli-args-semantics", @@ -38126,7 +38126,7 @@ "deprecation_active": false, "display_args": ["--autoflake-lockfile="], "env_var": "PANTS_AUTOFLAKE_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/python/lint/autoflake/autoflake.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=autoflake`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/python/lint/autoflake/autoflake.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=autoflake`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--autoflake-lockfile"], @@ -38216,7 +38216,7 @@ "deprecation_active": false, "display_args": ["--[no-]autoflake-skip"], "env_var": "PANTS_AUTOFLAKE_SKIP", - "help": "If true, don't use Autoflake when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Autoflake when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--autoflake-skip", "--no-autoflake-skip"], @@ -38280,7 +38280,7 @@ "deprecation_active": false, "display_args": ["--[no-]autoflake-export"], "env_var": "PANTS_AUTOFLAKE_EXPORT", - "help": "If true, export a virtual environment with Autoflake when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with Autoflake when running `/home/josh/work/scie-pants/dist/pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -38388,7 +38388,7 @@ "deprecation_active": false, "display_args": ["--bandit-lockfile="], "env_var": "PANTS_BANDIT_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/python/lint/bandit/bandit.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=bandit`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/python/lint/bandit/bandit.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=bandit`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--bandit-lockfile"], @@ -38504,7 +38504,7 @@ "deprecation_active": false, "display_args": ["--[no-]bandit-skip"], "env_var": "PANTS_BANDIT_SKIP", - "help": "If true, don't use Bandit when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Bandit when running `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--bandit-skip", "--no-bandit-skip"], @@ -38566,7 +38566,7 @@ "deprecation_active": false, "display_args": ["--[no-]bandit-export"], "env_var": "PANTS_BANDIT_EXPORT", - "help": "If true, export a virtual environment with Bandit when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with Bandit when running `/home/josh/work/scie-pants/dist/pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--bandit-export", "--no-bandit-export"], @@ -38706,7 +38706,7 @@ "deprecation_active": false, "display_args": ["--black-lockfile="], "env_var": "PANTS_BLACK_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/python/lint/black/black.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=black`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/python/lint/black/black.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=black`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--black-lockfile"], @@ -38859,7 +38859,7 @@ "deprecation_active": false, "display_args": ["--[no-]black-skip"], "env_var": "PANTS_BLACK_SKIP", - "help": "If true, don't use Black when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Black when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--black-skip", "--no-black-skip"], @@ -38921,7 +38921,7 @@ "deprecation_active": false, "display_args": ["--[no-]black-export"], "env_var": "PANTS_BLACK_EXPORT", - "help": "If true, export a virtual environment with Black when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with Black when running `/home/josh/work/scie-pants/dist/pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--black-export", "--no-black-export"], @@ -39143,7 +39143,7 @@ "deprecation_active": false, "display_args": ["--[no-]buf-format-skip"], "env_var": "PANTS_BUF_FORMAT_SKIP", - "help": "If true, don't use Buf when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Buf when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--buf-format-skip", "--no-buf-format-skip"], @@ -39174,7 +39174,7 @@ "deprecation_active": false, "display_args": ["--[no-]buf-lint-skip"], "env_var": "PANTS_BUF_LINT_SKIP", - "help": "If true, don't use Buf when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Buf when running `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--buf-lint-skip", "--no-buf-lint-skip"], @@ -39464,7 +39464,7 @@ "deprecation_active": false, "display_args": ["--[no-]buildifier-skip"], "env_var": "PANTS_BUILDIFIER_SKIP", - "help": "If true, don't use Buildifier when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt`.", + "help": "If true, don't use Buildifier when running `/home/josh/work/scie-pants/dist/pants fmt`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--buildifier-skip", "--no-buildifier-skip"], @@ -39675,7 +39675,7 @@ "deprecation_active": false, "display_args": ["--cli-alias=\"{'key1': val1, 'key2': val2, ...}\""], "env_var": "PANTS_CLI_ALIAS", - "help": "Register command line aliases.\n\nExample:\n\n [cli.alias]\n green = \"fmt lint check\"\n all-changed = \"--changed-since=HEAD --changed-dependees=transitive\"\n\nThis would allow you to run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 green all-changed`, which is shorthand for `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt lint check --changed-since=HEAD --changed-dependees=transitive`.\n\nNotice: this option must be placed in a config file (e.g. `pants.toml` or `pantsrc`) to have any effect.", + "help": "Register command line aliases.\n\nExample:\n\n [cli.alias]\n green = \"fmt lint check\"\n all-changed = \"--changed-since=HEAD --changed-dependees=transitive\"\n\nThis would allow you to run `/home/josh/work/scie-pants/dist/pants green all-changed`, which is shorthand for `/home/josh/work/scie-pants/dist/pants fmt lint check --changed-since=HEAD --changed-dependees=transitive`.\n\nNotice: this option must be placed in a config file (e.g. `pants.toml` or `pantsrc`) to have any effect.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--cli-alias"], @@ -40061,7 +40061,7 @@ "deprecation_active": false, "display_args": ["--coverage-py-lockfile="], "env_var": "PANTS_COVERAGE_PY_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/python/subsystems/coverage_py.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=coverage-py`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/python/subsystems/coverage_py.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=coverage-py`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--coverage-py-lockfile"], @@ -40549,7 +40549,7 @@ "deprecation_active": false, "display_args": ["--debugpy-lockfile="], "env_var": "PANTS_DEBUGPY_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/python/subsystems/debugpy.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=debugpy`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/python/subsystems/debugpy.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=debugpy`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--debugpy-lockfile"], @@ -41051,7 +41051,7 @@ "deprecation_active": false, "display_args": ["--docformatter-lockfile="], "env_var": "PANTS_DOCFORMATTER_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/python/lint/docformatter/docformatter.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=docformatter`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/python/lint/docformatter/docformatter.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=docformatter`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--docformatter-lockfile"], @@ -41141,7 +41141,7 @@ "deprecation_active": false, "display_args": ["--[no-]docformatter-skip"], "env_var": "PANTS_DOCFORMATTER_SKIP", - "help": "If true, don't use docformatter when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use docformatter when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -41208,7 +41208,7 @@ "deprecation_active": false, "display_args": ["--[no-]docformatter-export"], "env_var": "PANTS_DOCFORMATTER_EXPORT", - "help": "If true, export a virtual environment with docformatter when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with docformatter when running `/home/josh/work/scie-pants/dist/pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -41572,7 +41572,7 @@ "--docker-run-args=\"[, , ...]\"" ], "env_var": "PANTS_DOCKER_RUN_ARGS", - "help": "Additional arguments to use for `docker run` invocations.\n\nExample:\n\n $ /home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 run --docker-run-args=\"-p 127.0.0.1:80:8080/tcp --name demo\" src/example:image -- [image entrypoint args]\n\nTo provide the top-level options to the `docker` client, use `[docker].env_vars` to configure the [Environment variables](https://docs.docker.com/engine/reference/commandline/cli/#environment-variables) as appropriate.\n\nThe arguments for the image entrypoint may be passed on the command line after a double dash (`--`), or using the `--run-args` option.\n\nDefaults to `--interactive --tty` when stdout is connected to a terminal.", + "help": "Additional arguments to use for `docker run` invocations.\n\nExample:\n\n $ /home/josh/work/scie-pants/dist/pants run --docker-run-args=\"-p 127.0.0.1:80:8080/tcp --name demo\" src/example:image -- [image entrypoint args]\n\nTo provide the top-level options to the `docker` client, use `[docker].env_vars` to configure the [Environment variables](https://docs.docker.com/engine/reference/commandline/cli/#environment-variables) as appropriate.\n\nThe arguments for the image entrypoint may be passed on the command line after a double dash (`--`), or using the `--run-args` option.\n\nDefaults to `--interactive --tty` when stdout is connected to a terminal.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--docker-run-args"], @@ -41712,7 +41712,7 @@ "deprecation_active": false, "display_args": ["--dockerfile-parser-lockfile="], "env_var": "PANTS_DOCKERFILE_PARSER_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/docker/subsystems/dockerfile.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=dockerfile-parser`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/docker/subsystems/dockerfile.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=dockerfile-parser`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--dockerfile-parser-lockfile"], @@ -42146,7 +42146,7 @@ "--experimental-bsp-runner-env-vars=\"['', '', ...]\"" ], "env_var": "PANTS_EXPERIMENTAL_BSP_RUNNER_ENV_VARS", - "help": "Environment variables to set in the BSP runner script when setting up BSP in a repository. Entries are either strings in the form `ENV_VAR=value` to set an explicit value; or just `ENV_VAR` to copy the value from Pants' own environment when the experimental-bsp goal was run.\n\nThis option only takes effect when the BSP runner script is written. If the option changes, you must run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 experimental-bsp` again to write a new copy of the BSP runner script.\n\nNote: The environment variables passed to the Pants BSP server will be those set for your IDE and not your shell. For example, on macOS, the IDE is generally launched by `launchd` after clicking on a Dock icon, and not from the shell. Thus, any environment variables set for your shell will likely not be seen by the Pants BSP server. At the very least, on macOS consider writing an explicit PATH into the BSP runner script via this option.", + "help": "Environment variables to set in the BSP runner script when setting up BSP in a repository. Entries are either strings in the form `ENV_VAR=value` to set an explicit value; or just `ENV_VAR` to copy the value from Pants' own environment when the experimental-bsp goal was run.\n\nThis option only takes effect when the BSP runner script is written. If the option changes, you must run `/home/josh/work/scie-pants/dist/pants experimental-bsp` again to write a new copy of the BSP runner script.\n\nNote: The environment variables passed to the Pants BSP server will be those set for your IDE and not your shell. For example, on macOS, the IDE is generally launched by `launchd` after clicking on a Dock icon, and not from the shell. Thus, any environment variables set for your shell will likely not be seen by the Pants BSP server. At the very least, on macOS consider writing an explicit PATH into the BSP runner script via this option.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--experimental-bsp-runner-env-vars"], @@ -42754,7 +42754,7 @@ "deprecation_active": false, "display_args": ["--flake8-lockfile="], "env_var": "PANTS_FLAKE8_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/python/lint/flake8/flake8.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=flake8`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/python/lint/flake8/flake8.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=flake8`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--flake8-lockfile"], @@ -42973,7 +42973,7 @@ "deprecation_active": false, "display_args": ["--[no-]flake8-skip"], "env_var": "PANTS_FLAKE8_SKIP", - "help": "If true, don't use Flake8 when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Flake8 when running `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--flake8-skip", "--no-flake8-skip"], @@ -43035,7 +43035,7 @@ "deprecation_active": false, "display_args": ["--[no-]flake8-export"], "env_var": "PANTS_FLAKE8_EXPORT", - "help": "If true, export a virtual environment with Flake8 when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with Flake8 when running `/home/josh/work/scie-pants/dist/pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--flake8-export", "--no-flake8-export"], @@ -43150,7 +43150,7 @@ "deprecation_active": false, "display_args": ["--generate-lockfiles-custom-command="], "env_var": "PANTS_GENERATE_LOCKFILES_CUSTOM_COMMAND", - "help": "If set, lockfile headers will say to run this command to regenerate the lockfile, rather than running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=` like normal.", + "help": "If set, lockfile headers will say to run this command to regenerate the lockfile, rather than running `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=` like normal.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--generate-lockfiles-custom-command"], @@ -43180,7 +43180,7 @@ "--generate-lockfiles-resolve=\"['', '', ...]\"" ], "env_var": "PANTS_GENERATE_LOCKFILES_RESOLVE", - "help": "Only generate lockfiles for the specified resolve(s).\n\nResolves are the logical names for the different lockfiles used in your project. For your own code's dependencies, these come from the option `[python].resolves`. For tool lockfiles, resolve names are the options scope for that tool such as `black`, `pytest`, and `mypy-protobuf`.\n\nFor example, you can run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=black --resolve=pytest --resolve=data-science` to only generate lockfiles for those two tools and your resolve named `data-science`.\n\nIf you specify an invalid resolve name, like 'fake', Pants will output all possible values.\n\nIf not specified, Pants will generate lockfiles for all resolves.", + "help": "Only generate lockfiles for the specified resolve(s).\n\nResolves are the logical names for the different lockfiles used in your project. For your own code's dependencies, these come from the option `[python].resolves`. For tool lockfiles, resolve names are the options scope for that tool such as `black`, `pytest`, and `mypy-protobuf`.\n\nFor example, you can run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=black --resolve=pytest --resolve=data-science` to only generate lockfiles for those two tools and your resolve named `data-science`.\n\nIf you specify an invalid resolve name, like 'fake', Pants will output all possible values.\n\nIf not specified, Pants will generate lockfiles for all resolves.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--generate-lockfiles-resolve"], @@ -43330,7 +43330,7 @@ "deprecation_active": false, "display_args": ["--[no-]gofmt-skip"], "env_var": "PANTS_GOFMT_SKIP", - "help": "If true, don't use gofmt when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use gofmt when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--gofmt-skip", "--no-gofmt-skip"], @@ -43721,7 +43721,7 @@ "deprecation_active": false, "display_args": ["--google-java-format-lockfile="], "env_var": "PANTS_GOOGLE_JAVA_FORMAT_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/java/lint/google_java_format/google_java_format.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=google-java-format`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/java/lint/google_java_format/google_java_format.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=google-java-format`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--google-java-format-lockfile"], @@ -43787,7 +43787,7 @@ "deprecation_active": false, "display_args": ["--[no-]google-java-format-skip"], "env_var": "PANTS_GOOGLE_JAVA_FORMAT_SKIP", - "help": "If true, don't use Google Java Format when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Google Java Format when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -44305,7 +44305,7 @@ "deprecation_active": false, "display_args": ["--[no-]hadolint-skip"], "env_var": "PANTS_HADOLINT_SKIP", - "help": "If true, don't use Hadolint when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Hadolint when running `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--hadolint-skip", "--no-hadolint-skip"], @@ -44856,7 +44856,7 @@ "deprecation_active": false, "display_args": ["--helm-k8s-parser-lockfile="], "env_var": "PANTS_HELM_K8S_PARSER_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/helm/subsystems/k8s_parser.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=helm-k8s-parser`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/helm/subsystems/k8s_parser.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=helm-k8s-parser`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--helm-k8s-parser-lockfile"], @@ -45001,7 +45001,7 @@ "deprecation_active": false, "display_args": ["--helm-post-renderer-lockfile="], "env_var": "PANTS_HELM_POST_RENDERER_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/helm/subsystems/post_renderer.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=helm-post-renderer`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/helm/subsystems/post_renderer.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=helm-post-renderer`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--helm-post-renderer-lockfile"], @@ -45397,7 +45397,7 @@ "deprecation_active": false, "display_args": ["--ipython-lockfile="], "env_var": "PANTS_IPYTHON_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/python/subsystems/ipython.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=ipython`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/python/subsystems/ipython.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=ipython`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--ipython-lockfile"], @@ -45627,7 +45627,7 @@ "deprecation_active": false, "display_args": ["--isort-lockfile="], "env_var": "PANTS_ISORT_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/python/lint/isort/isort.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=isort`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/python/lint/isort/isort.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=isort`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--isort-lockfile"], @@ -45787,7 +45787,7 @@ "deprecation_active": false, "display_args": ["--[no-]isort-skip"], "env_var": "PANTS_ISORT_SKIP", - "help": "If true, don't use isort when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use isort when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--isort-skip", "--no-isort-skip"], @@ -45849,7 +45849,7 @@ "deprecation_active": false, "display_args": ["--[no-]isort-export"], "env_var": "PANTS_ISORT_EXPORT", - "help": "If true, export a virtual environment with isort when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with isort when running `/home/josh/work/scie-pants/dist/pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--isort-export", "--no-isort-export"], @@ -46152,7 +46152,7 @@ "deprecation_active": false, "display_args": ["--junit-lockfile="], "env_var": "PANTS_JUNIT_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/jvm/test/junit.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=junit`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/jvm/test/junit.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=junit`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--junit-lockfile"], @@ -46838,7 +46838,7 @@ "deprecation_active": false, "display_args": ["--ktlint-lockfile="], "env_var": "PANTS_KTLINT_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/kotlin/lint/ktlint/ktlint.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=ktlint`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/kotlin/lint/ktlint/ktlint.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=ktlint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--ktlint-lockfile"], @@ -46902,7 +46902,7 @@ "deprecation_active": false, "display_args": ["--[no-]ktlint-skip"], "env_var": "PANTS_KTLINT_SKIP", - "help": "If true, don't use Ktlint when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Ktlint when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--ktlint-skip", "--no-ktlint-skip"], @@ -47040,7 +47040,7 @@ "deprecation_active": false, "display_args": ["--lambdex-lockfile="], "env_var": "PANTS_LAMBDEX_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/python/subsystems/lambdex.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=lambdex`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/python/subsystems/lambdex.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=lambdex`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--lambdex-lockfile"], @@ -47203,7 +47203,7 @@ "deprecation_active": false, "display_args": ["--[no-]lint-skip-formatters"], "env_var": "PANTS_LINT_SKIP_FORMATTERS", - "help": "If true, skip running all formatters in check-only mode.\n\nFYI: when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt lint ::`, there should be little performance benefit to using this flag. Pants will reuse the results from `fmt` when running `lint`.", + "help": "If true, skip running all formatters in check-only mode.\n\nFYI: when running `/home/josh/work/scie-pants/dist/pants fmt lint ::`, there should be little performance benefit to using this flag. Pants will reuse the results from `fmt` when running `lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -47446,7 +47446,7 @@ "deprecation_active": false, "display_args": ["--mypy-lockfile="], "env_var": "PANTS_MYPY_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/python/typecheck/mypy/mypy.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=mypy`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/python/typecheck/mypy/mypy.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=mypy`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--mypy-lockfile"], @@ -47663,7 +47663,7 @@ "deprecation_active": false, "display_args": ["--mypy-extra-type-stubs-lockfile="], "env_var": "PANTS_MYPY_EXTRA_TYPE_STUBS_LOCKFILE", - "help": "Path to a lockfile for the option `[mypy].extra_type_stubs`.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this if you use `[mypy].extra_type_stubs`, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=mypy-extra-type-stubs`.", + "help": "Path to a lockfile for the option `[mypy].extra_type_stubs`.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this if you use `[mypy].extra_type_stubs`, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=mypy-extra-type-stubs`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--mypy-extra-type-stubs-lockfile"], @@ -47696,7 +47696,7 @@ "deprecation_active": false, "display_args": ["--[no-]mypy-skip"], "env_var": "PANTS_MYPY_SKIP", - "help": "If true, don't use MyPy when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 check`.", + "help": "If true, don't use MyPy when running `/home/josh/work/scie-pants/dist/pants check`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--mypy-skip", "--no-mypy-skip"], @@ -47758,7 +47758,7 @@ "deprecation_active": false, "display_args": ["--[no-]mypy-export"], "env_var": "PANTS_MYPY_EXPORT", - "help": "If true, export a virtual environment with MyPy when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with MyPy when running `/home/josh/work/scie-pants/dist/pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--mypy-export", "--no-mypy-export"], @@ -47896,7 +47896,7 @@ "deprecation_active": false, "display_args": ["--mypy-protobuf-lockfile="], "env_var": "PANTS_MYPY_PROTOBUF_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/codegen/protobuf/python/mypy_protobuf.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=mypy-protobuf`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/codegen/protobuf/python/mypy_protobuf.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=mypy-protobuf`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--mypy-protobuf-lockfile"], @@ -48581,7 +48581,7 @@ "deprecation_active": false, "display_args": ["--poetry-lockfile="], "env_var": "PANTS_POETRY_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/python/subsystems/poetry.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=poetry`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/python/subsystems/poetry.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=poetry`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--poetry-lockfile"], @@ -48697,7 +48697,7 @@ "deprecation_active": false, "display_args": ["--protobuf-java-grpc-lockfile="], "env_var": "PANTS_PROTOBUF_JAVA_GRPC_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/codegen/protobuf/java/grpc-java.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=protobuf-java-grpc`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/codegen/protobuf/java/grpc-java.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=protobuf-java-grpc`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--protobuf-java-grpc-lockfile"], @@ -49205,7 +49205,7 @@ "deprecation_active": false, "display_args": ["--pylint-lockfile="], "env_var": "PANTS_PYLINT_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/python/lint/pylint/pylint.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=pylint`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/python/lint/pylint/pylint.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=pylint`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pylint-lockfile"], @@ -49391,7 +49391,7 @@ "deprecation_active": false, "display_args": ["--[no-]pylint-skip"], "env_var": "PANTS_PYLINT_SKIP", - "help": "If true, don't use Pylint when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Pylint when running `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pylint-skip", "--no-pylint-skip"], @@ -49453,7 +49453,7 @@ "deprecation_active": false, "display_args": ["--[no-]pylint-export"], "env_var": "PANTS_PYLINT_EXPORT", - "help": "If true, export a virtual environment with Pylint when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with Pylint when running `/home/josh/work/scie-pants/dist/pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pylint-export", "--no-pylint-export"], @@ -49591,7 +49591,7 @@ "deprecation_active": false, "display_args": ["--pyoxidizer-lockfile="], "env_var": "PANTS_PYOXIDIZER_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/python/packaging/pyoxidizer/pyoxidizer.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=pyoxidizer`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/python/packaging/pyoxidizer/pyoxidizer.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=pyoxidizer`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pyoxidizer-lockfile"], @@ -49791,7 +49791,7 @@ "deprecation_active": false, "display_args": ["--pytest-lockfile="], "env_var": "PANTS_PYTEST_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/python/subsystems/pytest.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=pytest`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/python/subsystems/pytest.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=pytest`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pytest-lockfile"], @@ -50069,7 +50069,7 @@ "deprecation_active": false, "display_args": ["--[no-]pytest-export"], "env_var": "PANTS_PYTEST_EXPORT", - "help": "If true, export a virtual environment with Pytest when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with Pytest when running `/home/josh/work/scie-pants/dist/pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pytest-export", "--no-pytest-export"], @@ -50310,7 +50310,7 @@ "--python-resolves=\"{'key1': val1, 'key2': val2, ...}\"" ], "env_var": "PANTS_PYTHON_RESOLVES", - "help": "A mapping of logical names to lockfile paths used in your project.\n\nMany organizations only need a single resolve for their whole project, which is a good default and often the simplest thing to do. However, you may need multiple resolves, such as if you use two conflicting versions of a requirement in your repository.\n\nIf you only need a single resolve, run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles` to generate the lockfile.\n\nIf you need multiple resolves:\n\n 1. Via this option, define multiple resolve names and their lockfile paths. The names should be meaningful to your repository, such as `data-science` or `pants-plugins`.\n 2. Set the default with `[python].default_resolve`.\n 3. Update your `python_requirement` targets with the `resolve` field to declare which resolve they should be available in. They default to `[python].default_resolve`, so you only need to update targets that you want in non-default resolves. (Often you'll set this via the `python_requirements` or `poetry_requirements` target generators)\n 4. Run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles` to generate the lockfiles. If the results aren't what you'd expect, adjust the prior step.\n 5. Update any targets like `python_source` / `python_sources`, `python_test` / `python_tests`, and `pex_binary` which need to set a non-default resolve with the `resolve` field.\n\nIf a target can work with multiple resolves, you can either use the `parametrize` mechanism or manually create a distinct target per resolve. See https://www.pantsbuild.org/v2.14/docs/targets for information about `parametrize`.\n\nFor example:\n\n python_sources(\n resolve=parametrize(\"data-science\", \"web-app\"),\n )\n\nYou can name the lockfile paths what you would like; Pants does not expect a certain file extension or location.\n\nOnly applies if `[python].enable_resolves` is true.", + "help": "A mapping of logical names to lockfile paths used in your project.\n\nMany organizations only need a single resolve for their whole project, which is a good default and often the simplest thing to do. However, you may need multiple resolves, such as if you use two conflicting versions of a requirement in your repository.\n\nIf you only need a single resolve, run `/home/josh/work/scie-pants/dist/pants generate-lockfiles` to generate the lockfile.\n\nIf you need multiple resolves:\n\n 1. Via this option, define multiple resolve names and their lockfile paths. The names should be meaningful to your repository, such as `data-science` or `pants-plugins`.\n 2. Set the default with `[python].default_resolve`.\n 3. Update your `python_requirement` targets with the `resolve` field to declare which resolve they should be available in. They default to `[python].default_resolve`, so you only need to update targets that you want in non-default resolves. (Often you'll set this via the `python_requirements` or `poetry_requirements` target generators)\n 4. Run `/home/josh/work/scie-pants/dist/pants generate-lockfiles` to generate the lockfiles. If the results aren't what you'd expect, adjust the prior step.\n 5. Update any targets like `python_source` / `python_sources`, `python_test` / `python_tests`, and `pex_binary` which need to set a non-default resolve with the `resolve` field.\n\nIf a target can work with multiple resolves, you can either use the `parametrize` mechanism or manually create a distinct target per resolve. See https://www.pantsbuild.org/v2.14/docs/targets for information about `parametrize`.\n\nFor example:\n\n python_sources(\n resolve=parametrize(\"data-science\", \"web-app\"),\n )\n\nYou can name the lockfile paths what you would like; Pants does not expect a certain file extension or location.\n\nOnly applies if `[python].enable_resolves` is true.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--python-resolves"], @@ -50872,8 +50872,8 @@ "deprecation_active": true, "display_args": ["--python-lockfile-generator="], "env_var": "PANTS_PYTHON_LOCKFILE_GENERATOR", - "help": "Whether to use Pex or Poetry with the `generate-lockfiles` goal.\n\nPoetry does not support these features:\n\n 1) `[python-repos]` for custom indexes/cheeseshops.\n 2) VCS (Git) requirements.\n 3) `[GLOBAL].ca_certs_path`.\n\nIf you use any of these features, you should use Pex.\n\nSeveral users have also had issues with how Poetry's lockfile generation handles environment markers for transitive dependencies; certain dependencies end up with nonsensical environment markers which cause the dependency to not be installed, then for Pants/Pex to complain the dependency is missing, even though it's in the lockfile. There is a workaround: for `[python].resolves`, manually create a `python_requirement` target for the problematic transitive dependencies so that they are seen as direct requirements, rather than transitive. For tool lockfiles, add the problematic transitive dependency to `[tool].extra_requirements`, e.g. `[isort].extra_requirements`. Then, regenerate the lockfile(s) with the `generate-lockfiles` goal. Alternatively, use Pex for generation.\n\nFinally, installing from a Poetry-generated lockfile is slower than installing from a Pex lockfile. When using a Pex lockfile, Pants will only install the subset needed for the current task.\n\nHowever, Pex lockfile generation is a new feature. Given how vast the Python packaging ecosystem is, it is possible you may experience edge cases / bugs we haven't yet covered. Bug reports are appreciated! https://github.com/pantsbuild/pants/issues/new/choose\n\nNote that while Pex generates locks in a proprietary JSON format, you can use the `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export` goal for Pants to create a virtual environment for interoperability with tools like IDEs.", - "removal_hint": "Pants will soon only support generating lockfiles via the Pex format, as Poetry-generated lockfiles mismatch with Pants's pip-based approach.\n\nIf you do not want to use Pex lockfiles, you will still be able to manually generate lockfiles, e.g. by manually running `poetry export --dev` on your `poetry.lock`. See https://www.pantsbuild.org/v2.14/docs/python-third-party-dependencies#manually-generating-lockfiles for more information.\n\nWhile Pex generates locks in a proprietary JSON format, you can use the `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export` goal for Pants to create a virtual environment for interoperability with tools like IDEs.\n\nPlease open a GitHub issue or reach out on Slack if you encounter issues while migrating: https://www.pantsbuild.org/v2.14/docs/getting-help\n\nTip: you can incrementally migrate one lockfile at-a-time by dynamically setting the option `--python-lockfile-generator`. For example:\n\n /home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --python-lockfile-generator=pex generate-lockfiles --resolve=black --resolve=isort\n /home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --python-lockfile-generator=poetry generate-lockfiles --resolve=python-default", + "help": "Whether to use Pex or Poetry with the `generate-lockfiles` goal.\n\nPoetry does not support these features:\n\n 1) `[python-repos]` for custom indexes/cheeseshops.\n 2) VCS (Git) requirements.\n 3) `[GLOBAL].ca_certs_path`.\n\nIf you use any of these features, you should use Pex.\n\nSeveral users have also had issues with how Poetry's lockfile generation handles environment markers for transitive dependencies; certain dependencies end up with nonsensical environment markers which cause the dependency to not be installed, then for Pants/Pex to complain the dependency is missing, even though it's in the lockfile. There is a workaround: for `[python].resolves`, manually create a `python_requirement` target for the problematic transitive dependencies so that they are seen as direct requirements, rather than transitive. For tool lockfiles, add the problematic transitive dependency to `[tool].extra_requirements`, e.g. `[isort].extra_requirements`. Then, regenerate the lockfile(s) with the `generate-lockfiles` goal. Alternatively, use Pex for generation.\n\nFinally, installing from a Poetry-generated lockfile is slower than installing from a Pex lockfile. When using a Pex lockfile, Pants will only install the subset needed for the current task.\n\nHowever, Pex lockfile generation is a new feature. Given how vast the Python packaging ecosystem is, it is possible you may experience edge cases / bugs we haven't yet covered. Bug reports are appreciated! https://github.com/pantsbuild/pants/issues/new/choose\n\nNote that while Pex generates locks in a proprietary JSON format, you can use the `/home/josh/work/scie-pants/dist/pants export` goal for Pants to create a virtual environment for interoperability with tools like IDEs.", + "removal_hint": "Pants will soon only support generating lockfiles via the Pex format, as Poetry-generated lockfiles mismatch with Pants's pip-based approach.\n\nIf you do not want to use Pex lockfiles, you will still be able to manually generate lockfiles, e.g. by manually running `poetry export --dev` on your `poetry.lock`. See https://www.pantsbuild.org/v2.14/docs/python-third-party-dependencies#manually-generating-lockfiles for more information.\n\nWhile Pex generates locks in a proprietary JSON format, you can use the `/home/josh/work/scie-pants/dist/pants export` goal for Pants to create a virtual environment for interoperability with tools like IDEs.\n\nPlease open a GitHub issue or reach out on Slack if you encounter issues while migrating: https://www.pantsbuild.org/v2.14/docs/getting-help\n\nTip: you can incrementally migrate one lockfile at-a-time by dynamically setting the option `--python-lockfile-generator`. For example:\n\n /home/josh/work/scie-pants/dist/pants --python-lockfile-generator=pex generate-lockfiles --resolve=black --resolve=isort\n /home/josh/work/scie-pants/dist/pants --python-lockfile-generator=poetry generate-lockfiles --resolve=python-default", "removal_version": "2.15.0.dev0", "scoped_cmd_line_args": ["--python-lockfile-generator"], "typ": "LockfileGenerator", @@ -50904,7 +50904,7 @@ "display_args": ["--python-requirement-constraints="], "env_var": "PANTS_PYTHON_REQUIREMENT_CONSTRAINTS", "help": "When resolving third-party requirements for your own code (vs. tools you run), use this constraints file to determine which versions to use.\n\nMutually exclusive with `[python].enable_resolves`, which we generally recommend as an improvement over constraints file.\n\nSee https://pip.pypa.io/en/stable/user_guide/#constraints-files for more information on the format of constraint files and how constraints are applied in Pex and pip.\n\nThis only applies when resolving user requirements, rather than tools you run like Black and Pytest. To constrain tools, set `[tool].lockfile`, e.g. `[black].lockfile`.", - "removal_hint": "We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.\n\nTo migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles`.", + "removal_hint": "We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.\n\nTo migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `/home/josh/work/scie-pants/dist/pants generate-lockfiles`.", "removal_version": "3.0.0.dev0", "scoped_cmd_line_args": ["--python-requirement-constraints"], "typ": "file_option", @@ -50930,7 +50930,7 @@ "display_args": ["--[no-]python-resolve-all-constraints"], "env_var": "PANTS_PYTHON_RESOLVE_ALL_CONSTRAINTS", "help": "(Only relevant when using `[python].requirement_constraints.`) If enabled, when resolving requirements, Pants will first resolve your entire constraints file as a single global resolve. Then, if the code uses a subset of your constraints file, Pants will extract the relevant requirements from that global resolve so that only what's actually needed gets used. If disabled, Pants will not use a global resolve and will resolve each subset of your requirements independently.\n\nUsually this option should be enabled because it can result in far fewer resolves.", - "removal_hint": "We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.\n\nTo migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles`.", + "removal_hint": "We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.\n\nTo migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `/home/josh/work/scie-pants/dist/pants generate-lockfiles`.", "removal_version": "3.0.0.dev0", "scoped_cmd_line_args": [ "--python-resolve-all-constraints", @@ -51316,7 +51316,7 @@ "deprecation_active": false, "display_args": ["--python-infer-init-files="], "env_var": "PANTS_PYTHON_INFER_INIT_FILES", - "help": "Infer a target's dependencies on any `__init__.py` files in the packages it is located in (recursively upward in the directory structure).\n\nEven if this is set to `never` or `content_only`, Pants will still always include any ancestor `__init__.py` files in the sandbox. Only, they will not be \"proper\" dependencies, e.g. they will not show up in `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` and their own dependencies will not be used.\n\nBy default, Pants only adds a \"proper\" dependency if there is content in the `__init__.py` file. This makes sure that dependencies are added when likely necessary to build, while also avoiding adding unnecessary dependencies. While accurate, those unnecessary dependencies can complicate setting metadata like the `interpreter_constraints` and `resolve` fields.", + "help": "Infer a target's dependencies on any `__init__.py` files in the packages it is located in (recursively upward in the directory structure).\n\nEven if this is set to `never` or `content_only`, Pants will still always include any ancestor `__init__.py` files in the sandbox. Only, they will not be \"proper\" dependencies, e.g. they will not show up in `/home/josh/work/scie-pants/dist/pants dependencies` and their own dependencies will not be used.\n\nBy default, Pants only adds a \"proper\" dependency if there is content in the `__init__.py` file. This makes sure that dependencies are added when likely necessary to build, while also avoiding adding unnecessary dependencies. While accurate, those unnecessary dependencies can complicate setting metadata like the `interpreter_constraints` and `resolve` fields.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--python-infer-init-files"], @@ -51942,7 +51942,7 @@ "deprecation_active": false, "display_args": ["--pyupgrade-lockfile="], "env_var": "PANTS_PYUPGRADE_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/python/lint/pyupgrade/pyupgrade.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=pyupgrade`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/python/lint/pyupgrade/pyupgrade.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=pyupgrade`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pyupgrade-lockfile"], @@ -52032,7 +52032,7 @@ "deprecation_active": false, "display_args": ["--[no-]pyupgrade-skip"], "env_var": "PANTS_PYUPGRADE_SKIP", - "help": "If true, don't use pyupgrade when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use pyupgrade when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pyupgrade-skip", "--no-pyupgrade-skip"], @@ -52096,7 +52096,7 @@ "deprecation_active": false, "display_args": ["--[no-]pyupgrade-export"], "env_var": "PANTS_PYUPGRADE_EXPORT", - "help": "If true, export a virtual environment with pyupgrade when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with pyupgrade when running `/home/josh/work/scie-pants/dist/pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -52838,7 +52838,7 @@ "deprecation_active": false, "display_args": ["--scalafmt-lockfile="], "env_var": "PANTS_SCALAFMT_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/scala/lint/scalafmt/scalafmt.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalafmt`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/scala/lint/scalafmt/scalafmt.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=scalafmt`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalafmt-lockfile"], @@ -52904,7 +52904,7 @@ "deprecation_active": false, "display_args": ["--[no-]scalafmt-skip"], "env_var": "PANTS_SCALAFMT_SKIP", - "help": "If true, don't use scalafmt when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use scalafmt when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalafmt-skip", "--no-scalafmt-skip"], @@ -53007,7 +53007,7 @@ "deprecation_active": false, "display_args": ["--scalapb-lockfile="], "env_var": "PANTS_SCALAPB_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/codegen/protobuf/scala/scalapbc.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalapb`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/codegen/protobuf/scala/scalapbc.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=scalapb`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalapb-lockfile"], @@ -53174,7 +53174,7 @@ "deprecation_active": false, "display_args": ["--scalatest-lockfile="], "env_var": "PANTS_SCALATEST_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/scala/subsystems/scalatest.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalatest`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/scala/subsystems/scalatest.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=scalatest`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalatest-lockfile"], @@ -53656,7 +53656,7 @@ "deprecation_active": false, "display_args": ["--setuptools-lockfile="], "env_var": "PANTS_SETUPTOOLS_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/python/subsystems/setuptools.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=setuptools`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/python/subsystems/setuptools.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=setuptools`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--setuptools-lockfile"], @@ -53795,7 +53795,7 @@ "deprecation_active": false, "display_args": ["--setuptools-scm-lockfile="], "env_var": "PANTS_SETUPTOOLS_SCM_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/python/subsystems/setuptools_scm.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=setuptools-scm`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/python/subsystems/setuptools_scm.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=setuptools-scm`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--setuptools-scm-lockfile"], @@ -54229,7 +54229,7 @@ "deprecation_active": false, "display_args": ["--[no-]shellcheck-skip"], "env_var": "PANTS_SHELLCHECK_SKIP", - "help": "If true, don't use Shellcheck when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Shellcheck when running `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--shellcheck-skip", "--no-shellcheck-skip"], @@ -54523,7 +54523,7 @@ "deprecation_active": false, "display_args": ["--[no-]shfmt-skip"], "env_var": "PANTS_SHFMT_SKIP", - "help": "If true, don't use shfmt when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use shfmt when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--shfmt-skip", "--no-shfmt-skip"], @@ -55053,7 +55053,7 @@ "deprecation_active": false, "display_args": ["--[no-]terraform-fmt-skip"], "env_var": "PANTS_TERRAFORM_FMT_SKIP", - "help": "If true, don't use `terraform fmt` when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use `terraform fmt` when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -55198,7 +55198,7 @@ "deprecation_active": false, "display_args": ["--terraform-hcl2-parser-lockfile="], "env_var": "PANTS_TERRAFORM_HCL2_PARSER_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/terraform/hcl2.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=terraform-hcl2-parser`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/terraform/hcl2.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=terraform-hcl2-parser`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--terraform-hcl2-parser-lockfile"], @@ -55241,7 +55241,7 @@ "deprecation_active": false, "display_args": ["--[no-]terraform-validate-skip"], "env_var": "PANTS_TERRAFORM_VALIDATE_SKIP", - "help": "If true, don't use `terraform validate` when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 check`.", + "help": "If true, don't use `terraform validate` when running `/home/josh/work/scie-pants/dist/pants check`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -55876,7 +55876,7 @@ "deprecation_active": false, "display_args": ["--twine-lockfile="], "env_var": "PANTS_TWINE_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/python/subsystems/twine.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=twine`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/python/subsystems/twine.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=twine`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--twine-lockfile"], @@ -56060,7 +56060,7 @@ "deprecation_active": false, "display_args": ["--[no-]twine-skip"], "env_var": "PANTS_TWINE_SKIP", - "help": "If true, don't use Twine when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 publish`.", + "help": "If true, don't use Twine when running `/home/josh/work/scie-pants/dist/pants publish`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--twine-skip", "--no-twine-skip"], @@ -56386,7 +56386,7 @@ "deprecation_active": false, "display_args": ["--yapf-lockfile="], "env_var": "PANTS_YAPF_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/python/lint/yapf/yapf.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=yapf`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/python/lint/yapf/yapf.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=yapf`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--yapf-lockfile"], @@ -56539,7 +56539,7 @@ "deprecation_active": false, "display_args": ["--[no-]yapf-skip"], "env_var": "PANTS_YAPF_SKIP", - "help": "If true, don't use yapf when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use yapf when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--yapf-skip", "--no-yapf-skip"], @@ -56601,7 +56601,7 @@ "deprecation_active": false, "display_args": ["--[no-]yapf-export"], "env_var": "PANTS_YAPF_EXPORT", - "help": "If true, export a virtual environment with yapf when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with yapf when running `/home/josh/work/scie-pants/dist/pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--yapf-export", "--no-yapf-export"], diff --git a/versioned_docs/version-2.14/reference/subsystems/autoflake.mdx b/versioned_docs/version-2.14/reference/subsystems/autoflake.mdx index 1555072aa..806db8030 100644 --- a/versioned_docs/version-2.14/reference/subsystems/autoflake.mdx +++ b/versioned_docs/version-2.14/reference/subsystems/autoflake.mdx @@ -25,7 +25,7 @@ Config section: `[autoflake]` default_repr={`False`} > -If true, don't use Autoflake when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +If true, don't use Autoflake when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. @@ -49,7 +49,7 @@ Arguments to pass directly to Autoflake, e.g. `--autoflake-args='--remove-all-un default_repr={`True`} > -If true, export a virtual environment with Autoflake when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`. +If true, export a virtual environment with Autoflake when running `/home/josh/work/scie-pants/dist/pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. @@ -107,7 +107,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=autoflake`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=autoflake`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.14/reference/subsystems/bandit.mdx b/versioned_docs/version-2.14/reference/subsystems/bandit.mdx index 15bee4168..14f54725c 100644 --- a/versioned_docs/version-2.14/reference/subsystems/bandit.mdx +++ b/versioned_docs/version-2.14/reference/subsystems/bandit.mdx @@ -25,7 +25,7 @@ Config section: `[bandit]` default_repr={`False`} > -If true, don't use Bandit when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +If true, don't use Bandit when running `/home/josh/work/scie-pants/dist/pants lint`. @@ -49,7 +49,7 @@ Arguments to pass directly to Bandit, e.g. `--bandit-args='--skip B101,B308 --co default_repr={`True`} > -If true, export a virtual environment with Bandit when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`. +If true, export a virtual environment with Bandit when running `/home/josh/work/scie-pants/dist/pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. @@ -95,7 +95,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=bandit`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=bandit`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.14/reference/subsystems/black.mdx b/versioned_docs/version-2.14/reference/subsystems/black.mdx index e2dddb9d6..6d9a45224 100644 --- a/versioned_docs/version-2.14/reference/subsystems/black.mdx +++ b/versioned_docs/version-2.14/reference/subsystems/black.mdx @@ -25,7 +25,7 @@ Config section: `[black]` default_repr={`False`} > -If true, don't use Black when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +If true, don't use Black when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. @@ -49,7 +49,7 @@ Arguments to pass directly to Black, e.g. `--black-args='--target-version=py37 - default_repr={`True`} > -If true, export a virtual environment with Black when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`. +If true, export a virtual environment with Black when running `/home/josh/work/scie-pants/dist/pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. @@ -107,7 +107,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=black`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=black`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.14/reference/subsystems/buf.mdx b/versioned_docs/version-2.14/reference/subsystems/buf.mdx index c77d3212f..a3da729ad 100644 --- a/versioned_docs/version-2.14/reference/subsystems/buf.mdx +++ b/versioned_docs/version-2.14/reference/subsystems/buf.mdx @@ -25,7 +25,7 @@ Config section: `[buf]` default_repr={`False`} > -If true, don't use Buf when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +If true, don't use Buf when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. @@ -37,7 +37,7 @@ If true, don't use Buf when running `/home/josh/work/scie-pants/dist/scie-p default_repr={`False`} > -If true, don't use Buf when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +If true, don't use Buf when running `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.14/reference/subsystems/buildifier.mdx b/versioned_docs/version-2.14/reference/subsystems/buildifier.mdx index 84c6bfec3..982a2ce07 100644 --- a/versioned_docs/version-2.14/reference/subsystems/buildifier.mdx +++ b/versioned_docs/version-2.14/reference/subsystems/buildifier.mdx @@ -32,7 +32,7 @@ Config section: `[buildifier]` default_repr={`False`} > -If true, don't use Buildifier when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt`. +If true, don't use Buildifier when running `/home/josh/work/scie-pants/dist/pants fmt`. diff --git a/versioned_docs/version-2.14/reference/subsystems/cli.mdx b/versioned_docs/version-2.14/reference/subsystems/cli.mdx index 3612faf24..8c2253b82 100644 --- a/versioned_docs/version-2.14/reference/subsystems/cli.mdx +++ b/versioned_docs/version-2.14/reference/subsystems/cli.mdx @@ -35,7 +35,7 @@ green = "fmt lint check" all-changed = "--changed-since=HEAD --changed-dependees=transitive" ``` -This would allow you to run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 green all-changed`, which is shorthand for `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt lint check --changed-since=HEAD --changed-dependees=transitive`. +This would allow you to run `/home/josh/work/scie-pants/dist/pants green all-changed`, which is shorthand for `/home/josh/work/scie-pants/dist/pants fmt lint check --changed-since=HEAD --changed-dependees=transitive`. Notice: this option must be placed in a config file (e.g. `pants.toml` or `pantsrc`) to have any effect. diff --git a/versioned_docs/version-2.14/reference/subsystems/coverage-py.mdx b/versioned_docs/version-2.14/reference/subsystems/coverage-py.mdx index 3d0633ca8..813b0a62d 100644 --- a/versioned_docs/version-2.14/reference/subsystems/coverage-py.mdx +++ b/versioned_docs/version-2.14/reference/subsystems/coverage-py.mdx @@ -130,7 +130,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=coverage-py`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=coverage-py`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.14/reference/subsystems/debugpy.mdx b/versioned_docs/version-2.14/reference/subsystems/debugpy.mdx index a89fb5b6b..2c2ce8ed6 100644 --- a/versioned_docs/version-2.14/reference/subsystems/debugpy.mdx +++ b/versioned_docs/version-2.14/reference/subsystems/debugpy.mdx @@ -81,7 +81,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=debugpy`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=debugpy`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.14/reference/subsystems/docformatter.mdx b/versioned_docs/version-2.14/reference/subsystems/docformatter.mdx index 231293039..d17c6e530 100644 --- a/versioned_docs/version-2.14/reference/subsystems/docformatter.mdx +++ b/versioned_docs/version-2.14/reference/subsystems/docformatter.mdx @@ -25,7 +25,7 @@ Config section: `[docformatter]` default_repr={`False`} > -If true, don't use docformatter when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +If true, don't use docformatter when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. @@ -49,7 +49,7 @@ Arguments to pass directly to docformatter, e.g. `--docformatter-args='--wrap-su default_repr={`True`} > -If true, export a virtual environment with docformatter when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`. +If true, export a virtual environment with docformatter when running `/home/josh/work/scie-pants/dist/pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. @@ -107,7 +107,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=docformatter`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=docformatter`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.14/reference/subsystems/docker.mdx b/versioned_docs/version-2.14/reference/subsystems/docker.mdx index 689815dc2..52b9434ff 100644 --- a/versioned_docs/version-2.14/reference/subsystems/docker.mdx +++ b/versioned_docs/version-2.14/reference/subsystems/docker.mdx @@ -166,7 +166,7 @@ Additional arguments to use for `docker run` invocations. Example: ``` -$ /home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 run --docker-run-args="-p 127.0.0.1:80:8080/tcp --name demo" src/example:image -- [image entrypoint args] +$ /home/josh/work/scie-pants/dist/pants run --docker-run-args="-p 127.0.0.1:80:8080/tcp --name demo" src/example:image -- [image entrypoint args] ``` To provide the top-level options to the `docker` client, use `[docker].env_vars` to configure the [Environment variables](https://docs.docker.com/engine/reference/commandline/cli/#environment-variables) as appropriate. diff --git a/versioned_docs/version-2.14/reference/subsystems/dockerfile-parser.mdx b/versioned_docs/version-2.14/reference/subsystems/dockerfile-parser.mdx index 951e1197a..aaf40ec56 100644 --- a/versioned_docs/version-2.14/reference/subsystems/dockerfile-parser.mdx +++ b/versioned_docs/version-2.14/reference/subsystems/dockerfile-parser.mdx @@ -71,7 +71,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=dockerfile-parser`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=dockerfile-parser`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.14/reference/subsystems/flake8.mdx b/versioned_docs/version-2.14/reference/subsystems/flake8.mdx index b53494939..ae0063c06 100644 --- a/versioned_docs/version-2.14/reference/subsystems/flake8.mdx +++ b/versioned_docs/version-2.14/reference/subsystems/flake8.mdx @@ -25,7 +25,7 @@ Config section: `[flake8]` default_repr={`False`} > -If true, don't use Flake8 when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +If true, don't use Flake8 when running `/home/josh/work/scie-pants/dist/pants lint`. @@ -49,7 +49,7 @@ Arguments to pass directly to Flake8, e.g. `--flake8-args='--ignore E123,W456 -- default_repr={`True`} > -If true, export a virtual environment with Flake8 when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`. +If true, export a virtual environment with Flake8 when running `/home/josh/work/scie-pants/dist/pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. @@ -95,7 +95,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=flake8`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=flake8`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.14/reference/subsystems/gofmt.mdx b/versioned_docs/version-2.14/reference/subsystems/gofmt.mdx index 1114d4e84..deddbc716 100644 --- a/versioned_docs/version-2.14/reference/subsystems/gofmt.mdx +++ b/versioned_docs/version-2.14/reference/subsystems/gofmt.mdx @@ -25,7 +25,7 @@ Config section: `[gofmt]` default_repr={`False`} > -If true, don't use gofmt when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +If true, don't use gofmt when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.14/reference/subsystems/google-java-format.mdx b/versioned_docs/version-2.14/reference/subsystems/google-java-format.mdx index be19c0e98..1183a9bb2 100644 --- a/versioned_docs/version-2.14/reference/subsystems/google-java-format.mdx +++ b/versioned_docs/version-2.14/reference/subsystems/google-java-format.mdx @@ -25,7 +25,7 @@ Config section: `[google-java-format]` default_repr={`False`} > -If true, don't use Google Java Format when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +If true, don't use Google Java Format when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. @@ -79,7 +79,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/java/lint/google_java_format/google_java_format.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=google-java-format`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=google-java-format`. diff --git a/versioned_docs/version-2.14/reference/subsystems/hadolint.mdx b/versioned_docs/version-2.14/reference/subsystems/hadolint.mdx index 8f19ad2c1..def28665d 100644 --- a/versioned_docs/version-2.14/reference/subsystems/hadolint.mdx +++ b/versioned_docs/version-2.14/reference/subsystems/hadolint.mdx @@ -25,7 +25,7 @@ Config section: `[hadolint]` default_repr={`False`} > -If true, don't use Hadolint when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +If true, don't use Hadolint when running `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.14/reference/subsystems/helm-k8s-parser.mdx b/versioned_docs/version-2.14/reference/subsystems/helm-k8s-parser.mdx index b631f161d..4a1a989b3 100644 --- a/versioned_docs/version-2.14/reference/subsystems/helm-k8s-parser.mdx +++ b/versioned_docs/version-2.14/reference/subsystems/helm-k8s-parser.mdx @@ -71,7 +71,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=helm-k8s-parser`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=helm-k8s-parser`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.14/reference/subsystems/helm-post-renderer.mdx b/versioned_docs/version-2.14/reference/subsystems/helm-post-renderer.mdx index 3dab8d05f..3c9d1fd75 100644 --- a/versioned_docs/version-2.14/reference/subsystems/helm-post-renderer.mdx +++ b/versioned_docs/version-2.14/reference/subsystems/helm-post-renderer.mdx @@ -71,7 +71,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=helm-post-renderer`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=helm-post-renderer`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.14/reference/subsystems/ipython.mdx b/versioned_docs/version-2.14/reference/subsystems/ipython.mdx index ae6dfe9ba..e2f2c0a04 100644 --- a/versioned_docs/version-2.14/reference/subsystems/ipython.mdx +++ b/versioned_docs/version-2.14/reference/subsystems/ipython.mdx @@ -59,7 +59,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=ipython`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=ipython`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.14/reference/subsystems/isort.mdx b/versioned_docs/version-2.14/reference/subsystems/isort.mdx index 7afa87626..9be2b0aba 100644 --- a/versioned_docs/version-2.14/reference/subsystems/isort.mdx +++ b/versioned_docs/version-2.14/reference/subsystems/isort.mdx @@ -25,7 +25,7 @@ Config section: `[isort]` default_repr={`False`} > -If true, don't use isort when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +If true, don't use isort when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. @@ -49,7 +49,7 @@ Arguments to pass directly to isort, e.g. `--isort-args='--case-sensitive --trai default_repr={`True`} > -If true, export a virtual environment with isort when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`. +If true, export a virtual environment with isort when running `/home/josh/work/scie-pants/dist/pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. @@ -107,7 +107,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=isort`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=isort`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.14/reference/subsystems/junit.mdx b/versioned_docs/version-2.14/reference/subsystems/junit.mdx index 8cf5e3c20..179c2ab44 100644 --- a/versioned_docs/version-2.14/reference/subsystems/junit.mdx +++ b/versioned_docs/version-2.14/reference/subsystems/junit.mdx @@ -67,7 +67,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/jvm/test/junit.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=junit`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=junit`. diff --git a/versioned_docs/version-2.14/reference/subsystems/ktlint.mdx b/versioned_docs/version-2.14/reference/subsystems/ktlint.mdx index 52abeb56f..43c9dcbe2 100644 --- a/versioned_docs/version-2.14/reference/subsystems/ktlint.mdx +++ b/versioned_docs/version-2.14/reference/subsystems/ktlint.mdx @@ -25,7 +25,7 @@ Config section: `[ktlint]` default_repr={`False`} > -If true, don't use Ktlint when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +If true, don't use Ktlint when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. @@ -67,7 +67,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/kotlin/lint/ktlint/ktlint.lock for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=ktlint`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=ktlint`. diff --git a/versioned_docs/version-2.14/reference/subsystems/lambdex.mdx b/versioned_docs/version-2.14/reference/subsystems/lambdex.mdx index 21f691dc7..6424e82e4 100644 --- a/versioned_docs/version-2.14/reference/subsystems/lambdex.mdx +++ b/versioned_docs/version-2.14/reference/subsystems/lambdex.mdx @@ -71,7 +71,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=lambdex`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=lambdex`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.14/reference/subsystems/mypy-protobuf.mdx b/versioned_docs/version-2.14/reference/subsystems/mypy-protobuf.mdx index f44116f90..001578b73 100644 --- a/versioned_docs/version-2.14/reference/subsystems/mypy-protobuf.mdx +++ b/versioned_docs/version-2.14/reference/subsystems/mypy-protobuf.mdx @@ -71,7 +71,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=mypy-protobuf`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=mypy-protobuf`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.14/reference/subsystems/mypy.mdx b/versioned_docs/version-2.14/reference/subsystems/mypy.mdx index 1f122cf2d..cec94c1f3 100644 --- a/versioned_docs/version-2.14/reference/subsystems/mypy.mdx +++ b/versioned_docs/version-2.14/reference/subsystems/mypy.mdx @@ -25,7 +25,7 @@ Config section: `[mypy]` default_repr={`False`} > -If true, don't use MyPy when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 check`. +If true, don't use MyPy when running `/home/josh/work/scie-pants/dist/pants check`. @@ -49,7 +49,7 @@ Arguments to pass directly to MyPy, e.g. `--mypy-args='--python-version 3.7 --di default_repr={`True`} > -If true, export a virtual environment with MyPy when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`. +If true, export a virtual environment with MyPy when running `/home/josh/work/scie-pants/dist/pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. @@ -107,7 +107,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=mypy`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=mypy`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. @@ -211,7 +211,7 @@ Path to a lockfile for the option `[mypy].extra_type_stubs`. Set to the string `` to opt out of using a lockfile. We do not recommend this if you use `[mypy].extra_type_stubs`, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=mypy-extra-type-stubs`. +To use a lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=mypy-extra-type-stubs`. diff --git a/versioned_docs/version-2.14/reference/subsystems/poetry.mdx b/versioned_docs/version-2.14/reference/subsystems/poetry.mdx index d42a219a1..f54ffba92 100644 --- a/versioned_docs/version-2.14/reference/subsystems/poetry.mdx +++ b/versioned_docs/version-2.14/reference/subsystems/poetry.mdx @@ -71,7 +71,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=poetry`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=poetry`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.14/reference/subsystems/protobuf-java-grpc.mdx b/versioned_docs/version-2.14/reference/subsystems/protobuf-java-grpc.mdx index 762497e64..e5c10ad1d 100644 --- a/versioned_docs/version-2.14/reference/subsystems/protobuf-java-grpc.mdx +++ b/versioned_docs/version-2.14/reference/subsystems/protobuf-java-grpc.mdx @@ -57,7 +57,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/codegen/protobuf/java/grpc-java.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=protobuf-java-grpc`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=protobuf-java-grpc`. diff --git a/versioned_docs/version-2.14/reference/subsystems/pylint.mdx b/versioned_docs/version-2.14/reference/subsystems/pylint.mdx index 324acee2a..506781f06 100644 --- a/versioned_docs/version-2.14/reference/subsystems/pylint.mdx +++ b/versioned_docs/version-2.14/reference/subsystems/pylint.mdx @@ -25,7 +25,7 @@ Config section: `[pylint]` default_repr={`False`} > -If true, don't use Pylint when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +If true, don't use Pylint when running `/home/josh/work/scie-pants/dist/pants lint`. @@ -49,7 +49,7 @@ Arguments to pass directly to Pylint, e.g. `--pylint-args='--ignore=foo.py,bar.p default_repr={`True`} > -If true, export a virtual environment with Pylint when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`. +If true, export a virtual environment with Pylint when running `/home/josh/work/scie-pants/dist/pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. @@ -95,7 +95,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=pylint`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=pylint`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.14/reference/subsystems/pyoxidizer.mdx b/versioned_docs/version-2.14/reference/subsystems/pyoxidizer.mdx index 5a4b5105c..90e5da855 100644 --- a/versioned_docs/version-2.14/reference/subsystems/pyoxidizer.mdx +++ b/versioned_docs/version-2.14/reference/subsystems/pyoxidizer.mdx @@ -83,7 +83,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=pyoxidizer`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=pyoxidizer`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.14/reference/subsystems/pytest.mdx b/versioned_docs/version-2.14/reference/subsystems/pytest.mdx index 5b864d3a8..f52bbcf39 100644 --- a/versioned_docs/version-2.14/reference/subsystems/pytest.mdx +++ b/versioned_docs/version-2.14/reference/subsystems/pytest.mdx @@ -51,7 +51,7 @@ NOTE: Enabling `pytest-xdist` can cause high-level scoped fixtures (for example default_repr={`True`} > -If true, export a virtual environment with Pytest when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`. +If true, export a virtual environment with Pytest when running `/home/josh/work/scie-pants/dist/pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. @@ -97,7 +97,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=pytest`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=pytest`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.14/reference/subsystems/python-infer.mdx b/versioned_docs/version-2.14/reference/subsystems/python-infer.mdx index 3d78de082..5f89c9c2a 100644 --- a/versioned_docs/version-2.14/reference/subsystems/python-infer.mdx +++ b/versioned_docs/version-2.14/reference/subsystems/python-infer.mdx @@ -94,7 +94,7 @@ If --assets is True, treat valid-looking strings with at least this many forward Infer a target's dependencies on any `__init__.py` files in the packages it is located in (recursively upward in the directory structure). -Even if this is set to `never` or `content_only`, Pants will still always include any ancestor `__init__.py` files in the sandbox. Only, they will not be "proper" dependencies, e.g. they will not show up in `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` and their own dependencies will not be used. +Even if this is set to `never` or `content_only`, Pants will still always include any ancestor `__init__.py` files in the sandbox. Only, they will not be "proper" dependencies, e.g. they will not show up in `/home/josh/work/scie-pants/dist/pants dependencies` and their own dependencies will not be used. By default, Pants only adds a "proper" dependency if there is content in the `__init__.py` file. This makes sure that dependencies are added when likely necessary to build, while also avoiding adding unnecessary dependencies. While accurate, those unnecessary dependencies can complicate setting metadata like the `interpreter_constraints` and `resolve` fields. diff --git a/versioned_docs/version-2.14/reference/subsystems/python.mdx b/versioned_docs/version-2.14/reference/subsystems/python.mdx index f26ffca4b..7ffee953f 100644 --- a/versioned_docs/version-2.14/reference/subsystems/python.mdx +++ b/versioned_docs/version-2.14/reference/subsystems/python.mdx @@ -99,14 +99,14 @@ A mapping of logical names to lockfile paths used in your project. Many organizations only need a single resolve for their whole project, which is a good default and often the simplest thing to do. However, you may need multiple resolves, such as if you use two conflicting versions of a requirement in your repository. -If you only need a single resolve, run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles` to generate the lockfile. +If you only need a single resolve, run `/home/josh/work/scie-pants/dist/pants generate-lockfiles` to generate the lockfile. If you need multiple resolves: 1. Via this option, define multiple resolve names and their lockfile paths. The names should be meaningful to your repository, such as `data-science` or `pants-plugins`. 2. Set the default with `[python].default_resolve`. 3. Update your `python_requirement` targets with the `resolve` field to declare which resolve they should be available in. They default to `[python].default_resolve`, so you only need to update targets that you want in non-default resolves. (Often you'll set this via the `python_requirements` or `poetry_requirements` target generators) -4. Run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles` to generate the lockfiles. If the results aren't what you'd expect, adjust the prior step. +4. Run `/home/josh/work/scie-pants/dist/pants generate-lockfiles` to generate the lockfiles. If the results aren't what you'd expect, adjust the prior step. 5. Update any targets like `python_source` / `python_sources`, `python_test` / `python_tests`, and `pex_binary` which need to set a non-default resolve with the `resolve` field. If a target can work with multiple resolves, you can either use the `parametrize` mechanism or manually create a distinct target per resolve. See https://www.pantsbuild.org/v2.14/docs/targets for information about `parametrize`. @@ -370,7 +370,7 @@ If set, and if running on MacOS Big Sur, use macosx_10_16 as the platform when b one_of='pex, poetry' default_repr={`pex`} removal_version='2.15.0.dev0' - removal_hint={'Pants will soon only support generating lockfiles via the Pex format, as Poetry-generated lockfiles mismatch with Pants\'s pip-based approach.

If you do not want to use Pex lockfiles, you will still be able to manually generate lockfiles, e.g. by manually running `poetry export --dev` on your `poetry.lock`. See https://www.pantsbuild.org/v2.14/docs/python-third-party-dependencies#manually-generating-lockfiles for more information.

While Pex generates locks in a proprietary JSON format, you can use the `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export` goal for Pants to create a virtual environment for interoperability with tools like IDEs.

Please open a GitHub issue or reach out on Slack if you encounter issues while migrating: https://www.pantsbuild.org/v2.14/docs/getting-help

Tip: you can incrementally migrate one lockfile at-a-time by dynamically setting the option `--python-lockfile-generator`. For example:

/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --python-lockfile-generator=pex generate-lockfiles --resolve=black --resolve=isort
/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --python-lockfile-generator=poetry generate-lockfiles --resolve=python-default'} + removal_hint={'Pants will soon only support generating lockfiles via the Pex format, as Poetry-generated lockfiles mismatch with Pants\'s pip-based approach.

If you do not want to use Pex lockfiles, you will still be able to manually generate lockfiles, e.g. by manually running `poetry export --dev` on your `poetry.lock`. See https://www.pantsbuild.org/v2.14/docs/python-third-party-dependencies#manually-generating-lockfiles for more information.

While Pex generates locks in a proprietary JSON format, you can use the `/home/josh/work/scie-pants/dist/pants export` goal for Pants to create a virtual environment for interoperability with tools like IDEs.

Please open a GitHub issue or reach out on Slack if you encounter issues while migrating: https://www.pantsbuild.org/v2.14/docs/getting-help

Tip: you can incrementally migrate one lockfile at-a-time by dynamically setting the option `--python-lockfile-generator`. For example:

/home/josh/work/scie-pants/dist/pants --python-lockfile-generator=pex generate-lockfiles --resolve=black --resolve=isort
/home/josh/work/scie-pants/dist/pants --python-lockfile-generator=poetry generate-lockfiles --resolve=python-default'} > Whether to use Pex or Poetry with the `generate-lockfiles` goal. @@ -389,7 +389,7 @@ Finally, installing from a Poetry-generated lockfile is slower than installing f However, Pex lockfile generation is a new feature. Given how vast the Python packaging ecosystem is, it is possible you may experience edge cases / bugs we haven't yet covered. Bug reports are appreciated! https://github.com/pantsbuild/pants/issues/new/choose -Note that while Pex generates locks in a proprietary JSON format, you can use the `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export` goal for Pants to create a virtual environment for interoperability with tools like IDEs. +Note that while Pex generates locks in a proprietary JSON format, you can use the `/home/josh/work/scie-pants/dist/pants export` goal for Pants to create a virtual environment for interoperability with tools like IDEs. @@ -400,7 +400,7 @@ Note that while Pex generates locks in a proprietary JSON format, you can use th env_repr='PANTS_PYTHON_REQUIREMENT_CONSTRAINTS' default_repr={`None`} removal_version='3.0.0.dev0' - removal_hint={'We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.

To migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles`.'} + removal_hint={'We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.

To migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `/home/josh/work/scie-pants/dist/pants generate-lockfiles`.'} > When resolving third-party requirements for your own code (vs. tools you run), use this constraints file to determine which versions to use. @@ -420,7 +420,7 @@ This only applies when resolving user requirements, rather than tools you run li env_repr='PANTS_PYTHON_RESOLVE_ALL_CONSTRAINTS' default_repr={`True`} removal_version='3.0.0.dev0' - removal_hint={'We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.

To migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles`.'} + removal_hint={'We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.

To migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `/home/josh/work/scie-pants/dist/pants generate-lockfiles`.'} > (Only relevant when using `[python].requirement_constraints.`) If enabled, when resolving requirements, Pants will first resolve your entire constraints file as a single global resolve. Then, if the code uses a subset of your constraints file, Pants will extract the relevant requirements from that global resolve so that only what's actually needed gets used. If disabled, Pants will not use a global resolve and will resolve each subset of your requirements independently. diff --git a/versioned_docs/version-2.14/reference/subsystems/pyupgrade.mdx b/versioned_docs/version-2.14/reference/subsystems/pyupgrade.mdx index 40c5cfdde..d873f5133 100644 --- a/versioned_docs/version-2.14/reference/subsystems/pyupgrade.mdx +++ b/versioned_docs/version-2.14/reference/subsystems/pyupgrade.mdx @@ -25,7 +25,7 @@ Config section: `[pyupgrade]` default_repr={`False`} > -If true, don't use pyupgrade when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +If true, don't use pyupgrade when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. @@ -49,7 +49,7 @@ Arguments to pass directly to pyupgrade, e.g. `--pyupgrade-args='--py39-plus --k default_repr={`True`} > -If true, export a virtual environment with pyupgrade when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`. +If true, export a virtual environment with pyupgrade when running `/home/josh/work/scie-pants/dist/pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. @@ -107,7 +107,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=pyupgrade`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=pyupgrade`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.14/reference/subsystems/scalafmt.mdx b/versioned_docs/version-2.14/reference/subsystems/scalafmt.mdx index d1d203bfe..90fe78f12 100644 --- a/versioned_docs/version-2.14/reference/subsystems/scalafmt.mdx +++ b/versioned_docs/version-2.14/reference/subsystems/scalafmt.mdx @@ -25,7 +25,7 @@ Config section: `[scalafmt]` default_repr={`False`} > -If true, don't use scalafmt when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +If true, don't use scalafmt when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. @@ -67,7 +67,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/scala/lint/scalafmt/scalafmt.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalafmt`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=scalafmt`. diff --git a/versioned_docs/version-2.14/reference/subsystems/scalapb.mdx b/versioned_docs/version-2.14/reference/subsystems/scalapb.mdx index cd23a4710..995df3fb8 100644 --- a/versioned_docs/version-2.14/reference/subsystems/scalapb.mdx +++ b/versioned_docs/version-2.14/reference/subsystems/scalapb.mdx @@ -69,7 +69,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/codegen/protobuf/scala/scalapbc.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalapb`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=scalapb`. diff --git a/versioned_docs/version-2.14/reference/subsystems/scalatest.mdx b/versioned_docs/version-2.14/reference/subsystems/scalatest.mdx index b3139b120..9d9cf2423 100644 --- a/versioned_docs/version-2.14/reference/subsystems/scalatest.mdx +++ b/versioned_docs/version-2.14/reference/subsystems/scalatest.mdx @@ -69,7 +69,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.14.2/src/python/pants/backend/scala/subsystems/scalatest.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalatest`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=scalatest`. diff --git a/versioned_docs/version-2.14/reference/subsystems/setuptools-scm.mdx b/versioned_docs/version-2.14/reference/subsystems/setuptools-scm.mdx index bd46b25a1..e77a08515 100644 --- a/versioned_docs/version-2.14/reference/subsystems/setuptools-scm.mdx +++ b/versioned_docs/version-2.14/reference/subsystems/setuptools-scm.mdx @@ -71,7 +71,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=setuptools-scm`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=setuptools-scm`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.14/reference/subsystems/setuptools.mdx b/versioned_docs/version-2.14/reference/subsystems/setuptools.mdx index f091b5e2d..f9d3d9630 100644 --- a/versioned_docs/version-2.14/reference/subsystems/setuptools.mdx +++ b/versioned_docs/version-2.14/reference/subsystems/setuptools.mdx @@ -59,7 +59,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=setuptools`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=setuptools`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.14/reference/subsystems/shellcheck.mdx b/versioned_docs/version-2.14/reference/subsystems/shellcheck.mdx index b40571393..fa1c06148 100644 --- a/versioned_docs/version-2.14/reference/subsystems/shellcheck.mdx +++ b/versioned_docs/version-2.14/reference/subsystems/shellcheck.mdx @@ -25,7 +25,7 @@ Config section: `[shellcheck]` default_repr={`False`} > -If true, don't use Shellcheck when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +If true, don't use Shellcheck when running `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.14/reference/subsystems/shfmt.mdx b/versioned_docs/version-2.14/reference/subsystems/shfmt.mdx index 8135f0031..7ddb7ac39 100644 --- a/versioned_docs/version-2.14/reference/subsystems/shfmt.mdx +++ b/versioned_docs/version-2.14/reference/subsystems/shfmt.mdx @@ -25,7 +25,7 @@ Config section: `[shfmt]` default_repr={`False`} > -If true, don't use shfmt when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +If true, don't use shfmt when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.14/reference/subsystems/terraform-fmt.mdx b/versioned_docs/version-2.14/reference/subsystems/terraform-fmt.mdx index a846d1f40..6082dec1a 100644 --- a/versioned_docs/version-2.14/reference/subsystems/terraform-fmt.mdx +++ b/versioned_docs/version-2.14/reference/subsystems/terraform-fmt.mdx @@ -25,7 +25,7 @@ Config section: `[terraform-fmt]` default_repr={`False`} > -If true, don't use `terraform fmt` when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +If true, don't use `terraform fmt` when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.14/reference/subsystems/terraform-hcl2-parser.mdx b/versioned_docs/version-2.14/reference/subsystems/terraform-hcl2-parser.mdx index 143537e2d..08f2dc408 100644 --- a/versioned_docs/version-2.14/reference/subsystems/terraform-hcl2-parser.mdx +++ b/versioned_docs/version-2.14/reference/subsystems/terraform-hcl2-parser.mdx @@ -71,7 +71,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=terraform-hcl2-parser`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=terraform-hcl2-parser`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.14/reference/subsystems/terraform-validate.mdx b/versioned_docs/version-2.14/reference/subsystems/terraform-validate.mdx index 05288ff5d..8b679e12f 100644 --- a/versioned_docs/version-2.14/reference/subsystems/terraform-validate.mdx +++ b/versioned_docs/version-2.14/reference/subsystems/terraform-validate.mdx @@ -25,7 +25,7 @@ Config section: `[terraform-validate]` default_repr={`False`} > -If true, don't use `terraform validate` when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 check`. +If true, don't use `terraform validate` when running `/home/josh/work/scie-pants/dist/pants check`. diff --git a/versioned_docs/version-2.14/reference/subsystems/twine.mdx b/versioned_docs/version-2.14/reference/subsystems/twine.mdx index 5c0c289df..26018c5bf 100644 --- a/versioned_docs/version-2.14/reference/subsystems/twine.mdx +++ b/versioned_docs/version-2.14/reference/subsystems/twine.mdx @@ -25,7 +25,7 @@ Config section: `[twine]` default_repr={`False`} > -If true, don't use Twine when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 publish`. +If true, don't use Twine when running `/home/josh/work/scie-pants/dist/pants publish`. @@ -93,7 +93,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=twine`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=twine`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.14/reference/subsystems/yapf.mdx b/versioned_docs/version-2.14/reference/subsystems/yapf.mdx index 3d671ec32..59c3004f0 100644 --- a/versioned_docs/version-2.14/reference/subsystems/yapf.mdx +++ b/versioned_docs/version-2.14/reference/subsystems/yapf.mdx @@ -25,7 +25,7 @@ Config section: `[yapf]` default_repr={`False`} > -If true, don't use yapf when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +If true, don't use yapf when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. @@ -51,7 +51,7 @@ Certain arguments, specifically `--recursive`, `--in-place`, and `--parallel`, w default_repr={`True`} > -If true, export a virtual environment with yapf when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`. +If true, export a virtual environment with yapf when running `/home/josh/work/scie-pants/dist/pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. @@ -109,7 +109,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=yapf`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=yapf`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.14/reference/targets/archive.mdx b/versioned_docs/version-2.14/reference/targets/archive.mdx index eee2b5712..801685458 100644 --- a/versioned_docs/version-2.14/reference/targets/archive.mdx +++ b/versioned_docs/version-2.14/reference/targets/archive.mdx @@ -24,7 +24,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -52,7 +52,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. @@ -65,11 +65,11 @@ Warning: setting this value risks naming collisions with other package targets y default_repr={`None`} > -Addresses to any targets that can be built with `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, e.g. `["project:app"]`. +Addresses to any targets that can be built with `/home/josh/work/scie-pants/dist/pants package`, e.g. `["project:app"]`. -Pants will build the assets as if you had run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`. It will include the results in your archive using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). +Pants will build the assets as if you had run `/home/josh/work/scie-pants/dist/pants package`. It will include the results in your archive using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). -You can include anything that can be built by `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or even another `archive`. +You can include anything that can be built by `/home/josh/work/scie-pants/dist/pants package`, e.g. a `pex_binary`, `python_awslambda`, or even another `archive`. diff --git a/versioned_docs/version-2.14/reference/targets/deploy_jar.mdx b/versioned_docs/version-2.14/reference/targets/deploy_jar.mdx index 4197bb11a..03e3d65f2 100644 --- a/versioned_docs/version-2.14/reference/targets/deploy_jar.mdx +++ b/versioned_docs/version-2.14/reference/targets/deploy_jar.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.experimental.java` @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -52,9 +52,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -73,7 +73,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. diff --git a/versioned_docs/version-2.14/reference/targets/docker_image.mdx b/versioned_docs/version-2.14/reference/targets/docker_image.mdx index b03bc4cd2..041c07a22 100644 --- a/versioned_docs/version-2.14/reference/targets/docker_image.mdx +++ b/versioned_docs/version-2.14/reference/targets/docker_image.mdx @@ -39,7 +39,7 @@ Backend: `pants.backend.docker` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -52,7 +52,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -78,9 +78,9 @@ Use `[docker].build_args` to set default build args for all images. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -277,7 +277,7 @@ See [Docker documentation](https://docs.docker.com/develop/develop-images/build_ default_repr={`False`} > -If set to true, do not push this image to registries when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 publish`. +If set to true, do not push this image to registries when running `/home/josh/work/scie-pants/dist/pants publish`. diff --git a/versioned_docs/version-2.14/reference/targets/experimental_run_shell_command.mdx b/versioned_docs/version-2.14/reference/targets/experimental_run_shell_command.mdx index 6fc5bfd7d..0d8d50638 100644 --- a/versioned_docs/version-2.14/reference/targets/experimental_run_shell_command.mdx +++ b/versioned_docs/version-2.14/reference/targets/experimental_run_shell_command.mdx @@ -37,7 +37,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -50,7 +50,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -63,9 +63,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.14/reference/targets/experimental_shell_command.mdx b/versioned_docs/version-2.14/reference/targets/experimental_shell_command.mdx index 1aafcce64..c54023389 100644 --- a/versioned_docs/version-2.14/reference/targets/experimental_shell_command.mdx +++ b/versioned_docs/version-2.14/reference/targets/experimental_shell_command.mdx @@ -41,7 +41,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -54,7 +54,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -67,9 +67,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.14/reference/targets/file.mdx b/versioned_docs/version-2.14/reference/targets/file.mdx index cc2295b31..5af52140f 100644 --- a/versioned_docs/version-2.14/reference/targets/file.mdx +++ b/versioned_docs/version-2.14/reference/targets/file.mdx @@ -26,7 +26,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -52,9 +52,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.14/reference/targets/files.mdx b/versioned_docs/version-2.14/reference/targets/files.mdx index ff494ee88..50547451b 100644 --- a/versioned_docs/version-2.14/reference/targets/files.mdx +++ b/versioned_docs/version-2.14/reference/targets/files.mdx @@ -24,7 +24,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -91,9 +91,9 @@ You can specify the same file name in multiple keys, so long as you don't o Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.14/reference/targets/go_binary.mdx b/versioned_docs/version-2.14/reference/targets/go_binary.mdx index 3f172d7d0..26351b1ff 100644 --- a/versioned_docs/version-2.14/reference/targets/go_binary.mdx +++ b/versioned_docs/version-2.14/reference/targets/go_binary.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.go` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -52,7 +52,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. diff --git a/versioned_docs/version-2.14/reference/targets/go_mod.mdx b/versioned_docs/version-2.14/reference/targets/go_mod.mdx index 605db3545..caeac0e75 100644 --- a/versioned_docs/version-2.14/reference/targets/go_mod.mdx +++ b/versioned_docs/version-2.14/reference/targets/go_mod.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.go` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.14/reference/targets/go_package.mdx b/versioned_docs/version-2.14/reference/targets/go_package.mdx index 343f65f26..125f218d3 100644 --- a/versioned_docs/version-2.14/reference/targets/go_package.mdx +++ b/versioned_docs/version-2.14/reference/targets/go_package.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.experimental.go` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -52,9 +52,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.14/reference/targets/go_third_party_package.mdx b/versioned_docs/version-2.14/reference/targets/go_third_party_package.mdx index de01c00ae..b4cf0c75f 100644 --- a/versioned_docs/version-2.14/reference/targets/go_third_party_package.mdx +++ b/versioned_docs/version-2.14/reference/targets/go_third_party_package.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.go` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -54,9 +54,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.14/reference/targets/helm_artifact.mdx b/versioned_docs/version-2.14/reference/targets/helm_artifact.mdx index 62850ffdf..33546af67 100644 --- a/versioned_docs/version-2.14/reference/targets/helm_artifact.mdx +++ b/versioned_docs/version-2.14/reference/targets/helm_artifact.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.helm` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.14/reference/targets/helm_chart.mdx b/versioned_docs/version-2.14/reference/targets/helm_chart.mdx index 102da2b17..0cb317b0a 100644 --- a/versioned_docs/version-2.14/reference/targets/helm_chart.mdx +++ b/versioned_docs/version-2.14/reference/targets/helm_chart.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.helm` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -76,9 +76,9 @@ Example: `sources=['values.yaml', 'templates/*.yaml', '!values_ignore.yaml']` Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -99,7 +99,7 @@ If undefined, this will use the path to the BUILD file, For example, `src/charts Regardless of whether you use the default or set this field, the path will end with Helms's file format of `-.tgz`, where `chart_name` and `chart_version` are the values extracted from the Chart.yaml file. So, using the default for this field, the target `src/charts/mychart:tgt_name` might have a final path like `src.charts.mychart/tgt_name/mychart-0.1.0.tgz`. -When running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. @@ -170,7 +170,7 @@ The above example shows two valid `registry` options: using an alias to a config default_repr={`False`} > -If set to true, do not push this Helm chart to registries when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 publish`. +If set to true, do not push this Helm chart to registries when running `/home/josh/work/scie-pants/dist/pants publish`. @@ -181,7 +181,7 @@ If set to true, do not push this Helm chart to registries when running `/home/jo default_repr={`False`} > -If set to true, do not run any linting in this Helm chart when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +If set to true, do not run any linting in this Helm chart when running `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.14/reference/targets/helm_deployment.mdx b/versioned_docs/version-2.14/reference/targets/helm_deployment.mdx index 5e904e3d0..d8210ef5b 100644 --- a/versioned_docs/version-2.14/reference/targets/helm_deployment.mdx +++ b/versioned_docs/version-2.14/reference/targets/helm_deployment.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.helm` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -61,9 +61,9 @@ Name of the release used in the deployment. If not set, the target name will be Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.14/reference/targets/helm_unittest_test.mdx b/versioned_docs/version-2.14/reference/targets/helm_unittest_test.mdx index 3c5737e47..749014609 100644 --- a/versioned_docs/version-2.14/reference/targets/helm_unittest_test.mdx +++ b/versioned_docs/version-2.14/reference/targets/helm_unittest_test.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.helm` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -63,9 +63,9 @@ Path is relative to the BUILD file's directory, e.g. `source='example.ext'` Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.14/reference/targets/helm_unittest_tests.mdx b/versioned_docs/version-2.14/reference/targets/helm_unittest_tests.mdx index c37b98ea9..9f4a4362e 100644 --- a/versioned_docs/version-2.14/reference/targets/helm_unittest_tests.mdx +++ b/versioned_docs/version-2.14/reference/targets/helm_unittest_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.helm` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -65,9 +65,9 @@ Example: `sources=['*_test.yaml', '!ignore_test.yaml']` Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -109,9 +109,9 @@ You can specify the same file name in multiple keys, so long as you don't o Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.14/reference/targets/java_source.mdx b/versioned_docs/version-2.14/reference/targets/java_source.mdx index c74572ff5..8f6643ff9 100644 --- a/versioned_docs/version-2.14/reference/targets/java_source.mdx +++ b/versioned_docs/version-2.14/reference/targets/java_source.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.java` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.14/reference/targets/java_sources.mdx b/versioned_docs/version-2.14/reference/targets/java_sources.mdx index c8ab83596..c74b4958c 100644 --- a/versioned_docs/version-2.14/reference/targets/java_sources.mdx +++ b/versioned_docs/version-2.14/reference/targets/java_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.java` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -77,9 +77,9 @@ If true, don't run Google Java Format on this target's code. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.14/reference/targets/junit_test.mdx b/versioned_docs/version-2.14/reference/targets/junit_test.mdx index a29cf39da..877e6bfb4 100644 --- a/versioned_docs/version-2.14/reference/targets/junit_test.mdx +++ b/versioned_docs/version-2.14/reference/targets/junit_test.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.java` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -91,9 +91,9 @@ This will be merged with and override values from `[test].extra_env_vars`. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.14/reference/targets/junit_tests.mdx b/versioned_docs/version-2.14/reference/targets/junit_tests.mdx index 444c43a61..5c70a772a 100644 --- a/versioned_docs/version-2.14/reference/targets/junit_tests.mdx +++ b/versioned_docs/version-2.14/reference/targets/junit_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.java` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -93,9 +93,9 @@ This will be merged with and override values from `[test].extra_env_vars`. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.14/reference/targets/jvm_artifact.mdx b/versioned_docs/version-2.14/reference/targets/jvm_artifact.mdx index 93f88ab0d..38392e7ea 100644 --- a/versioned_docs/version-2.14/reference/targets/jvm_artifact.mdx +++ b/versioned_docs/version-2.14/reference/targets/jvm_artifact.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.java` @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.14/reference/targets/jvm_war.mdx b/versioned_docs/version-2.14/reference/targets/jvm_war.mdx index d44642f24..8db67961a 100644 --- a/versioned_docs/version-2.14/reference/targets/jvm_war.mdx +++ b/versioned_docs/version-2.14/reference/targets/jvm_war.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.java` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -74,9 +74,9 @@ A list of addresses to `resources` and `files` targets with content to place in Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -106,7 +106,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. diff --git a/versioned_docs/version-2.14/reference/targets/kotlin_junit_test.mdx b/versioned_docs/version-2.14/reference/targets/kotlin_junit_test.mdx index bdeec17b6..8c9e48bb1 100644 --- a/versioned_docs/version-2.14/reference/targets/kotlin_junit_test.mdx +++ b/versioned_docs/version-2.14/reference/targets/kotlin_junit_test.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.kotlin` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.14/reference/targets/kotlin_junit_tests.mdx b/versioned_docs/version-2.14/reference/targets/kotlin_junit_tests.mdx index 5585f2c93..06f3f98b1 100644 --- a/versioned_docs/version-2.14/reference/targets/kotlin_junit_tests.mdx +++ b/versioned_docs/version-2.14/reference/targets/kotlin_junit_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.kotlin` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -65,9 +65,9 @@ Example: `sources=['*Test.kt', '!TestIgnore.kt']` Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.14/reference/targets/kotlin_source.mdx b/versioned_docs/version-2.14/reference/targets/kotlin_source.mdx index 8579e62a0..c311373e0 100644 --- a/versioned_docs/version-2.14/reference/targets/kotlin_source.mdx +++ b/versioned_docs/version-2.14/reference/targets/kotlin_source.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.kotlin` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.14/reference/targets/kotlin_sources.mdx b/versioned_docs/version-2.14/reference/targets/kotlin_sources.mdx index bd6c6643d..b4d16acdf 100644 --- a/versioned_docs/version-2.14/reference/targets/kotlin_sources.mdx +++ b/versioned_docs/version-2.14/reference/targets/kotlin_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.kotlin` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -77,9 +77,9 @@ If true, don't run Ktlint on this target's code. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.14/reference/targets/kotlinc_plugin.mdx b/versioned_docs/version-2.14/reference/targets/kotlinc_plugin.mdx index 936aa994f..5facbbddf 100644 --- a/versioned_docs/version-2.14/reference/targets/kotlinc_plugin.mdx +++ b/versioned_docs/version-2.14/reference/targets/kotlinc_plugin.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.kotlin` @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.14/reference/targets/pants_requirements.mdx b/versioned_docs/version-2.14/reference/targets/pants_requirements.mdx index b614acc58..3ee24852c 100644 --- a/versioned_docs/version-2.14/reference/targets/pants_requirements.mdx +++ b/versioned_docs/version-2.14/reference/targets/pants_requirements.mdx @@ -30,7 +30,7 @@ Backend: `pants.backend.plugin_development` @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.14/reference/targets/pex_binaries.mdx b/versioned_docs/version-2.14/reference/targets/pex_binaries.mdx index 4807105d7..7bd63d6a1 100644 --- a/versioned_docs/version-2.14/reference/targets/pex_binaries.mdx +++ b/versioned_docs/version-2.14/reference/targets/pex_binaries.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -132,9 +132,9 @@ All dependencies must share the same value for their `resolve` field. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.14/reference/targets/pex_binary.mdx b/versioned_docs/version-2.14/reference/targets/pex_binary.mdx index e7485af79..bce516396 100644 --- a/versioned_docs/version-2.14/reference/targets/pex_binary.mdx +++ b/versioned_docs/version-2.14/reference/targets/pex_binary.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -86,9 +86,9 @@ All dependencies must share the same value for their `resolve` field. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -337,7 +337,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. diff --git a/versioned_docs/version-2.14/reference/targets/pipenv_requirements.mdx b/versioned_docs/version-2.14/reference/targets/pipenv_requirements.mdx index e87501d1a..1a319f31a 100644 --- a/versioned_docs/version-2.14/reference/targets/pipenv_requirements.mdx +++ b/versioned_docs/version-2.14/reference/targets/pipenv_requirements.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.14/reference/targets/poetry_requirements.mdx b/versioned_docs/version-2.14/reference/targets/poetry_requirements.mdx index 4d8346512..344c86b2f 100644 --- a/versioned_docs/version-2.14/reference/targets/poetry_requirements.mdx +++ b/versioned_docs/version-2.14/reference/targets/poetry_requirements.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.14/reference/targets/protobuf_source.mdx b/versioned_docs/version-2.14/reference/targets/protobuf_source.mdx index 19d8477dd..1e0e81851 100644 --- a/versioned_docs/version-2.14/reference/targets/protobuf_source.mdx +++ b/versioned_docs/version-2.14/reference/targets/protobuf_source.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.codegen.protobuf.python Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -54,9 +54,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.14/reference/targets/protobuf_sources.mdx b/versioned_docs/version-2.14/reference/targets/protobuf_sources.mdx index b287a4566..96dd979ba 100644 --- a/versioned_docs/version-2.14/reference/targets/protobuf_sources.mdx +++ b/versioned_docs/version-2.14/reference/targets/protobuf_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.codegen.protobuf.python Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -218,9 +218,9 @@ Whether to generate gRPC code or not. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.14/reference/targets/pyoxidizer_binary.mdx b/versioned_docs/version-2.14/reference/targets/pyoxidizer_binary.mdx index 7dcf0d8d8..1b4b82772 100644 --- a/versioned_docs/version-2.14/reference/targets/pyoxidizer_binary.mdx +++ b/versioned_docs/version-2.14/reference/targets/pyoxidizer_binary.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.python.pac Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -58,7 +58,7 @@ If undefined, this will use the path to the BUILD file, followed by the target n Regardless of whether you use the default or set this field, the path will end with PyOxidizer's file format of `/{debug,release}/install/`, where `platform` is a Rust platform triplet like `aarch-64-apple-darwin` and `binary_name` is the `name` of the `pyoxidizer_target`. So, using the default for this field, the target `src/python/project:bin` might have a final path like `src.python.project/bin/aarch-64-apple-darwin/release/bin`. -When running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. diff --git a/versioned_docs/version-2.14/reference/targets/python_awslambda.mdx b/versioned_docs/version-2.14/reference/targets/python_awslambda.mdx index 45b1f8256..65448511a 100644 --- a/versioned_docs/version-2.14/reference/targets/python_awslambda.mdx +++ b/versioned_docs/version-2.14/reference/targets/python_awslambda.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.awslambda.python` @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -54,7 +54,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. @@ -69,9 +69,9 @@ Warning: setting this value risks naming collisions with other package targets y Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.14/reference/targets/python_distribution.mdx b/versioned_docs/version-2.14/reference/targets/python_distribution.mdx index 7d6ca9311..1c7dfed47 100644 --- a/versioned_docs/version-2.14/reference/targets/python_distribution.mdx +++ b/versioned_docs/version-2.14/reference/targets/python_distribution.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -71,9 +71,9 @@ See https://www.pantsbuild.org/v2.14/docs/python-interpreter-compatibility for h Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -108,7 +108,7 @@ Note that Pants will assume that any value that either starts with `:` or has `/ Pants will attempt to infer dependencies, which you can confirm by running: ``` -/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies +/home/josh/work/scie-pants/dist/pants dependencies ``` diff --git a/versioned_docs/version-2.14/reference/targets/python_google_cloud_function.mdx b/versioned_docs/version-2.14/reference/targets/python_google_cloud_function.mdx index 36834dc1b..165c21bc8 100644 --- a/versioned_docs/version-2.14/reference/targets/python_google_cloud_function.mdx +++ b/versioned_docs/version-2.14/reference/targets/python_google_cloud_function.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.google_cloud_function.p Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -54,7 +54,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. @@ -69,9 +69,9 @@ Warning: setting this value risks naming collisions with other package targets y Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.14/reference/targets/python_requirement.mdx b/versioned_docs/version-2.14/reference/targets/python_requirement.mdx index a44474edf..1026e31f9 100644 --- a/versioned_docs/version-2.14/reference/targets/python_requirement.mdx +++ b/versioned_docs/version-2.14/reference/targets/python_requirement.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -69,9 +69,9 @@ If the requirement depends on some other requirement to work, such as needing `s Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.14/reference/targets/python_requirements.mdx b/versioned_docs/version-2.14/reference/targets/python_requirements.mdx index 2691c18c2..6fba0b9aa 100644 --- a/versioned_docs/version-2.14/reference/targets/python_requirements.mdx +++ b/versioned_docs/version-2.14/reference/targets/python_requirements.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.14/reference/targets/python_source.mdx b/versioned_docs/version-2.14/reference/targets/python_source.mdx index cb4612433..54b5bec3b 100644 --- a/versioned_docs/version-2.14/reference/targets/python_source.mdx +++ b/versioned_docs/version-2.14/reference/targets/python_source.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -69,9 +69,9 @@ See https://www.pantsbuild.org/v2.14/docs/python-interpreter-compatibility for h Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.14/reference/targets/python_sources.mdx b/versioned_docs/version-2.14/reference/targets/python_sources.mdx index 1c4353157..23010ef34 100644 --- a/versioned_docs/version-2.14/reference/targets/python_sources.mdx +++ b/versioned_docs/version-2.14/reference/targets/python_sources.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -247,9 +247,9 @@ The latter mode is similar to creating, activating, and using a virtual environm Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.14/reference/targets/python_test.mdx b/versioned_docs/version-2.14/reference/targets/python_test.mdx index 152970954..103f5fbe6 100644 --- a/versioned_docs/version-2.14/reference/targets/python_test.mdx +++ b/versioned_docs/version-2.14/reference/targets/python_test.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -54,9 +54,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -135,11 +135,11 @@ Set this field to `0` to explicitly disable use of `pytest-xdist` for a target. default_repr={`None`} > -Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run. +Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/pants package` goal and whose resulting artifacts should be included in the test run. -Pants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). +Pants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). -You can include anything that can be built by `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`. +You can include anything that can be built by `/home/josh/work/scie-pants/dist/pants package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`. @@ -197,9 +197,9 @@ If true, don't run this target's tests. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.14/reference/targets/python_test_utils.mdx b/versioned_docs/version-2.14/reference/targets/python_test_utils.mdx index 4180707d2..0d53038bc 100644 --- a/versioned_docs/version-2.14/reference/targets/python_test_utils.mdx +++ b/versioned_docs/version-2.14/reference/targets/python_test_utils.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -247,9 +247,9 @@ The latter mode is similar to creating, activating, and using a virtual environm Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.14/reference/targets/python_tests.mdx b/versioned_docs/version-2.14/reference/targets/python_tests.mdx index 0f726b7d8..910a376ec 100644 --- a/versioned_docs/version-2.14/reference/targets/python_tests.mdx +++ b/versioned_docs/version-2.14/reference/targets/python_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -211,9 +211,9 @@ If true, don't run Bandit on this target's code. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -292,11 +292,11 @@ Set this field to `0` to explicitly disable use of `pytest-xdist` for a target. default_repr={`None`} > -Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run. +Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/pants package` goal and whose resulting artifacts should be included in the test run. -Pants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). +Pants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). -You can include anything that can be built by `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`. +You can include anything that can be built by `/home/josh/work/scie-pants/dist/pants package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`. diff --git a/versioned_docs/version-2.14/reference/targets/relocated_files.mdx b/versioned_docs/version-2.14/reference/targets/relocated_files.mdx index 73ed0c422..b920f40cd 100644 --- a/versioned_docs/version-2.14/reference/targets/relocated_files.mdx +++ b/versioned_docs/version-2.14/reference/targets/relocated_files.mdx @@ -61,7 +61,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -74,7 +74,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.14/reference/targets/resource.mdx b/versioned_docs/version-2.14/reference/targets/resource.mdx index a1b202f58..ea8968a40 100644 --- a/versioned_docs/version-2.14/reference/targets/resource.mdx +++ b/versioned_docs/version-2.14/reference/targets/resource.mdx @@ -26,7 +26,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -52,9 +52,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.14/reference/targets/resources.mdx b/versioned_docs/version-2.14/reference/targets/resources.mdx index 8721206a2..a25273fb0 100644 --- a/versioned_docs/version-2.14/reference/targets/resources.mdx +++ b/versioned_docs/version-2.14/reference/targets/resources.mdx @@ -24,7 +24,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -91,9 +91,9 @@ You can specify the same file name in multiple keys, so long as you don't o Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.14/reference/targets/scala_junit_test.mdx b/versioned_docs/version-2.14/reference/targets/scala_junit_test.mdx index d1be0ee7f..ff50a2605 100644 --- a/versioned_docs/version-2.14/reference/targets/scala_junit_test.mdx +++ b/versioned_docs/version-2.14/reference/targets/scala_junit_test.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.scala` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.14/reference/targets/scala_junit_tests.mdx b/versioned_docs/version-2.14/reference/targets/scala_junit_tests.mdx index 2b4f1063b..def256abf 100644 --- a/versioned_docs/version-2.14/reference/targets/scala_junit_tests.mdx +++ b/versioned_docs/version-2.14/reference/targets/scala_junit_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.scala` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -104,9 +104,9 @@ If unset, will default to `[test].timeout_default`; if that option is also unset Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.14/reference/targets/scala_source.mdx b/versioned_docs/version-2.14/reference/targets/scala_source.mdx index eedc940c5..3e751d21c 100644 --- a/versioned_docs/version-2.14/reference/targets/scala_source.mdx +++ b/versioned_docs/version-2.14/reference/targets/scala_source.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.scala` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.14/reference/targets/scala_sources.mdx b/versioned_docs/version-2.14/reference/targets/scala_sources.mdx index c8b43f093..e858897a5 100644 --- a/versioned_docs/version-2.14/reference/targets/scala_sources.mdx +++ b/versioned_docs/version-2.14/reference/targets/scala_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.scala` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -103,9 +103,9 @@ If true, don't run `scalafmt` on this target's code. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.14/reference/targets/scalac_plugin.mdx b/versioned_docs/version-2.14/reference/targets/scalac_plugin.mdx index 53c633e66..2d5fa0e60 100644 --- a/versioned_docs/version-2.14/reference/targets/scalac_plugin.mdx +++ b/versioned_docs/version-2.14/reference/targets/scalac_plugin.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.scala` @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.14/reference/targets/scalatest_test.mdx b/versioned_docs/version-2.14/reference/targets/scalatest_test.mdx index e892a2eb4..921599900 100644 --- a/versioned_docs/version-2.14/reference/targets/scalatest_test.mdx +++ b/versioned_docs/version-2.14/reference/targets/scalatest_test.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.scala` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.14/reference/targets/scalatest_tests.mdx b/versioned_docs/version-2.14/reference/targets/scalatest_tests.mdx index f66f58b49..e8aff87a4 100644 --- a/versioned_docs/version-2.14/reference/targets/scalatest_tests.mdx +++ b/versioned_docs/version-2.14/reference/targets/scalatest_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.scala` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -91,9 +91,9 @@ You can specify the same file name in multiple keys, so long as you don't o Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.14/reference/targets/shell_source.mdx b/versioned_docs/version-2.14/reference/targets/shell_source.mdx index a9463d616..233422236 100644 --- a/versioned_docs/version-2.14/reference/targets/shell_source.mdx +++ b/versioned_docs/version-2.14/reference/targets/shell_source.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.14/reference/targets/shell_sources.mdx b/versioned_docs/version-2.14/reference/targets/shell_sources.mdx index 40da5db3c..3ad129b60 100644 --- a/versioned_docs/version-2.14/reference/targets/shell_sources.mdx +++ b/versioned_docs/version-2.14/reference/targets/shell_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -115,9 +115,9 @@ If true, don't run shfmt on this target's code. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.14/reference/targets/shunit2_test.mdx b/versioned_docs/version-2.14/reference/targets/shunit2_test.mdx index 2a1c6a2dc..9de2946b4 100644 --- a/versioned_docs/version-2.14/reference/targets/shunit2_test.mdx +++ b/versioned_docs/version-2.14/reference/targets/shunit2_test.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -67,9 +67,9 @@ Path is relative to the BUILD file's directory, e.g. `source='example.ext'` Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -119,11 +119,11 @@ Which shell to run the tests with. If unspecified, Pants will look for a shebang default_repr={`None`} > -Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run. +Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/pants package` goal and whose resulting artifacts should be included in the test run. -Pants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). +Pants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). -You can include anything that can be built by `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`. +You can include anything that can be built by `/home/josh/work/scie-pants/dist/pants package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`. diff --git a/versioned_docs/version-2.14/reference/targets/shunit2_tests.mdx b/versioned_docs/version-2.14/reference/targets/shunit2_tests.mdx index fff7c0085..fab2482dd 100644 --- a/versioned_docs/version-2.14/reference/targets/shunit2_tests.mdx +++ b/versioned_docs/version-2.14/reference/targets/shunit2_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -115,9 +115,9 @@ If true, don't run shfmt on this target's code. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -167,11 +167,11 @@ Which shell to run the tests with. If unspecified, Pants will look for a shebang default_repr={`None`} > -Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run. +Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/pants package` goal and whose resulting artifacts should be included in the test run. -Pants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). +Pants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). -You can include anything that can be built by `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`. +You can include anything that can be built by `/home/josh/work/scie-pants/dist/pants package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`. diff --git a/versioned_docs/version-2.14/reference/targets/target.mdx b/versioned_docs/version-2.14/reference/targets/target.mdx index 070d416d3..792380ad5 100644 --- a/versioned_docs/version-2.14/reference/targets/target.mdx +++ b/versioned_docs/version-2.14/reference/targets/target.mdx @@ -26,7 +26,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -52,9 +52,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.14/reference/targets/terraform_module.mdx b/versioned_docs/version-2.14/reference/targets/terraform_module.mdx index 20ffd7ffb..59f40f8ce 100644 --- a/versioned_docs/version-2.14/reference/targets/terraform_module.mdx +++ b/versioned_docs/version-2.14/reference/targets/terraform_module.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.terraform` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -54,9 +54,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.14/reference/targets/thrift_source.mdx b/versioned_docs/version-2.14/reference/targets/thrift_source.mdx index 42dbd2c24..5075afcf0 100644 --- a/versioned_docs/version-2.14/reference/targets/thrift_source.mdx +++ b/versioned_docs/version-2.14/reference/targets/thrift_source.mdx @@ -27,7 +27,7 @@ Backend: `pants.backend.codegen.thrift.apache.p Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -40,7 +40,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -53,9 +53,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.14/reference/targets/thrift_sources.mdx b/versioned_docs/version-2.14/reference/targets/thrift_sources.mdx index 83763471d..63ba932f7 100644 --- a/versioned_docs/version-2.14/reference/targets/thrift_sources.mdx +++ b/versioned_docs/version-2.14/reference/targets/thrift_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.codegen.thrift.apache.p Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -106,9 +106,9 @@ All dependencies must share the same value for their `resolve` field. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.14/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.14/reference/targets/vcs_version.mdx b/versioned_docs/version-2.14/reference/targets/vcs_version.mdx index ff402b266..1b1a60cf8 100644 --- a/versioned_docs/version-2.14/reference/targets/vcs_version.mdx +++ b/versioned_docs/version-2.14/reference/targets/vcs_version.mdx @@ -30,7 +30,7 @@ Backend: `pants.backend.experimental.python` @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.15/reference/global-options.mdx b/versioned_docs/version-2.15/reference/global-options.mdx index d6bbfdf53..5af68ca7f 100644 --- a/versioned_docs/version-2.15/reference/global-options.mdx +++ b/versioned_docs/version-2.15/reference/global-options.mdx @@ -317,9 +317,9 @@ ignore_warnings = [ Use this Pants version. Note that Pants only uses this to verify that you are using the requested version, as Pants cannot dynamically change the version it is using once the program is already running. -If you use the `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64` script from https://www.pantsbuild.org/v2.15/docs/installation, however, changing the value in your `pants.toml` will cause the new version to be installed and run automatically. +If you use the `/home/josh/work/scie-pants/dist/pants` script from https://www.pantsbuild.org/v2.15/docs/installation, however, changing the value in your `pants.toml` will cause the new version to be installed and run automatically. -Run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --version` to check what is being used. +Run `/home/josh/work/scie-pants/dist/pants --version` to check what is being used. @@ -824,7 +824,7 @@ Whether or not to use nailgun to run JVM requests that are marked as supporting default_repr={`3`} > -The time in seconds to wait when gracefully shutting down an interactive process (such as one opened using `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 run`) before killing it. +The time in seconds to wait when gracefully shutting down an interactive process (such as one opened using `/home/josh/work/scie-pants/dist/pants run`) before killing it. diff --git a/versioned_docs/version-2.15/reference/goals/experimental-bsp.mdx b/versioned_docs/version-2.15/reference/goals/experimental-bsp.mdx index d6c922d3b..9601d9650 100644 --- a/versioned_docs/version-2.15/reference/goals/experimental-bsp.mdx +++ b/versioned_docs/version-2.15/reference/goals/experimental-bsp.mdx @@ -79,7 +79,7 @@ Run the Build Server Protocol server. Pants will receive BSP RPC requests via th Environment variables to set in the BSP runner script when setting up BSP in a repository. Entries are either strings in the form `ENV_VAR=value` to set an explicit value; or just `ENV_VAR` to copy the value from Pants' own environment when the experimental-bsp goal was run. -This option only takes effect when the BSP runner script is written. If the option changes, you must run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 experimental-bsp` again to write a new copy of the BSP runner script. +This option only takes effect when the BSP runner script is written. If the option changes, you must run `/home/josh/work/scie-pants/dist/pants experimental-bsp` again to write a new copy of the BSP runner script. Note: The environment variables passed to the Pants BSP server will be those set for your IDE and not your shell. For example, on macOS, the IDE is generally launched by `launchd` after clicking on a Dock icon, and not from the shell. Thus, any environment variables set for your shell will likely not be seen by the Pants BSP server. At the very least, on macOS consider writing an explicit PATH into the BSP runner script via this option. diff --git a/versioned_docs/version-2.15/reference/goals/fix.mdx b/versioned_docs/version-2.15/reference/goals/fix.mdx index 0261bd750..8286089dc 100644 --- a/versioned_docs/version-2.15/reference/goals/fix.mdx +++ b/versioned_docs/version-2.15/reference/goals/fix.mdx @@ -47,7 +47,7 @@ You can repeat this option, e.g. `fix --only=autoflake --only=pyupgrade` or `fix If true, skip running all formatters. -FYI: when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fix fmt ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `fix` where possible. +FYI: when running `/home/josh/work/scie-pants/dist/pants fix fmt ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `fix` where possible. diff --git a/versioned_docs/version-2.15/reference/goals/generate-lockfiles.mdx b/versioned_docs/version-2.15/reference/goals/generate-lockfiles.mdx index 80c49f897..5e272025f 100644 --- a/versioned_docs/version-2.15/reference/goals/generate-lockfiles.mdx +++ b/versioned_docs/version-2.15/reference/goals/generate-lockfiles.mdx @@ -33,7 +33,7 @@ Only generate lockfiles for the specified resolve(s). Resolves are the logical names for the different lockfiles used in your project. For your own code's dependencies, these come from backend-specific configuration such as `[python].resolves`. For tool lockfiles, resolve names are the options scope for that tool such as `black`, `pytest`, and `mypy-protobuf`. -For example, you can run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=black --resolve=pytest --resolve=data-science` to only generate lockfiles for those two tools and your resolve named `data-science`. +For example, you can run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=black --resolve=pytest --resolve=data-science` to only generate lockfiles for those two tools and your resolve named `data-science`. If you specify an invalid resolve name, like 'fake', Pants will output all possible values. @@ -51,7 +51,7 @@ If not specified, Pants will generate lockfiles for all resolves. default_repr={`None`} > -If set, lockfile headers will say to run this command to regenerate the lockfile, rather than running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=` like normal. +If set, lockfile headers will say to run this command to regenerate the lockfile, rather than running `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=` like normal. diff --git a/versioned_docs/version-2.15/reference/goals/lint.mdx b/versioned_docs/version-2.15/reference/goals/lint.mdx index a44207069..f5db4591a 100644 --- a/versioned_docs/version-2.15/reference/goals/lint.mdx +++ b/versioned_docs/version-2.15/reference/goals/lint.mdx @@ -47,7 +47,7 @@ You can repeat this option, e.g. `lint --only=flake8 --only=shellcheck` or `lint If true, skip running all formatters in check-only mode. -FYI: when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `lint` where possible. +FYI: when running `/home/josh/work/scie-pants/dist/pants fmt lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `lint` where possible. @@ -61,7 +61,7 @@ FYI: when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt l If true, skip running all fixers in check-only mode. -FYI: when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fix lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fix` when running `lint` where possible. +FYI: when running `/home/josh/work/scie-pants/dist/pants fix lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fix` when running `lint` where possible. diff --git a/versioned_docs/version-2.15/reference/help-all.json b/versioned_docs/version-2.15/reference/help-all.json index 3cd51fc47..d5c733e8c 100644 --- a/versioned_docs/version-2.15/reference/help-all.json +++ b/versioned_docs/version-2.15/reference/help-all.json @@ -31714,7 +31714,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -31722,7 +31722,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -31746,7 +31746,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -31754,7 +31754,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -31770,7 +31770,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -31786,7 +31786,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -31794,7 +31794,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -31810,7 +31810,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -31826,7 +31826,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -31834,7 +31834,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -31842,7 +31842,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -31850,7 +31850,7 @@ { "alias": "packages", "default": null, - "description": "Addresses to any targets that can be built with `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, e.g. `[\"project:app\"]`.\n\nPants will build the assets as if you had run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`. It will include the results in your archive using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or even another `archive`.", + "description": "Addresses to any targets that can be built with `/home/josh/work/scie-pants/dist/pants package`, e.g. `[\"project:app\"]`.\n\nPants will build the assets as if you had run `/home/josh/work/scie-pants/dist/pants package`. It will include the results in your archive using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `/home/josh/work/scie-pants/dist/pants package`, e.g. a `pex_binary`, `python_awslambda`, or even another `archive`.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -31882,7 +31882,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -31890,7 +31890,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -31898,7 +31898,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -31906,7 +31906,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -31954,7 +31954,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -31962,7 +31962,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -32186,7 +32186,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -32194,7 +32194,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -32210,7 +32210,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -32290,7 +32290,7 @@ { "alias": "skip_push", "default": "False", - "description": "If set to true, do not push this image to registries when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 publish`.", + "description": "If set to true, do not push this image to registries when running `/home/josh/work/scie-pants/dist/pants publish`.", "provider": "", "required": false, "type_hint": "bool" @@ -32346,7 +32346,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -32354,7 +32354,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -32362,7 +32362,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -32394,7 +32394,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -32402,7 +32402,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -32410,7 +32410,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -32482,7 +32482,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -32490,7 +32490,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -32498,7 +32498,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -32522,7 +32522,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -32530,7 +32530,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -32554,7 +32554,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -32570,7 +32570,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -32578,7 +32578,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -32586,7 +32586,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -32618,7 +32618,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -32626,7 +32626,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -32642,7 +32642,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -32650,7 +32650,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -32658,7 +32658,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -32714,7 +32714,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -32722,7 +32722,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -32730,7 +32730,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -32754,7 +32754,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -32762,7 +32762,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -32810,7 +32810,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -32818,7 +32818,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -32842,7 +32842,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -32850,7 +32850,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built directory tree should be located.\n\nIf undefined, this will use the path to the BUILD file, For example, `src/charts/mychart:tgt_name` would be `src.charts.mychart/tgt_name/`.\n\nRegardless of whether you use the default or set this field, the path will end with Helms's file format of `-.tgz`, where `chart_name` and `chart_version` are the values extracted from the Chart.yaml file. So, using the default for this field, the target `src/charts/mychart:tgt_name` might have a final path like `src.charts.mychart/tgt_name/mychart-0.1.0.tgz`.\n\nWhen running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built directory tree should be located.\n\nIf undefined, this will use the path to the BUILD file, For example, `src/charts/mychart:tgt_name` would be `src.charts.mychart/tgt_name/`.\n\nRegardless of whether you use the default or set this field, the path will end with Helms's file format of `-.tgz`, where `chart_name` and `chart_version` are the values extracted from the Chart.yaml file. So, using the default for this field, the target `src/charts/mychart:tgt_name` might have a final path like `src.charts.mychart/tgt_name/mychart-0.1.0.tgz`.\n\nWhen running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -32882,7 +32882,7 @@ { "alias": "skip_push", "default": "False", - "description": "If set to true, do not push this Helm chart to registries when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 publish`.", + "description": "If set to true, do not push this Helm chart to registries when running `/home/josh/work/scie-pants/dist/pants publish`.", "provider": "", "required": false, "type_hint": "bool" @@ -32890,7 +32890,7 @@ { "alias": "skip_lint", "default": "False", - "description": "If set to true, do not run any linting in this Helm chart when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "description": "If set to true, do not run any linting in this Helm chart when running `/home/josh/work/scie-pants/dist/pants lint`.", "provider": "", "required": false, "type_hint": "bool" @@ -32906,7 +32906,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -32914,7 +32914,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -32930,7 +32930,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -33010,7 +33010,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -33018,7 +33018,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -33034,7 +33034,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -33066,7 +33066,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -33074,7 +33074,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -33090,7 +33090,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -33106,7 +33106,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -33138,7 +33138,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -33146,7 +33146,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -33154,7 +33154,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -33210,7 +33210,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -33218,7 +33218,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -33242,7 +33242,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -33282,7 +33282,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -33290,7 +33290,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -33322,7 +33322,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -33362,7 +33362,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -33370,7 +33370,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -33402,7 +33402,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -33442,7 +33442,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -33450,7 +33450,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -33530,7 +33530,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -33538,7 +33538,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -33562,7 +33562,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -33578,7 +33578,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -33594,7 +33594,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -33602,7 +33602,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -33610,7 +33610,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -33682,7 +33682,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -33690,7 +33690,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -33706,7 +33706,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -33770,7 +33770,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -33778,7 +33778,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -33786,7 +33786,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -33850,7 +33850,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -33858,7 +33858,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -33882,7 +33882,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -33930,7 +33930,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -33938,7 +33938,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -33978,7 +33978,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -33986,7 +33986,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -34202,7 +34202,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -34210,7 +34210,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -34218,7 +34218,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -34250,7 +34250,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -34258,7 +34258,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -34282,7 +34282,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -34298,7 +34298,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -34306,7 +34306,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -34314,7 +34314,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -34338,7 +34338,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -34346,7 +34346,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -34362,7 +34362,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -34378,7 +34378,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -34386,7 +34386,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -34418,7 +34418,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -34426,7 +34426,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -34474,7 +34474,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -34610,7 +34610,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -34618,7 +34618,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -34650,7 +34650,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -34794,7 +34794,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -34810,7 +34810,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -34818,7 +34818,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -34874,7 +34874,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -34882,7 +34882,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -34938,7 +34938,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -34946,7 +34946,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -34954,7 +34954,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -35050,7 +35050,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -35058,7 +35058,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -35154,7 +35154,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -35170,7 +35170,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -35178,7 +35178,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -35186,7 +35186,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built directory tree should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:bin` would be `src.python.project/bin/`.\n\nRegardless of whether you use the default or set this field, the path will end with PyOxidizer's file format of `/{debug,release}/install/`, where `platform` is a Rust platform triplet like `aarch-64-apple-darwin` and `binary_name` is the value of the `binary_name` field. So, using the default for this field, the target `src/python/project:bin` might have a final path like `src.python.project/bin/aarch-64-apple-darwin/release/bin`.\n\nWhen running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built directory tree should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:bin` would be `src.python.project/bin/`.\n\nRegardless of whether you use the default or set this field, the path will end with PyOxidizer's file format of `/{debug,release}/install/`, where `platform` is a Rust platform triplet like `aarch-64-apple-darwin` and `binary_name` is the value of the `binary_name` field. So, using the default for this field, the target `src/python/project:bin` might have a final path like `src.python.project/bin/aarch-64-apple-darwin/release/bin`.\n\nWhen running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -35250,7 +35250,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -35258,7 +35258,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -35266,7 +35266,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -35274,7 +35274,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -35338,7 +35338,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -35346,7 +35346,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -35362,7 +35362,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -35370,7 +35370,7 @@ { "alias": "entry_points", "default": null, - "description": "Any entry points, such as `console_scripts` and `gui_scripts`.\n\nSpecify as a nested dictionary, with a dictionary for each type of entry point, e.g. `console_scripts` vs. `gui_scripts`. Each dictionary maps the entry point name to either a setuptools entry point (\"path.to.module:func\") or a Pants target address to a pex_binary target.\n\n Example:\n\n entry_points={\n \"console_scripts\": {\n \"my-script\": \"project.app:main\",\n \"another-script\": \"project/subdir:pex_binary_tgt\"\n }\n }\n\nNote that Pants will assume that any value that either starts with `:` or has `/` in it, is a target address to a pex_binary target. Otherwise, it will assume it's a setuptools entry point as defined by https://packaging.python.org/specifications/entry-points/#entry-points-specification. Use `//` as a prefix for target addresses if you need to disambiguate.\n\nPants will attempt to infer dependencies, which you can confirm by running:\n\n /home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies ", + "description": "Any entry points, such as `console_scripts` and `gui_scripts`.\n\nSpecify as a nested dictionary, with a dictionary for each type of entry point, e.g. `console_scripts` vs. `gui_scripts`. Each dictionary maps the entry point name to either a setuptools entry point (\"path.to.module:func\") or a Pants target address to a pex_binary target.\n\n Example:\n\n entry_points={\n \"console_scripts\": {\n \"my-script\": \"project.app:main\",\n \"another-script\": \"project/subdir:pex_binary_tgt\"\n }\n }\n\nNote that Pants will assume that any value that either starts with `:` or has `/` in it, is a target address to a pex_binary target. Otherwise, it will assume it's a setuptools entry point as defined by https://packaging.python.org/specifications/entry-points/#entry-points-specification. Use `//` as a prefix for target addresses if you need to disambiguate.\n\nPants will attempt to infer dependencies, which you can confirm by running:\n\n /home/josh/work/scie-pants/dist/pants dependencies ", "provider": "", "required": false, "type_hint": "Dict[str, Dict[str, str]] | None" @@ -35474,7 +35474,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -35482,7 +35482,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -35490,7 +35490,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -35498,7 +35498,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -35562,7 +35562,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -35570,7 +35570,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -35586,7 +35586,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -35626,7 +35626,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -35634,7 +35634,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -35690,7 +35690,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -35698,7 +35698,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -35714,7 +35714,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -35842,7 +35842,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -35850,7 +35850,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -35978,7 +35978,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -36002,7 +36002,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -36010,7 +36010,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -36018,7 +36018,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -36066,7 +36066,7 @@ { "alias": "runtime_package_dependencies", "default": null, - "description": "Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`.", + "description": "Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/pants package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `/home/josh/work/scie-pants/dist/pants package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -36210,7 +36210,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -36218,7 +36218,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -36346,7 +36346,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -36370,7 +36370,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -36378,7 +36378,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -36490,7 +36490,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -36538,7 +36538,7 @@ { "alias": "runtime_package_dependencies", "default": null, - "description": "Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`.", + "description": "Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/pants package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `/home/josh/work/scie-pants/dist/pants package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -36586,7 +36586,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -36594,7 +36594,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -36634,7 +36634,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -36642,7 +36642,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -36874,7 +36874,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -36882,7 +36882,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -36890,7 +36890,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -36914,7 +36914,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -36922,7 +36922,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -36946,7 +36946,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -36962,7 +36962,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -36970,7 +36970,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -36978,7 +36978,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -37050,7 +37050,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -37058,7 +37058,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -37090,7 +37090,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -37154,7 +37154,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -37162,7 +37162,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -37170,7 +37170,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -37234,7 +37234,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -37242,7 +37242,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -37274,7 +37274,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -37322,7 +37322,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -37330,7 +37330,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -37362,7 +37362,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -37370,7 +37370,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -37378,7 +37378,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -37450,7 +37450,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -37458,7 +37458,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -37482,7 +37482,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -37546,7 +37546,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -37554,7 +37554,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -37562,7 +37562,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -37602,7 +37602,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -37610,7 +37610,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -37650,7 +37650,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -37666,7 +37666,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -37674,7 +37674,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -37690,7 +37690,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -37722,7 +37722,7 @@ { "alias": "runtime_package_dependencies", "default": null, - "description": "Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`.", + "description": "Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/pants package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `/home/josh/work/scie-pants/dist/pants package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -37754,7 +37754,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -37762,7 +37762,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -37802,7 +37802,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -37834,7 +37834,7 @@ { "alias": "runtime_package_dependencies", "default": null, - "description": "Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`.", + "description": "Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/pants package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `/home/josh/work/scie-pants/dist/pants package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -37850,7 +37850,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -37858,7 +37858,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -37866,7 +37866,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -37882,7 +37882,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -37890,7 +37890,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -37898,7 +37898,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -37922,7 +37922,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -37930,7 +37930,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -37938,7 +37938,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -37970,7 +37970,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -37978,7 +37978,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -38010,7 +38010,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -38026,7 +38026,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -38034,7 +38034,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -38385,7 +38385,7 @@ "deprecation_active": false, "display_args": ["--pants-version="], "env_var": "PANTS_VERSION", - "help": "Use this Pants version. Note that Pants only uses this to verify that you are using the requested version, as Pants cannot dynamically change the version it is using once the program is already running.\n\nIf you use the `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64` script from https://www.pantsbuild.org/v2.15/docs/installation, however, changing the value in your `pants.toml` will cause the new version to be installed and run automatically.\n\nRun `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --version` to check what is being used.", + "help": "Use this Pants version. Note that Pants only uses this to verify that you are using the requested version, as Pants cannot dynamically change the version it is using once the program is already running.\n\nIf you use the `/home/josh/work/scie-pants/dist/pants` script from https://www.pantsbuild.org/v2.15/docs/installation, however, changing the value in your `pants.toml` will cause the new version to be installed and run automatically.\n\nRun `/home/josh/work/scie-pants/dist/pants --version` to check what is being used.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pants-version"], @@ -38444,7 +38444,7 @@ { "details": "from env var PANTS_BIN_NAME", "rank": "ENVIRONMENT", - "value": "/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64" + "value": "/home/josh/work/scie-pants/dist/pants" } ] } @@ -39608,7 +39608,7 @@ "--process-execution-graceful-shutdown-timeout=" ], "env_var": "PANTS_PROCESS_EXECUTION_GRACEFUL_SHUTDOWN_TIMEOUT", - "help": "The time in seconds to wait when gracefully shutting down an interactive process (such as one opened using `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 run`) before killing it.", + "help": "The time in seconds to wait when gracefully shutting down an interactive process (such as one opened using `/home/josh/work/scie-pants/dist/pants run`) before killing it.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -41333,7 +41333,7 @@ "deprecation_active": false, "display_args": ["--add-trailing-comma-lockfile="], "env_var": "PANTS_ADD_TRAILING_COMMA_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/python/lint/add_trailing_comma/add_trailing_comma.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=add-trailing-comma`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/python/lint/add_trailing_comma/add_trailing_comma.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=add-trailing-comma`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--add-trailing-comma-lockfile"], @@ -41426,7 +41426,7 @@ "deprecation_active": false, "display_args": ["--[no-]add-trailing-comma-skip"], "env_var": "PANTS_ADD_TRAILING_COMMA_SKIP", - "help": "If true, don't use add-trailing-comma when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use add-trailing-comma when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -41497,7 +41497,7 @@ "deprecation_active": true, "display_args": ["--[no-]add-trailing-comma-export"], "env_var": "PANTS_ADD_TRAILING_COMMA_EXPORT", - "help": "If true, export a virtual environment with add-trailing-comma when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with add-trailing-comma when running `/home/josh/work/scie-pants/dist/pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": "Use the export goal's --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.", "removal_version": "2.23.0.dev0", "scoped_cmd_line_args": [ @@ -41791,7 +41791,7 @@ "deprecation_active": false, "display_args": ["--autoflake-lockfile="], "env_var": "PANTS_AUTOFLAKE_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/python/lint/autoflake/autoflake.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=autoflake`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/python/lint/autoflake/autoflake.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=autoflake`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--autoflake-lockfile"], @@ -41884,7 +41884,7 @@ "deprecation_active": false, "display_args": ["--[no-]autoflake-skip"], "env_var": "PANTS_AUTOFLAKE_SKIP", - "help": "If true, don't use Autoflake when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Autoflake when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--autoflake-skip", "--no-autoflake-skip"], @@ -41952,7 +41952,7 @@ "deprecation_active": true, "display_args": ["--[no-]autoflake-export"], "env_var": "PANTS_AUTOFLAKE_EXPORT", - "help": "If true, export a virtual environment with Autoflake when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with Autoflake when running `/home/josh/work/scie-pants/dist/pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": "Use the export goal's --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.", "removal_version": "2.23.0.dev0", "scoped_cmd_line_args": [ @@ -42062,7 +42062,7 @@ "deprecation_active": false, "display_args": ["--bandit-lockfile="], "env_var": "PANTS_BANDIT_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/python/lint/bandit/bandit.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=bandit`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/python/lint/bandit/bandit.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=bandit`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--bandit-lockfile"], @@ -42182,7 +42182,7 @@ "deprecation_active": false, "display_args": ["--[no-]bandit-skip"], "env_var": "PANTS_BANDIT_SKIP", - "help": "If true, don't use Bandit when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Bandit when running `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--bandit-skip", "--no-bandit-skip"], @@ -42248,7 +42248,7 @@ "deprecation_active": true, "display_args": ["--[no-]bandit-export"], "env_var": "PANTS_BANDIT_EXPORT", - "help": "If true, export a virtual environment with Bandit when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with Bandit when running `/home/josh/work/scie-pants/dist/pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": "Use the export goal's --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.", "removal_version": "2.23.0.dev0", "scoped_cmd_line_args": ["--bandit-export", "--no-bandit-export"], @@ -42391,7 +42391,7 @@ "deprecation_active": false, "display_args": ["--black-lockfile="], "env_var": "PANTS_BLACK_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/python/lint/black/black.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=black`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/python/lint/black/black.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=black`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--black-lockfile"], @@ -42549,7 +42549,7 @@ "deprecation_active": false, "display_args": ["--[no-]black-skip"], "env_var": "PANTS_BLACK_SKIP", - "help": "If true, don't use Black when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Black when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--black-skip", "--no-black-skip"], @@ -42615,7 +42615,7 @@ "deprecation_active": true, "display_args": ["--[no-]black-export"], "env_var": "PANTS_BLACK_EXPORT", - "help": "If true, export a virtual environment with Black when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with Black when running `/home/josh/work/scie-pants/dist/pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": "Use the export goal's --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.", "removal_version": "2.23.0.dev0", "scoped_cmd_line_args": ["--black-export", "--no-black-export"], @@ -42842,7 +42842,7 @@ "deprecation_active": false, "display_args": ["--[no-]buf-format-skip"], "env_var": "PANTS_BUF_FORMAT_SKIP", - "help": "If true, don't use Buf when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Buf when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--buf-format-skip", "--no-buf-format-skip"], @@ -42874,7 +42874,7 @@ "deprecation_active": false, "display_args": ["--[no-]buf-lint-skip"], "env_var": "PANTS_BUF_LINT_SKIP", - "help": "If true, don't use Buf when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Buf when running `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--buf-lint-skip", "--no-buf-lint-skip"], @@ -42985,7 +42985,7 @@ "deprecation_active": false, "display_args": ["--[no-]build-deprecations-fixer-skip"], "env_var": "PANTS_BUILD_DEPRECATIONS_FIXER_SKIP", - "help": "If true, don't use BUILD Deprecations Fixer when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fix`.", + "help": "If true, don't use BUILD Deprecations Fixer when running `/home/josh/work/scie-pants/dist/pants fix`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -43218,7 +43218,7 @@ "deprecation_active": false, "display_args": ["--[no-]buildifier-skip"], "env_var": "PANTS_BUILDIFIER_SKIP", - "help": "If true, don't use Buildifier when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt`.", + "help": "If true, don't use Buildifier when running `/home/josh/work/scie-pants/dist/pants fmt`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--buildifier-skip", "--no-buildifier-skip"], @@ -43435,7 +43435,7 @@ "deprecation_active": false, "display_args": ["--cli-alias=\"{'key1': val1, 'key2': val2, ...}\""], "env_var": "PANTS_CLI_ALIAS", - "help": "Register command line aliases.\n\nExample:\n\n [cli.alias]\n green = \"fmt lint check\"\n all-changed = \"--changed-since=HEAD --changed-dependees=transitive\"\n\nThis would allow you to run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 green all-changed`, which is shorthand for `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt lint check --changed-since=HEAD --changed-dependees=transitive`.\n\nNotice: this option must be placed in a config file (e.g. `pants.toml` or `pantsrc`) to have any effect.", + "help": "Register command line aliases.\n\nExample:\n\n [cli.alias]\n green = \"fmt lint check\"\n all-changed = \"--changed-since=HEAD --changed-dependees=transitive\"\n\nThis would allow you to run `/home/josh/work/scie-pants/dist/pants green all-changed`, which is shorthand for `/home/josh/work/scie-pants/dist/pants fmt lint check --changed-since=HEAD --changed-dependees=transitive`.\n\nNotice: this option must be placed in a config file (e.g. `pants.toml` or `pantsrc`) to have any effect.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--cli-alias"], @@ -43831,7 +43831,7 @@ "deprecation_active": false, "display_args": ["--coverage-py-lockfile="], "env_var": "PANTS_COVERAGE_PY_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/python/subsystems/coverage_py.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=coverage-py`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/python/subsystems/coverage_py.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=coverage-py`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--coverage-py-lockfile"], @@ -44334,7 +44334,7 @@ "deprecation_active": false, "display_args": ["--debugpy-lockfile="], "env_var": "PANTS_DEBUGPY_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/python/subsystems/debugpy.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=debugpy`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/python/subsystems/debugpy.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=debugpy`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--debugpy-lockfile"], @@ -44851,7 +44851,7 @@ "deprecation_active": false, "display_args": ["--docformatter-lockfile="], "env_var": "PANTS_DOCFORMATTER_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/python/lint/docformatter/docformatter.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=docformatter`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/python/lint/docformatter/docformatter.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=docformatter`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--docformatter-lockfile"], @@ -44944,7 +44944,7 @@ "deprecation_active": false, "display_args": ["--[no-]docformatter-skip"], "env_var": "PANTS_DOCFORMATTER_SKIP", - "help": "If true, don't use docformatter when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use docformatter when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -45015,7 +45015,7 @@ "deprecation_active": true, "display_args": ["--[no-]docformatter-export"], "env_var": "PANTS_DOCFORMATTER_EXPORT", - "help": "If true, export a virtual environment with docformatter when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with docformatter when running `/home/josh/work/scie-pants/dist/pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": "Use the export goal's --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.", "removal_version": "2.23.0.dev0", "scoped_cmd_line_args": [ @@ -45389,7 +45389,7 @@ "--docker-run-args=\"[, , ...]\"" ], "env_var": "PANTS_DOCKER_RUN_ARGS", - "help": "Additional arguments to use for `docker run` invocations.\n\nExample:\n\n $ /home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 run --docker-run-args=\"-p 127.0.0.1:80:8080/tcp --name demo\" src/example:image -- [image entrypoint args]\n\nTo provide the top-level options to the `docker` client, use `[docker].env_vars` to configure the [Environment variables](https://docs.docker.com/engine/reference/commandline/cli/#environment-variables) as appropriate.\n\nThe arguments for the image entrypoint may be passed on the command line after a double dash (`--`), or using the `--run-args` option.\n\nDefaults to `--interactive --tty` when stdout is connected to a terminal.", + "help": "Additional arguments to use for `docker run` invocations.\n\nExample:\n\n $ /home/josh/work/scie-pants/dist/pants run --docker-run-args=\"-p 127.0.0.1:80:8080/tcp --name demo\" src/example:image -- [image entrypoint args]\n\nTo provide the top-level options to the `docker` client, use `[docker].env_vars` to configure the [Environment variables](https://docs.docker.com/engine/reference/commandline/cli/#environment-variables) as appropriate.\n\nThe arguments for the image entrypoint may be passed on the command line after a double dash (`--`), or using the `--run-args` option.\n\nDefaults to `--interactive --tty` when stdout is connected to a terminal.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--docker-run-args"], @@ -45533,7 +45533,7 @@ "deprecation_active": false, "display_args": ["--dockerfile-parser-lockfile="], "env_var": "PANTS_DOCKERFILE_PARSER_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/docker/subsystems/dockerfile.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=dockerfile-parser`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/docker/subsystems/dockerfile.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=dockerfile-parser`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--dockerfile-parser-lockfile"], @@ -46020,7 +46020,7 @@ "--experimental-bsp-runner-env-vars=\"['', '', ...]\"" ], "env_var": "PANTS_EXPERIMENTAL_BSP_RUNNER_ENV_VARS", - "help": "Environment variables to set in the BSP runner script when setting up BSP in a repository. Entries are either strings in the form `ENV_VAR=value` to set an explicit value; or just `ENV_VAR` to copy the value from Pants' own environment when the experimental-bsp goal was run.\n\nThis option only takes effect when the BSP runner script is written. If the option changes, you must run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 experimental-bsp` again to write a new copy of the BSP runner script.\n\nNote: The environment variables passed to the Pants BSP server will be those set for your IDE and not your shell. For example, on macOS, the IDE is generally launched by `launchd` after clicking on a Dock icon, and not from the shell. Thus, any environment variables set for your shell will likely not be seen by the Pants BSP server. At the very least, on macOS consider writing an explicit PATH into the BSP runner script via this option.", + "help": "Environment variables to set in the BSP runner script when setting up BSP in a repository. Entries are either strings in the form `ENV_VAR=value` to set an explicit value; or just `ENV_VAR` to copy the value from Pants' own environment when the experimental-bsp goal was run.\n\nThis option only takes effect when the BSP runner script is written. If the option changes, you must run `/home/josh/work/scie-pants/dist/pants experimental-bsp` again to write a new copy of the BSP runner script.\n\nNote: The environment variables passed to the Pants BSP server will be those set for your IDE and not your shell. For example, on macOS, the IDE is generally launched by `launchd` after clicking on a Dock icon, and not from the shell. Thus, any environment variables set for your shell will likely not be seen by the Pants BSP server. At the very least, on macOS consider writing an explicit PATH into the BSP runner script via this option.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--experimental-bsp-runner-env-vars"], @@ -46716,7 +46716,7 @@ "deprecation_active": false, "display_args": ["--[no-]fix-skip-formatters"], "env_var": "PANTS_FIX_SKIP_FORMATTERS", - "help": "If true, skip running all formatters.\n\nFYI: when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fix fmt ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `fix` where possible.", + "help": "If true, skip running all formatters.\n\nFYI: when running `/home/josh/work/scie-pants/dist/pants fix fmt ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `fix` where possible.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -46830,7 +46830,7 @@ "deprecation_active": false, "display_args": ["--flake8-lockfile="], "env_var": "PANTS_FLAKE8_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/python/lint/flake8/flake8.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=flake8`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/python/lint/flake8/flake8.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=flake8`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--flake8-lockfile"], @@ -47056,7 +47056,7 @@ "deprecation_active": false, "display_args": ["--[no-]flake8-skip"], "env_var": "PANTS_FLAKE8_SKIP", - "help": "If true, don't use Flake8 when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Flake8 when running `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--flake8-skip", "--no-flake8-skip"], @@ -47122,7 +47122,7 @@ "deprecation_active": true, "display_args": ["--[no-]flake8-export"], "env_var": "PANTS_FLAKE8_EXPORT", - "help": "If true, export a virtual environment with Flake8 when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with Flake8 when running `/home/josh/work/scie-pants/dist/pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": "Use the export goal's --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.", "removal_version": "2.23.0.dev0", "scoped_cmd_line_args": ["--flake8-export", "--no-flake8-export"], @@ -47239,7 +47239,7 @@ "deprecation_active": false, "display_args": ["--generate-lockfiles-custom-command="], "env_var": "PANTS_GENERATE_LOCKFILES_CUSTOM_COMMAND", - "help": "If set, lockfile headers will say to run this command to regenerate the lockfile, rather than running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=` like normal.", + "help": "If set, lockfile headers will say to run this command to regenerate the lockfile, rather than running `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=` like normal.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--generate-lockfiles-custom-command"], @@ -47270,7 +47270,7 @@ "--generate-lockfiles-resolve=\"['', '', ...]\"" ], "env_var": "PANTS_GENERATE_LOCKFILES_RESOLVE", - "help": "Only generate lockfiles for the specified resolve(s).\n\nResolves are the logical names for the different lockfiles used in your project. For your own code's dependencies, these come from backend-specific configuration such as `[python].resolves`. For tool lockfiles, resolve names are the options scope for that tool such as `black`, `pytest`, and `mypy-protobuf`.\n\nFor example, you can run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=black --resolve=pytest --resolve=data-science` to only generate lockfiles for those two tools and your resolve named `data-science`.\n\nIf you specify an invalid resolve name, like 'fake', Pants will output all possible values.\n\nIf not specified, Pants will generate lockfiles for all resolves.", + "help": "Only generate lockfiles for the specified resolve(s).\n\nResolves are the logical names for the different lockfiles used in your project. For your own code's dependencies, these come from backend-specific configuration such as `[python].resolves`. For tool lockfiles, resolve names are the options scope for that tool such as `black`, `pytest`, and `mypy-protobuf`.\n\nFor example, you can run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=black --resolve=pytest --resolve=data-science` to only generate lockfiles for those two tools and your resolve named `data-science`.\n\nIf you specify an invalid resolve name, like 'fake', Pants will output all possible values.\n\nIf not specified, Pants will generate lockfiles for all resolves.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--generate-lockfiles-resolve"], @@ -47493,7 +47493,7 @@ "deprecation_active": false, "display_args": ["--[no-]go-test-skip"], "env_var": "PANTS_GO_TEST_SKIP", - "help": "If true, don't use Go test binary when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 test`.", + "help": "If true, don't use Go test binary when running `/home/josh/work/scie-pants/dist/pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--go-test-skip", "--no-go-test-skip"], @@ -47536,7 +47536,7 @@ "deprecation_active": false, "display_args": ["--[no-]gofmt-skip"], "env_var": "PANTS_GOFMT_SKIP", - "help": "If true, don't use gofmt when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use gofmt when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--gofmt-skip", "--no-gofmt-skip"], @@ -48237,7 +48237,7 @@ "deprecation_active": false, "display_args": ["--google-java-format-lockfile="], "env_var": "PANTS_GOOGLE_JAVA_FORMAT_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/java/lint/google_java_format/google_java_format.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=google-java-format`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/java/lint/google_java_format/google_java_format.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=google-java-format`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--google-java-format-lockfile"], @@ -48305,7 +48305,7 @@ "deprecation_active": false, "display_args": ["--[no-]google-java-format-skip"], "env_var": "PANTS_GOOGLE_JAVA_FORMAT_SKIP", - "help": "If true, don't use Google Java Format when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Google Java Format when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -48837,7 +48837,7 @@ "deprecation_active": false, "display_args": ["--[no-]hadolint-skip"], "env_var": "PANTS_HADOLINT_SKIP", - "help": "If true, don't use Hadolint when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Hadolint when running `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--hadolint-skip", "--no-hadolint-skip"], @@ -49412,7 +49412,7 @@ "deprecation_active": false, "display_args": ["--helm-k8s-parser-lockfile="], "env_var": "PANTS_HELM_K8S_PARSER_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/helm/subsystems/k8s_parser.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=helm-k8s-parser`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/helm/subsystems/k8s_parser.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=helm-k8s-parser`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--helm-k8s-parser-lockfile"], @@ -49561,7 +49561,7 @@ "deprecation_active": false, "display_args": ["--helm-post-renderer-lockfile="], "env_var": "PANTS_HELM_POST_RENDERER_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/helm/subsystems/post_renderer.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=helm-post-renderer`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/helm/subsystems/post_renderer.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=helm-post-renderer`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--helm-post-renderer-lockfile"], @@ -49861,7 +49861,7 @@ "deprecation_active": false, "display_args": ["--[no-]helm-unittest-skip"], "env_var": "PANTS_HELM_UNITTEST_SKIP", - "help": "If true, don't use helmunittestsubsystem when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 test`.", + "help": "If true, don't use helmunittestsubsystem when running `/home/josh/work/scie-pants/dist/pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -50002,7 +50002,7 @@ "deprecation_active": false, "display_args": ["--ipython-lockfile="], "env_var": "PANTS_IPYTHON_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/python/subsystems/ipython.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=ipython`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/python/subsystems/ipython.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=ipython`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--ipython-lockfile"], @@ -50239,7 +50239,7 @@ "deprecation_active": false, "display_args": ["--isort-lockfile="], "env_var": "PANTS_ISORT_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/python/lint/isort/isort.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=isort`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/python/lint/isort/isort.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=isort`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--isort-lockfile"], @@ -50404,7 +50404,7 @@ "deprecation_active": false, "display_args": ["--[no-]isort-skip"], "env_var": "PANTS_ISORT_SKIP", - "help": "If true, don't use isort when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use isort when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--isort-skip", "--no-isort-skip"], @@ -50470,7 +50470,7 @@ "deprecation_active": true, "display_args": ["--[no-]isort-export"], "env_var": "PANTS_ISORT_EXPORT", - "help": "If true, export a virtual environment with isort when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with isort when running `/home/josh/work/scie-pants/dist/pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": "Use the export goal's --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.", "removal_version": "2.23.0.dev0", "scoped_cmd_line_args": ["--isort-export", "--no-isort-export"], @@ -50780,7 +50780,7 @@ "deprecation_active": false, "display_args": ["--junit-lockfile="], "env_var": "PANTS_JUNIT_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/jvm/test/junit.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=junit`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/jvm/test/junit.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=junit`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--junit-lockfile"], @@ -50881,7 +50881,7 @@ "deprecation_active": false, "display_args": ["--[no-]junit-skip"], "env_var": "PANTS_JUNIT_SKIP", - "help": "If true, don't use JUnit when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 test`.", + "help": "If true, don't use JUnit when running `/home/josh/work/scie-pants/dist/pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--junit-skip", "--no-junit-skip"], @@ -51517,7 +51517,7 @@ "deprecation_active": false, "display_args": ["--ktlint-lockfile="], "env_var": "PANTS_KTLINT_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/kotlin/lint/ktlint/ktlint.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=ktlint`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/kotlin/lint/ktlint/ktlint.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=ktlint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--ktlint-lockfile"], @@ -51583,7 +51583,7 @@ "deprecation_active": false, "display_args": ["--[no-]ktlint-skip"], "env_var": "PANTS_KTLINT_SKIP", - "help": "If true, don't use Ktlint when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Ktlint when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--ktlint-skip", "--no-ktlint-skip"], @@ -51725,7 +51725,7 @@ "deprecation_active": false, "display_args": ["--lambdex-lockfile="], "env_var": "PANTS_LAMBDEX_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/python/subsystems/lambdex.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=lambdex`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/python/subsystems/lambdex.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=lambdex`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--lambdex-lockfile"], @@ -51893,7 +51893,7 @@ "deprecation_active": false, "display_args": ["--[no-]lint-skip-formatters"], "env_var": "PANTS_LINT_SKIP_FORMATTERS", - "help": "If true, skip running all formatters in check-only mode.\n\nFYI: when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `lint` where possible.", + "help": "If true, skip running all formatters in check-only mode.\n\nFYI: when running `/home/josh/work/scie-pants/dist/pants fmt lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `lint` where possible.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -51931,7 +51931,7 @@ "deprecation_active": false, "display_args": ["--[no-]lint-skip-fixers"], "env_var": "PANTS_LINT_SKIP_FIXERS", - "help": "If true, skip running all fixers in check-only mode.\n\nFYI: when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fix lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fix` when running `lint` where possible.", + "help": "If true, skip running all fixers in check-only mode.\n\nFYI: when running `/home/josh/work/scie-pants/dist/pants fix lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fix` when running `lint` where possible.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -52178,7 +52178,7 @@ "deprecation_active": false, "display_args": ["--mypy-lockfile="], "env_var": "PANTS_MYPY_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/python/typecheck/mypy/mypy.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=mypy`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/python/typecheck/mypy/mypy.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=mypy`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--mypy-lockfile"], @@ -52402,7 +52402,7 @@ "deprecation_active": false, "display_args": ["--mypy-extra-type-stubs-lockfile="], "env_var": "PANTS_MYPY_EXTRA_TYPE_STUBS_LOCKFILE", - "help": "Path to a lockfile for the option `[mypy].extra_type_stubs`.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this if you use `[mypy].extra_type_stubs`, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=mypy-extra-type-stubs`.", + "help": "Path to a lockfile for the option `[mypy].extra_type_stubs`.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this if you use `[mypy].extra_type_stubs`, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=mypy-extra-type-stubs`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--mypy-extra-type-stubs-lockfile"], @@ -52436,7 +52436,7 @@ "deprecation_active": false, "display_args": ["--[no-]mypy-skip"], "env_var": "PANTS_MYPY_SKIP", - "help": "If true, don't use MyPy when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 check`.", + "help": "If true, don't use MyPy when running `/home/josh/work/scie-pants/dist/pants check`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--mypy-skip", "--no-mypy-skip"], @@ -52502,7 +52502,7 @@ "deprecation_active": true, "display_args": ["--[no-]mypy-export"], "env_var": "PANTS_MYPY_EXPORT", - "help": "If true, export a virtual environment with MyPy when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with MyPy when running `/home/josh/work/scie-pants/dist/pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": "Use the export goal's --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.", "removal_version": "2.23.0.dev0", "scoped_cmd_line_args": ["--mypy-export", "--no-mypy-export"], @@ -52643,7 +52643,7 @@ "deprecation_active": false, "display_args": ["--mypy-protobuf-lockfile="], "env_var": "PANTS_MYPY_PROTOBUF_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/codegen/protobuf/python/mypy_protobuf.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=mypy-protobuf`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/codegen/protobuf/python/mypy_protobuf.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=mypy-protobuf`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--mypy-protobuf-lockfile"], @@ -53369,7 +53369,7 @@ "deprecation_active": false, "display_args": ["--protobuf-java-grpc-lockfile="], "env_var": "PANTS_PROTOBUF_JAVA_GRPC_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/codegen/protobuf/java/grpc-java.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=protobuf-java-grpc`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/codegen/protobuf/java/grpc-java.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=protobuf-java-grpc`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--protobuf-java-grpc-lockfile"], @@ -53891,7 +53891,7 @@ "deprecation_active": false, "display_args": ["--pylint-lockfile="], "env_var": "PANTS_PYLINT_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/python/lint/pylint/pylint.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=pylint`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/python/lint/pylint/pylint.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=pylint`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pylint-lockfile"], @@ -54083,7 +54083,7 @@ "deprecation_active": false, "display_args": ["--[no-]pylint-skip"], "env_var": "PANTS_PYLINT_SKIP", - "help": "If true, don't use Pylint when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Pylint when running `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pylint-skip", "--no-pylint-skip"], @@ -54149,7 +54149,7 @@ "deprecation_active": true, "display_args": ["--[no-]pylint-export"], "env_var": "PANTS_PYLINT_EXPORT", - "help": "If true, export a virtual environment with Pylint when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with Pylint when running `/home/josh/work/scie-pants/dist/pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": "Use the export goal's --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.", "removal_version": "2.23.0.dev0", "scoped_cmd_line_args": ["--pylint-export", "--no-pylint-export"], @@ -54290,7 +54290,7 @@ "deprecation_active": false, "display_args": ["--pyoxidizer-lockfile="], "env_var": "PANTS_PYOXIDIZER_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/python/packaging/pyoxidizer/pyoxidizer.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=pyoxidizer`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/python/packaging/pyoxidizer/pyoxidizer.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=pyoxidizer`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pyoxidizer-lockfile"], @@ -54496,7 +54496,7 @@ "deprecation_active": false, "display_args": ["--pytest-lockfile="], "env_var": "PANTS_PYTEST_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/python/subsystems/pytest.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=pytest`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/python/subsystems/pytest.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=pytest`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pytest-lockfile"], @@ -54783,7 +54783,7 @@ "deprecation_active": false, "display_args": ["--[no-]pytest-skip"], "env_var": "PANTS_PYTEST_SKIP", - "help": "If true, don't use Pytest when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 test`.", + "help": "If true, don't use Pytest when running `/home/josh/work/scie-pants/dist/pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pytest-skip", "--no-pytest-skip"], @@ -54817,7 +54817,7 @@ "deprecation_active": true, "display_args": ["--[no-]pytest-export"], "env_var": "PANTS_PYTEST_EXPORT", - "help": "If true, export a virtual environment with Pytest when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with Pytest when running `/home/josh/work/scie-pants/dist/pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": "Use the export goal's --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.", "removal_version": "2.23.0.dev0", "scoped_cmd_line_args": ["--pytest-export", "--no-pytest-export"], @@ -54977,7 +54977,7 @@ "--python-resolves=\"{'key1': val1, 'key2': val2, ...}\"" ], "env_var": "PANTS_PYTHON_RESOLVES", - "help": "A mapping of logical names to lockfile paths used in your project.\n\nMany organizations only need a single resolve for their whole project, which is a good default and often the simplest thing to do. However, you may need multiple resolves, such as if you use two conflicting versions of a requirement in your repository.\n\nIf you only need a single resolve, run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles` to generate the lockfile.\n\nIf you need multiple resolves:\n\n 1. Via this option, define multiple resolve names and their lockfile paths. The names should be meaningful to your repository, such as `data-science` or `pants-plugins`.\n 2. Set the default with `[python].default_resolve`.\n 3. Update your `python_requirement` targets with the `resolve` field to declare which resolve they should be available in. They default to `[python].default_resolve`, so you only need to update targets that you want in non-default resolves. (Often you'll set this via the `python_requirements` or `poetry_requirements` target generators)\n 4. Run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles` to generate the lockfiles. If the results aren't what you'd expect, adjust the prior step.\n 5. Update any targets like `python_source` / `python_sources`, `python_test` / `python_tests`, and `pex_binary` which need to set a non-default resolve with the `resolve` field.\n\nIf a target can work with multiple resolves, you can either use the `parametrize` mechanism or manually create a distinct target per resolve. See https://www.pantsbuild.org/v2.15/docs/targets for information about `parametrize`.\n\nFor example:\n\n python_sources(\n resolve=parametrize(\"data-science\", \"web-app\"),\n )\n\nYou can name the lockfile paths what you would like; Pants does not expect a certain file extension or location.\n\nOnly applies if `[python].enable_resolves` is true.", + "help": "A mapping of logical names to lockfile paths used in your project.\n\nMany organizations only need a single resolve for their whole project, which is a good default and often the simplest thing to do. However, you may need multiple resolves, such as if you use two conflicting versions of a requirement in your repository.\n\nIf you only need a single resolve, run `/home/josh/work/scie-pants/dist/pants generate-lockfiles` to generate the lockfile.\n\nIf you need multiple resolves:\n\n 1. Via this option, define multiple resolve names and their lockfile paths. The names should be meaningful to your repository, such as `data-science` or `pants-plugins`.\n 2. Set the default with `[python].default_resolve`.\n 3. Update your `python_requirement` targets with the `resolve` field to declare which resolve they should be available in. They default to `[python].default_resolve`, so you only need to update targets that you want in non-default resolves. (Often you'll set this via the `python_requirements` or `poetry_requirements` target generators)\n 4. Run `/home/josh/work/scie-pants/dist/pants generate-lockfiles` to generate the lockfiles. If the results aren't what you'd expect, adjust the prior step.\n 5. Update any targets like `python_source` / `python_sources`, `python_test` / `python_tests`, and `pex_binary` which need to set a non-default resolve with the `resolve` field.\n\nIf a target can work with multiple resolves, you can either use the `parametrize` mechanism or manually create a distinct target per resolve. See https://www.pantsbuild.org/v2.15/docs/targets for information about `parametrize`.\n\nFor example:\n\n python_sources(\n resolve=parametrize(\"data-science\", \"web-app\"),\n )\n\nYou can name the lockfile paths what you would like; Pants does not expect a certain file extension or location.\n\nOnly applies if `[python].enable_resolves` is true.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--python-resolves"], @@ -55594,7 +55594,7 @@ "display_args": ["--python-requirement-constraints="], "env_var": "PANTS_PYTHON_REQUIREMENT_CONSTRAINTS", "help": "When resolving third-party requirements for your own code (vs. tools you run), use this constraints file to determine which versions to use.\n\nMutually exclusive with `[python].enable_resolves`, which we generally recommend as an improvement over constraints file.\n\nSee https://pip.pypa.io/en/stable/user_guide/#constraints-files for more information on the format of constraint files and how constraints are applied in Pex and pip.\n\nThis only applies when resolving user requirements, rather than tools you run like Black and Pytest. To constrain tools, set `[tool].lockfile`, e.g. `[black].lockfile`.", - "removal_hint": "We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.\n\nTo migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles`.", + "removal_hint": "We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.\n\nTo migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `/home/josh/work/scie-pants/dist/pants generate-lockfiles`.", "removal_version": "3.0.0.dev0", "scoped_cmd_line_args": ["--python-requirement-constraints"], "target_field_name": null, @@ -55621,7 +55621,7 @@ "display_args": ["--[no-]python-resolve-all-constraints"], "env_var": "PANTS_PYTHON_RESOLVE_ALL_CONSTRAINTS", "help": "(Only relevant when using `[python].requirement_constraints.`) If enabled, when resolving requirements, Pants will first resolve your entire constraints file as a single global resolve. Then, if the code uses a subset of your constraints file, Pants will extract the relevant requirements from that global resolve so that only what's actually needed gets used. If disabled, Pants will not use a global resolve and will resolve each subset of your requirements independently.\n\nUsually this option should be enabled because it can result in far fewer resolves.", - "removal_hint": "We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.\n\nTo migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles`.", + "removal_hint": "We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.\n\nTo migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `/home/josh/work/scie-pants/dist/pants generate-lockfiles`.", "removal_version": "3.0.0.dev0", "scoped_cmd_line_args": [ "--python-resolve-all-constraints", @@ -55916,7 +55916,7 @@ "deprecation_active": false, "display_args": ["--python-infer-init-files="], "env_var": "PANTS_PYTHON_INFER_INIT_FILES", - "help": "Infer a target's dependencies on any `__init__.py` files in the packages it is located in (recursively upward in the directory structure).\n\nEven if this is set to `never` or `content_only`, Pants will still always include any ancestor `__init__.py` files in the sandbox. Only, they will not be \"proper\" dependencies, e.g. they will not show up in `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` and their own dependencies will not be used.\n\nBy default, Pants only adds a \"proper\" dependency if there is content in the `__init__.py` file. This makes sure that dependencies are added when likely necessary to build, while also avoiding adding unnecessary dependencies. While accurate, those unnecessary dependencies can complicate setting metadata like the `interpreter_constraints` and `resolve` fields.", + "help": "Infer a target's dependencies on any `__init__.py` files in the packages it is located in (recursively upward in the directory structure).\n\nEven if this is set to `never` or `content_only`, Pants will still always include any ancestor `__init__.py` files in the sandbox. Only, they will not be \"proper\" dependencies, e.g. they will not show up in `/home/josh/work/scie-pants/dist/pants dependencies` and their own dependencies will not be used.\n\nBy default, Pants only adds a \"proper\" dependency if there is content in the `__init__.py` file. This makes sure that dependencies are added when likely necessary to build, while also avoiding adding unnecessary dependencies. While accurate, those unnecessary dependencies can complicate setting metadata like the `interpreter_constraints` and `resolve` fields.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--python-infer-init-files"], @@ -56559,7 +56559,7 @@ "deprecation_active": false, "display_args": ["--pyupgrade-lockfile="], "env_var": "PANTS_PYUPGRADE_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/python/lint/pyupgrade/pyupgrade.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=pyupgrade`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/python/lint/pyupgrade/pyupgrade.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=pyupgrade`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pyupgrade-lockfile"], @@ -56652,7 +56652,7 @@ "deprecation_active": false, "display_args": ["--[no-]pyupgrade-skip"], "env_var": "PANTS_PYUPGRADE_SKIP", - "help": "If true, don't use pyupgrade when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use pyupgrade when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pyupgrade-skip", "--no-pyupgrade-skip"], @@ -56720,7 +56720,7 @@ "deprecation_active": true, "display_args": ["--[no-]pyupgrade-export"], "env_var": "PANTS_PYUPGRADE_EXPORT", - "help": "If true, export a virtual environment with pyupgrade when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with pyupgrade when running `/home/josh/work/scie-pants/dist/pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": "Use the export goal's --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.", "removal_version": "2.23.0.dev0", "scoped_cmd_line_args": [ @@ -56765,7 +56765,7 @@ "deprecation_active": false, "display_args": ["--[no-]regex-lint-skip"], "env_var": "PANTS_REGEX_LINT_SKIP", - "help": "If true, don't use regex-lint when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use regex-lint when running `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--regex-lint-skip", "--no-regex-lint-skip"], @@ -57514,7 +57514,7 @@ "deprecation_active": false, "display_args": ["--scalafmt-lockfile="], "env_var": "PANTS_SCALAFMT_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/scala/lint/scalafmt/scalafmt.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalafmt`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/scala/lint/scalafmt/scalafmt.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=scalafmt`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalafmt-lockfile"], @@ -57582,7 +57582,7 @@ "deprecation_active": false, "display_args": ["--[no-]scalafmt-skip"], "env_var": "PANTS_SCALAFMT_SKIP", - "help": "If true, don't use scalafmt when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use scalafmt when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalafmt-skip", "--no-scalafmt-skip"], @@ -57688,7 +57688,7 @@ "deprecation_active": false, "display_args": ["--scalapb-lockfile="], "env_var": "PANTS_SCALAPB_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/codegen/protobuf/scala/scalapbc.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalapb`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/codegen/protobuf/scala/scalapbc.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=scalapb`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalapb-lockfile"], @@ -57860,7 +57860,7 @@ "deprecation_active": false, "display_args": ["--scalatest-lockfile="], "env_var": "PANTS_SCALATEST_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/scala/subsystems/scalatest.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalatest`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/scala/subsystems/scalatest.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=scalatest`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalatest-lockfile"], @@ -57963,7 +57963,7 @@ "deprecation_active": false, "display_args": ["--[no-]scalatest-skip"], "env_var": "PANTS_SCALATEST_SKIP", - "help": "If true, don't use Scalatest when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 test`.", + "help": "If true, don't use Scalatest when running `/home/josh/work/scie-pants/dist/pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalatest-skip", "--no-scalatest-skip"], @@ -58387,7 +58387,7 @@ "deprecation_active": false, "display_args": ["--setuptools-lockfile="], "env_var": "PANTS_SETUPTOOLS_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/python/subsystems/setuptools.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=setuptools`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/python/subsystems/setuptools.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=setuptools`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--setuptools-lockfile"], @@ -58530,7 +58530,7 @@ "deprecation_active": false, "display_args": ["--setuptools-scm-lockfile="], "env_var": "PANTS_SETUPTOOLS_SCM_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/python/subsystems/setuptools_scm.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=setuptools-scm`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/python/subsystems/setuptools_scm.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=setuptools-scm`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--setuptools-scm-lockfile"], @@ -58976,7 +58976,7 @@ "deprecation_active": false, "display_args": ["--[no-]shellcheck-skip"], "env_var": "PANTS_SHELLCHECK_SKIP", - "help": "If true, don't use Shellcheck when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Shellcheck when running `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--shellcheck-skip", "--no-shellcheck-skip"], @@ -59278,7 +59278,7 @@ "deprecation_active": false, "display_args": ["--[no-]shfmt-skip"], "env_var": "PANTS_SHFMT_SKIP", - "help": "If true, don't use shfmt when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use shfmt when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--shfmt-skip", "--no-shfmt-skip"], @@ -59525,7 +59525,7 @@ "deprecation_active": false, "display_args": ["--[no-]shunit2-skip"], "env_var": "PANTS_SHUNIT2_SKIP", - "help": "If true, don't use shunit2 when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 test`.", + "help": "If true, don't use shunit2 when running `/home/josh/work/scie-pants/dist/pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--shunit2-skip", "--no-shunit2-skip"], @@ -59854,7 +59854,7 @@ "deprecation_active": false, "display_args": ["--[no-]spectral-skip"], "env_var": "PANTS_SPECTRAL_SKIP", - "help": "If true, don't use Spectral when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Spectral when running `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--spectral-skip", "--no-spectral-skip"], @@ -60301,7 +60301,7 @@ "deprecation_active": false, "display_args": ["--[no-]terraform-fmt-skip"], "env_var": "PANTS_TERRAFORM_FMT_SKIP", - "help": "If true, don't use `terraform fmt` when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use `terraform fmt` when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -60450,7 +60450,7 @@ "deprecation_active": false, "display_args": ["--terraform-hcl2-parser-lockfile="], "env_var": "PANTS_TERRAFORM_HCL2_PARSER_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/terraform/hcl2.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=terraform-hcl2-parser`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/terraform/hcl2.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=terraform-hcl2-parser`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--terraform-hcl2-parser-lockfile"], @@ -60494,7 +60494,7 @@ "deprecation_active": false, "display_args": ["--[no-]terraform-validate-skip"], "env_var": "PANTS_TERRAFORM_VALIDATE_SKIP", - "help": "If true, don't use `terraform validate` when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 check`.", + "help": "If true, don't use `terraform validate` when running `/home/josh/work/scie-pants/dist/pants check`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -61180,7 +61180,7 @@ "deprecation_active": false, "display_args": ["--twine-lockfile="], "env_var": "PANTS_TWINE_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/python/subsystems/twine.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=twine`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/python/subsystems/twine.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=twine`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--twine-lockfile"], @@ -61370,7 +61370,7 @@ "deprecation_active": false, "display_args": ["--[no-]twine-skip"], "env_var": "PANTS_TWINE_SKIP", - "help": "If true, don't use Twine when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 publish`.", + "help": "If true, don't use Twine when running `/home/josh/work/scie-pants/dist/pants publish`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--twine-skip", "--no-twine-skip"], @@ -61705,7 +61705,7 @@ "deprecation_active": false, "display_args": ["--yapf-lockfile="], "env_var": "PANTS_YAPF_LOCKFILE", - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/python/lint/yapf/yapf.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=yapf`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/python/lint/yapf/yapf.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=yapf`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--yapf-lockfile"], @@ -61863,7 +61863,7 @@ "deprecation_active": false, "display_args": ["--[no-]yapf-skip"], "env_var": "PANTS_YAPF_SKIP", - "help": "If true, don't use yapf when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use yapf when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--yapf-skip", "--no-yapf-skip"], @@ -61929,7 +61929,7 @@ "deprecation_active": true, "display_args": ["--[no-]yapf-export"], "env_var": "PANTS_YAPF_EXPORT", - "help": "If true, export a virtual environment with yapf when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with yapf when running `/home/josh/work/scie-pants/dist/pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": "Use the export goal's --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.", "removal_version": "2.23.0.dev0", "scoped_cmd_line_args": ["--yapf-export", "--no-yapf-export"], diff --git a/versioned_docs/version-2.15/reference/subsystems/add-trailing-comma.mdx b/versioned_docs/version-2.15/reference/subsystems/add-trailing-comma.mdx index 433857c3d..677874c56 100644 --- a/versioned_docs/version-2.15/reference/subsystems/add-trailing-comma.mdx +++ b/versioned_docs/version-2.15/reference/subsystems/add-trailing-comma.mdx @@ -25,7 +25,7 @@ Config section: `[add-trailing-comma]` default_repr={`False`} > -If true, don't use add-trailing-comma when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +If true, don't use add-trailing-comma when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. @@ -93,7 +93,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=add-trailing-comma`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=add-trailing-comma`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. @@ -135,7 +135,7 @@ The entry point for the tool. Generally you only want to use this option if the removal_hint={'Use the export goal\'s --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.'} > -If true, export a virtual environment with add-trailing-comma when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`. +If true, export a virtual environment with add-trailing-comma when running `/home/josh/work/scie-pants/dist/pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. diff --git a/versioned_docs/version-2.15/reference/subsystems/autoflake.mdx b/versioned_docs/version-2.15/reference/subsystems/autoflake.mdx index bffd1bb65..a1459db1a 100644 --- a/versioned_docs/version-2.15/reference/subsystems/autoflake.mdx +++ b/versioned_docs/version-2.15/reference/subsystems/autoflake.mdx @@ -25,7 +25,7 @@ Config section: `[autoflake]` default_repr={`False`} > -If true, don't use Autoflake when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +If true, don't use Autoflake when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. @@ -93,7 +93,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=autoflake`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=autoflake`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. @@ -135,7 +135,7 @@ The entry point for the tool. Generally you only want to use this option if the removal_hint={'Use the export goal\'s --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.'} > -If true, export a virtual environment with Autoflake when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`. +If true, export a virtual environment with Autoflake when running `/home/josh/work/scie-pants/dist/pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. diff --git a/versioned_docs/version-2.15/reference/subsystems/bandit.mdx b/versioned_docs/version-2.15/reference/subsystems/bandit.mdx index 6de53d7c8..926e10745 100644 --- a/versioned_docs/version-2.15/reference/subsystems/bandit.mdx +++ b/versioned_docs/version-2.15/reference/subsystems/bandit.mdx @@ -25,7 +25,7 @@ Config section: `[bandit]` default_repr={`False`} > -If true, don't use Bandit when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +If true, don't use Bandit when running `/home/josh/work/scie-pants/dist/pants lint`. @@ -81,7 +81,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=bandit`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=bandit`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. @@ -135,7 +135,7 @@ Path to a Bandit YAML config file (https://bandit.readthedocs.io/en/latest/confi removal_hint={'Use the export goal\'s --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.'} > -If true, export a virtual environment with Bandit when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`. +If true, export a virtual environment with Bandit when running `/home/josh/work/scie-pants/dist/pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. diff --git a/versioned_docs/version-2.15/reference/subsystems/black.mdx b/versioned_docs/version-2.15/reference/subsystems/black.mdx index a590e1602..38545f6b9 100644 --- a/versioned_docs/version-2.15/reference/subsystems/black.mdx +++ b/versioned_docs/version-2.15/reference/subsystems/black.mdx @@ -25,7 +25,7 @@ Config section: `[black]` default_repr={`False`} > -If true, don't use Black when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +If true, don't use Black when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. @@ -93,7 +93,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=black`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=black`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. @@ -163,7 +163,7 @@ Use `[black].config` instead if your config is in a non-standard location. removal_hint={'Use the export goal\'s --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.'} > -If true, export a virtual environment with Black when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`. +If true, export a virtual environment with Black when running `/home/josh/work/scie-pants/dist/pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. diff --git a/versioned_docs/version-2.15/reference/subsystems/buf.mdx b/versioned_docs/version-2.15/reference/subsystems/buf.mdx index e74526775..abd877aa4 100644 --- a/versioned_docs/version-2.15/reference/subsystems/buf.mdx +++ b/versioned_docs/version-2.15/reference/subsystems/buf.mdx @@ -25,7 +25,7 @@ Config section: `[buf]` default_repr={`False`} > -If true, don't use Buf when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +If true, don't use Buf when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. @@ -37,7 +37,7 @@ If true, don't use Buf when running `/home/josh/work/scie-pants/dist/scie-p default_repr={`False`} > -If true, don't use Buf when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +If true, don't use Buf when running `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.15/reference/subsystems/build-deprecations-fixer.mdx b/versioned_docs/version-2.15/reference/subsystems/build-deprecations-fixer.mdx index f7df0b70e..9c088cf04 100644 --- a/versioned_docs/version-2.15/reference/subsystems/build-deprecations-fixer.mdx +++ b/versioned_docs/version-2.15/reference/subsystems/build-deprecations-fixer.mdx @@ -27,7 +27,7 @@ Config section: `[build-deprecations-fixer]` -If true, don't use BUILD Deprecations Fixer when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fix`. +If true, don't use BUILD Deprecations Fixer when running `/home/josh/work/scie-pants/dist/pants fix`. diff --git a/versioned_docs/version-2.15/reference/subsystems/buildifier.mdx b/versioned_docs/version-2.15/reference/subsystems/buildifier.mdx index 21664c1b5..ffd8e7f1d 100644 --- a/versioned_docs/version-2.15/reference/subsystems/buildifier.mdx +++ b/versioned_docs/version-2.15/reference/subsystems/buildifier.mdx @@ -32,7 +32,7 @@ Config section: `[buildifier]` default_repr={`False`} > -If true, don't use Buildifier when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt`. +If true, don't use Buildifier when running `/home/josh/work/scie-pants/dist/pants fmt`. diff --git a/versioned_docs/version-2.15/reference/subsystems/cli.mdx b/versioned_docs/version-2.15/reference/subsystems/cli.mdx index 3612faf24..8c2253b82 100644 --- a/versioned_docs/version-2.15/reference/subsystems/cli.mdx +++ b/versioned_docs/version-2.15/reference/subsystems/cli.mdx @@ -35,7 +35,7 @@ green = "fmt lint check" all-changed = "--changed-since=HEAD --changed-dependees=transitive" ``` -This would allow you to run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 green all-changed`, which is shorthand for `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt lint check --changed-since=HEAD --changed-dependees=transitive`. +This would allow you to run `/home/josh/work/scie-pants/dist/pants green all-changed`, which is shorthand for `/home/josh/work/scie-pants/dist/pants fmt lint check --changed-since=HEAD --changed-dependees=transitive`. Notice: this option must be placed in a config file (e.g. `pants.toml` or `pantsrc`) to have any effect. diff --git a/versioned_docs/version-2.15/reference/subsystems/coverage-py.mdx b/versioned_docs/version-2.15/reference/subsystems/coverage-py.mdx index 218c856b0..0ab6ce1fd 100644 --- a/versioned_docs/version-2.15/reference/subsystems/coverage-py.mdx +++ b/versioned_docs/version-2.15/reference/subsystems/coverage-py.mdx @@ -130,7 +130,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=coverage-py`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=coverage-py`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.15/reference/subsystems/debugpy.mdx b/versioned_docs/version-2.15/reference/subsystems/debugpy.mdx index 40cb26bf5..e92f1d029 100644 --- a/versioned_docs/version-2.15/reference/subsystems/debugpy.mdx +++ b/versioned_docs/version-2.15/reference/subsystems/debugpy.mdx @@ -81,7 +81,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=debugpy`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=debugpy`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.15/reference/subsystems/docformatter.mdx b/versioned_docs/version-2.15/reference/subsystems/docformatter.mdx index 2d4489f42..9bc461514 100644 --- a/versioned_docs/version-2.15/reference/subsystems/docformatter.mdx +++ b/versioned_docs/version-2.15/reference/subsystems/docformatter.mdx @@ -25,7 +25,7 @@ Config section: `[docformatter]` default_repr={`False`} > -If true, don't use docformatter when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +If true, don't use docformatter when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. @@ -93,7 +93,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=docformatter`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=docformatter`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. @@ -135,7 +135,7 @@ The entry point for the tool. Generally you only want to use this option if the removal_hint={'Use the export goal\'s --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.'} > -If true, export a virtual environment with docformatter when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`. +If true, export a virtual environment with docformatter when running `/home/josh/work/scie-pants/dist/pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. diff --git a/versioned_docs/version-2.15/reference/subsystems/docker.mdx b/versioned_docs/version-2.15/reference/subsystems/docker.mdx index f3c42426d..de260e4a3 100644 --- a/versioned_docs/version-2.15/reference/subsystems/docker.mdx +++ b/versioned_docs/version-2.15/reference/subsystems/docker.mdx @@ -166,7 +166,7 @@ Additional arguments to use for `docker run` invocations. Example: ``` -$ /home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 run --docker-run-args="-p 127.0.0.1:80:8080/tcp --name demo" src/example:image -- [image entrypoint args] +$ /home/josh/work/scie-pants/dist/pants run --docker-run-args="-p 127.0.0.1:80:8080/tcp --name demo" src/example:image -- [image entrypoint args] ``` To provide the top-level options to the `docker` client, use `[docker].env_vars` to configure the [Environment variables](https://docs.docker.com/engine/reference/commandline/cli/#environment-variables) as appropriate. diff --git a/versioned_docs/version-2.15/reference/subsystems/dockerfile-parser.mdx b/versioned_docs/version-2.15/reference/subsystems/dockerfile-parser.mdx index 2a68f484c..96304614b 100644 --- a/versioned_docs/version-2.15/reference/subsystems/dockerfile-parser.mdx +++ b/versioned_docs/version-2.15/reference/subsystems/dockerfile-parser.mdx @@ -71,7 +71,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=dockerfile-parser`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=dockerfile-parser`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.15/reference/subsystems/flake8.mdx b/versioned_docs/version-2.15/reference/subsystems/flake8.mdx index 1387d1317..334de328b 100644 --- a/versioned_docs/version-2.15/reference/subsystems/flake8.mdx +++ b/versioned_docs/version-2.15/reference/subsystems/flake8.mdx @@ -25,7 +25,7 @@ Config section: `[flake8]` default_repr={`False`} > -If true, don't use Flake8 when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +If true, don't use Flake8 when running `/home/josh/work/scie-pants/dist/pants lint`. @@ -81,7 +81,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=flake8`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=flake8`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. @@ -194,7 +194,7 @@ Tip: it's often helpful to define a dedicated 'resolve' via `[pyt removal_hint={'Use the export goal\'s --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.'} > -If true, export a virtual environment with Flake8 when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`. +If true, export a virtual environment with Flake8 when running `/home/josh/work/scie-pants/dist/pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. diff --git a/versioned_docs/version-2.15/reference/subsystems/go-test.mdx b/versioned_docs/version-2.15/reference/subsystems/go-test.mdx index 07bb83ad0..f13b3b12c 100644 --- a/versioned_docs/version-2.15/reference/subsystems/go-test.mdx +++ b/versioned_docs/version-2.15/reference/subsystems/go-test.mdx @@ -70,7 +70,7 @@ If true, then convert coverage reports to HTML format and write a `coverage.html default_repr={`False`} > -If true, don't use Go test binary when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 test`. +If true, don't use Go test binary when running `/home/josh/work/scie-pants/dist/pants test`. diff --git a/versioned_docs/version-2.15/reference/subsystems/gofmt.mdx b/versioned_docs/version-2.15/reference/subsystems/gofmt.mdx index 1114d4e84..deddbc716 100644 --- a/versioned_docs/version-2.15/reference/subsystems/gofmt.mdx +++ b/versioned_docs/version-2.15/reference/subsystems/gofmt.mdx @@ -25,7 +25,7 @@ Config section: `[gofmt]` default_repr={`False`} > -If true, don't use gofmt when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +If true, don't use gofmt when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.15/reference/subsystems/google-java-format.mdx b/versioned_docs/version-2.15/reference/subsystems/google-java-format.mdx index 0892e77fc..5edf320d6 100644 --- a/versioned_docs/version-2.15/reference/subsystems/google-java-format.mdx +++ b/versioned_docs/version-2.15/reference/subsystems/google-java-format.mdx @@ -25,7 +25,7 @@ Config section: `[google-java-format]` default_repr={`False`} > -If true, don't use Google Java Format when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +If true, don't use Google Java Format when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. @@ -79,7 +79,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/java/lint/google_java_format/google_java_format.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=google-java-format`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=google-java-format`. diff --git a/versioned_docs/version-2.15/reference/subsystems/hadolint.mdx b/versioned_docs/version-2.15/reference/subsystems/hadolint.mdx index a8a02b575..e7d3278d9 100644 --- a/versioned_docs/version-2.15/reference/subsystems/hadolint.mdx +++ b/versioned_docs/version-2.15/reference/subsystems/hadolint.mdx @@ -25,7 +25,7 @@ Config section: `[hadolint]` default_repr={`False`} > -If true, don't use Hadolint when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +If true, don't use Hadolint when running `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.15/reference/subsystems/helm-k8s-parser.mdx b/versioned_docs/version-2.15/reference/subsystems/helm-k8s-parser.mdx index d6d061bd8..83779942d 100644 --- a/versioned_docs/version-2.15/reference/subsystems/helm-k8s-parser.mdx +++ b/versioned_docs/version-2.15/reference/subsystems/helm-k8s-parser.mdx @@ -71,7 +71,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=helm-k8s-parser`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=helm-k8s-parser`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.15/reference/subsystems/helm-post-renderer.mdx b/versioned_docs/version-2.15/reference/subsystems/helm-post-renderer.mdx index ce6340e50..a78e0bacd 100644 --- a/versioned_docs/version-2.15/reference/subsystems/helm-post-renderer.mdx +++ b/versioned_docs/version-2.15/reference/subsystems/helm-post-renderer.mdx @@ -71,7 +71,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=helm-post-renderer`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=helm-post-renderer`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.15/reference/subsystems/helm-unittest.mdx b/versioned_docs/version-2.15/reference/subsystems/helm-unittest.mdx index 75587d38a..c9b34ac15 100644 --- a/versioned_docs/version-2.15/reference/subsystems/helm-unittest.mdx +++ b/versioned_docs/version-2.15/reference/subsystems/helm-unittest.mdx @@ -50,7 +50,7 @@ Output type used for the test report. default_repr={`False`} > -If true, don't use helmunittestsubsystem when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 test`. +If true, don't use helmunittestsubsystem when running `/home/josh/work/scie-pants/dist/pants test`. diff --git a/versioned_docs/version-2.15/reference/subsystems/ipython.mdx b/versioned_docs/version-2.15/reference/subsystems/ipython.mdx index 99e33b761..2c8a9b4f5 100644 --- a/versioned_docs/version-2.15/reference/subsystems/ipython.mdx +++ b/versioned_docs/version-2.15/reference/subsystems/ipython.mdx @@ -59,7 +59,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=ipython`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=ipython`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.15/reference/subsystems/isort.mdx b/versioned_docs/version-2.15/reference/subsystems/isort.mdx index fa6e287e1..e600770ed 100644 --- a/versioned_docs/version-2.15/reference/subsystems/isort.mdx +++ b/versioned_docs/version-2.15/reference/subsystems/isort.mdx @@ -25,7 +25,7 @@ Config section: `[isort]` default_repr={`False`} > -If true, don't use isort when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +If true, don't use isort when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. @@ -93,7 +93,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=isort`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=isort`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. @@ -165,7 +165,7 @@ Use `[isort].config` instead if your config is in a non-standard location. removal_hint={'Use the export goal\'s --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.'} > -If true, export a virtual environment with isort when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`. +If true, export a virtual environment with isort when running `/home/josh/work/scie-pants/dist/pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. diff --git a/versioned_docs/version-2.15/reference/subsystems/junit.mdx b/versioned_docs/version-2.15/reference/subsystems/junit.mdx index fa924d599..5ca9b3422 100644 --- a/versioned_docs/version-2.15/reference/subsystems/junit.mdx +++ b/versioned_docs/version-2.15/reference/subsystems/junit.mdx @@ -37,7 +37,7 @@ Arguments to pass directly to JUnit, e.g. `--junit-args='--disable-ansi-colors'` default_repr={`False`} > -If true, don't use JUnit when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 test`. +If true, don't use JUnit when running `/home/josh/work/scie-pants/dist/pants test`. @@ -79,7 +79,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/jvm/test/junit.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=junit`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=junit`. diff --git a/versioned_docs/version-2.15/reference/subsystems/ktlint.mdx b/versioned_docs/version-2.15/reference/subsystems/ktlint.mdx index 74b45fddf..b7f831142 100644 --- a/versioned_docs/version-2.15/reference/subsystems/ktlint.mdx +++ b/versioned_docs/version-2.15/reference/subsystems/ktlint.mdx @@ -25,7 +25,7 @@ Config section: `[ktlint]` default_repr={`False`} > -If true, don't use Ktlint when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +If true, don't use Ktlint when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. @@ -67,7 +67,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/kotlin/lint/ktlint/ktlint.lock for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=ktlint`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=ktlint`. diff --git a/versioned_docs/version-2.15/reference/subsystems/lambdex.mdx b/versioned_docs/version-2.15/reference/subsystems/lambdex.mdx index 7a7add102..e365eb79d 100644 --- a/versioned_docs/version-2.15/reference/subsystems/lambdex.mdx +++ b/versioned_docs/version-2.15/reference/subsystems/lambdex.mdx @@ -71,7 +71,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=lambdex`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=lambdex`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.15/reference/subsystems/mypy-protobuf.mdx b/versioned_docs/version-2.15/reference/subsystems/mypy-protobuf.mdx index 716d554d2..0a13d34e7 100644 --- a/versioned_docs/version-2.15/reference/subsystems/mypy-protobuf.mdx +++ b/versioned_docs/version-2.15/reference/subsystems/mypy-protobuf.mdx @@ -71,7 +71,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=mypy-protobuf`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=mypy-protobuf`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.15/reference/subsystems/mypy.mdx b/versioned_docs/version-2.15/reference/subsystems/mypy.mdx index b0a72526b..438c5c4d7 100644 --- a/versioned_docs/version-2.15/reference/subsystems/mypy.mdx +++ b/versioned_docs/version-2.15/reference/subsystems/mypy.mdx @@ -25,7 +25,7 @@ Config section: `[mypy]` default_repr={`False`} > -If true, don't use MyPy when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 check`. +If true, don't use MyPy when running `/home/josh/work/scie-pants/dist/pants check`. @@ -93,7 +93,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=mypy`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=mypy`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. @@ -197,7 +197,7 @@ Path to a lockfile for the option `[mypy].extra_type_stubs`. Set to the string `` to opt out of using a lockfile. We do not recommend this if you use `[mypy].extra_type_stubs`, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=mypy-extra-type-stubs`. +To use a lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=mypy-extra-type-stubs`. @@ -213,7 +213,7 @@ To use a lockfile, set this option to a file path relative to the build root, th removal_hint={'Use the export goal\'s --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.'} > -If true, export a virtual environment with MyPy when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`. +If true, export a virtual environment with MyPy when running `/home/josh/work/scie-pants/dist/pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. diff --git a/versioned_docs/version-2.15/reference/subsystems/protobuf-java-grpc.mdx b/versioned_docs/version-2.15/reference/subsystems/protobuf-java-grpc.mdx index 7430cc5f9..7513e4554 100644 --- a/versioned_docs/version-2.15/reference/subsystems/protobuf-java-grpc.mdx +++ b/versioned_docs/version-2.15/reference/subsystems/protobuf-java-grpc.mdx @@ -57,7 +57,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/codegen/protobuf/java/grpc-java.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=protobuf-java-grpc`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=protobuf-java-grpc`. diff --git a/versioned_docs/version-2.15/reference/subsystems/pylint.mdx b/versioned_docs/version-2.15/reference/subsystems/pylint.mdx index 020b25983..a7760c89e 100644 --- a/versioned_docs/version-2.15/reference/subsystems/pylint.mdx +++ b/versioned_docs/version-2.15/reference/subsystems/pylint.mdx @@ -25,7 +25,7 @@ Config section: `[pylint]` default_repr={`False`} > -If true, don't use Pylint when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +If true, don't use Pylint when running `/home/josh/work/scie-pants/dist/pants lint`. @@ -81,7 +81,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=pylint`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=pylint`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. @@ -173,7 +173,7 @@ Tip: it's often helpful to define a dedicated 'resolve' via `[pyt removal_hint={'Use the export goal\'s --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.'} > -If true, export a virtual environment with Pylint when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`. +If true, export a virtual environment with Pylint when running `/home/josh/work/scie-pants/dist/pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. diff --git a/versioned_docs/version-2.15/reference/subsystems/pyoxidizer.mdx b/versioned_docs/version-2.15/reference/subsystems/pyoxidizer.mdx index de6d37368..19baf2b36 100644 --- a/versioned_docs/version-2.15/reference/subsystems/pyoxidizer.mdx +++ b/versioned_docs/version-2.15/reference/subsystems/pyoxidizer.mdx @@ -83,7 +83,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=pyoxidizer`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=pyoxidizer`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.15/reference/subsystems/pytest.mdx b/versioned_docs/version-2.15/reference/subsystems/pytest.mdx index 3352617f0..ae782ee83 100644 --- a/versioned_docs/version-2.15/reference/subsystems/pytest.mdx +++ b/versioned_docs/version-2.15/reference/subsystems/pytest.mdx @@ -51,7 +51,7 @@ NOTE: Enabling `pytest-xdist` can cause high-level scoped fixtures (for example default_repr={`False`} > -If true, don't use Pytest when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 test`. +If true, don't use Pytest when running `/home/josh/work/scie-pants/dist/pants test`. @@ -95,7 +95,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=pytest`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=pytest`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. @@ -187,7 +187,7 @@ Use `[pytest].config` instead if your config is in a non-standard location. removal_hint={'Use the export goal\'s --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.'} > -If true, export a virtual environment with Pytest when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`. +If true, export a virtual environment with Pytest when running `/home/josh/work/scie-pants/dist/pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. diff --git a/versioned_docs/version-2.15/reference/subsystems/python-infer.mdx b/versioned_docs/version-2.15/reference/subsystems/python-infer.mdx index 3d78de082..5f89c9c2a 100644 --- a/versioned_docs/version-2.15/reference/subsystems/python-infer.mdx +++ b/versioned_docs/version-2.15/reference/subsystems/python-infer.mdx @@ -94,7 +94,7 @@ If --assets is True, treat valid-looking strings with at least this many forward Infer a target's dependencies on any `__init__.py` files in the packages it is located in (recursively upward in the directory structure). -Even if this is set to `never` or `content_only`, Pants will still always include any ancestor `__init__.py` files in the sandbox. Only, they will not be "proper" dependencies, e.g. they will not show up in `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` and their own dependencies will not be used. +Even if this is set to `never` or `content_only`, Pants will still always include any ancestor `__init__.py` files in the sandbox. Only, they will not be "proper" dependencies, e.g. they will not show up in `/home/josh/work/scie-pants/dist/pants dependencies` and their own dependencies will not be used. By default, Pants only adds a "proper" dependency if there is content in the `__init__.py` file. This makes sure that dependencies are added when likely necessary to build, while also avoiding adding unnecessary dependencies. While accurate, those unnecessary dependencies can complicate setting metadata like the `interpreter_constraints` and `resolve` fields. diff --git a/versioned_docs/version-2.15/reference/subsystems/python.mdx b/versioned_docs/version-2.15/reference/subsystems/python.mdx index f6d3454f9..d9db86f43 100644 --- a/versioned_docs/version-2.15/reference/subsystems/python.mdx +++ b/versioned_docs/version-2.15/reference/subsystems/python.mdx @@ -95,14 +95,14 @@ A mapping of logical names to lockfile paths used in your project. Many organizations only need a single resolve for their whole project, which is a good default and often the simplest thing to do. However, you may need multiple resolves, such as if you use two conflicting versions of a requirement in your repository. -If you only need a single resolve, run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles` to generate the lockfile. +If you only need a single resolve, run `/home/josh/work/scie-pants/dist/pants generate-lockfiles` to generate the lockfile. If you need multiple resolves: 1. Via this option, define multiple resolve names and their lockfile paths. The names should be meaningful to your repository, such as `data-science` or `pants-plugins`. 2. Set the default with `[python].default_resolve`. 3. Update your `python_requirement` targets with the `resolve` field to declare which resolve they should be available in. They default to `[python].default_resolve`, so you only need to update targets that you want in non-default resolves. (Often you'll set this via the `python_requirements` or `poetry_requirements` target generators) -4. Run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles` to generate the lockfiles. If the results aren't what you'd expect, adjust the prior step. +4. Run `/home/josh/work/scie-pants/dist/pants generate-lockfiles` to generate the lockfiles. If the results aren't what you'd expect, adjust the prior step. 5. Update any targets like `python_source` / `python_sources`, `python_test` / `python_tests`, and `pex_binary` which need to set a non-default resolve with the `resolve` field. If a target can work with multiple resolves, you can either use the `parametrize` mechanism or manually create a distinct target per resolve. See https://www.pantsbuild.org/v2.15/docs/targets for information about `parametrize`. @@ -375,7 +375,7 @@ If another targets address is in conflict with the created lockfile target, it w env_repr='PANTS_PYTHON_REQUIREMENT_CONSTRAINTS' default_repr={`None`} removal_version='3.0.0.dev0' - removal_hint={'We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.

To migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles`.'} + removal_hint={'We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.

To migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `/home/josh/work/scie-pants/dist/pants generate-lockfiles`.'} > When resolving third-party requirements for your own code (vs. tools you run), use this constraints file to determine which versions to use. @@ -395,7 +395,7 @@ This only applies when resolving user requirements, rather than tools you run li env_repr='PANTS_PYTHON_RESOLVE_ALL_CONSTRAINTS' default_repr={`True`} removal_version='3.0.0.dev0' - removal_hint={'We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.

To migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles`.'} + removal_hint={'We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.

To migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `/home/josh/work/scie-pants/dist/pants generate-lockfiles`.'} > (Only relevant when using `[python].requirement_constraints.`) If enabled, when resolving requirements, Pants will first resolve your entire constraints file as a single global resolve. Then, if the code uses a subset of your constraints file, Pants will extract the relevant requirements from that global resolve so that only what's actually needed gets used. If disabled, Pants will not use a global resolve and will resolve each subset of your requirements independently. diff --git a/versioned_docs/version-2.15/reference/subsystems/pyupgrade.mdx b/versioned_docs/version-2.15/reference/subsystems/pyupgrade.mdx index 2ef5e02ab..c56380bb0 100644 --- a/versioned_docs/version-2.15/reference/subsystems/pyupgrade.mdx +++ b/versioned_docs/version-2.15/reference/subsystems/pyupgrade.mdx @@ -25,7 +25,7 @@ Config section: `[pyupgrade]` default_repr={`False`} > -If true, don't use pyupgrade when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +If true, don't use pyupgrade when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. @@ -93,7 +93,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=pyupgrade`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=pyupgrade`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. @@ -135,7 +135,7 @@ The entry point for the tool. Generally you only want to use this option if the removal_hint={'Use the export goal\'s --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.'} > -If true, export a virtual environment with pyupgrade when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`. +If true, export a virtual environment with pyupgrade when running `/home/josh/work/scie-pants/dist/pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. diff --git a/versioned_docs/version-2.15/reference/subsystems/regex-lint.mdx b/versioned_docs/version-2.15/reference/subsystems/regex-lint.mdx index 9182dfa5f..f3b97fdf0 100644 --- a/versioned_docs/version-2.15/reference/subsystems/regex-lint.mdx +++ b/versioned_docs/version-2.15/reference/subsystems/regex-lint.mdx @@ -29,7 +29,7 @@ Config section: `[regex-lint]` default_repr={`False`} > -If true, don't use regex-lint when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +If true, don't use regex-lint when running `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.15/reference/subsystems/scalafmt.mdx b/versioned_docs/version-2.15/reference/subsystems/scalafmt.mdx index 51896998c..82b4006d6 100644 --- a/versioned_docs/version-2.15/reference/subsystems/scalafmt.mdx +++ b/versioned_docs/version-2.15/reference/subsystems/scalafmt.mdx @@ -25,7 +25,7 @@ Config section: `[scalafmt]` default_repr={`False`} > -If true, don't use scalafmt when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +If true, don't use scalafmt when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. @@ -67,7 +67,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/scala/lint/scalafmt/scalafmt.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalafmt`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=scalafmt`. diff --git a/versioned_docs/version-2.15/reference/subsystems/scalapb.mdx b/versioned_docs/version-2.15/reference/subsystems/scalapb.mdx index 09e4d7bef..f17f5c3b8 100644 --- a/versioned_docs/version-2.15/reference/subsystems/scalapb.mdx +++ b/versioned_docs/version-2.15/reference/subsystems/scalapb.mdx @@ -69,7 +69,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/codegen/protobuf/scala/scalapbc.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalapb`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=scalapb`. diff --git a/versioned_docs/version-2.15/reference/subsystems/scalatest.mdx b/versioned_docs/version-2.15/reference/subsystems/scalatest.mdx index 052b865da..20cc9c555 100644 --- a/versioned_docs/version-2.15/reference/subsystems/scalatest.mdx +++ b/versioned_docs/version-2.15/reference/subsystems/scalatest.mdx @@ -39,7 +39,7 @@ See https://www.scalatest.org/user_guide/using_the_runner for supported argument default_repr={`False`} > -If true, don't use Scalatest when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 test`. +If true, don't use Scalatest when running `/home/josh/work/scie-pants/dist/pants test`. @@ -81,7 +81,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.15.2/src/python/pants/backend/scala/subsystems/scalatest.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalatest`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants jvm-generate-lockfiles --resolve=scalatest`. diff --git a/versioned_docs/version-2.15/reference/subsystems/setuptools-scm.mdx b/versioned_docs/version-2.15/reference/subsystems/setuptools-scm.mdx index 8b79aa66c..5109d4704 100644 --- a/versioned_docs/version-2.15/reference/subsystems/setuptools-scm.mdx +++ b/versioned_docs/version-2.15/reference/subsystems/setuptools-scm.mdx @@ -71,7 +71,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=setuptools-scm`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=setuptools-scm`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.15/reference/subsystems/setuptools.mdx b/versioned_docs/version-2.15/reference/subsystems/setuptools.mdx index 876eba94f..ce1596f84 100644 --- a/versioned_docs/version-2.15/reference/subsystems/setuptools.mdx +++ b/versioned_docs/version-2.15/reference/subsystems/setuptools.mdx @@ -59,7 +59,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=setuptools`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=setuptools`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.15/reference/subsystems/shellcheck.mdx b/versioned_docs/version-2.15/reference/subsystems/shellcheck.mdx index fd90dd917..e143719aa 100644 --- a/versioned_docs/version-2.15/reference/subsystems/shellcheck.mdx +++ b/versioned_docs/version-2.15/reference/subsystems/shellcheck.mdx @@ -25,7 +25,7 @@ Config section: `[shellcheck]` default_repr={`False`} > -If true, don't use Shellcheck when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +If true, don't use Shellcheck when running `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.15/reference/subsystems/shfmt.mdx b/versioned_docs/version-2.15/reference/subsystems/shfmt.mdx index 98f4003f1..f47aefa5d 100644 --- a/versioned_docs/version-2.15/reference/subsystems/shfmt.mdx +++ b/versioned_docs/version-2.15/reference/subsystems/shfmt.mdx @@ -25,7 +25,7 @@ Config section: `[shfmt]` default_repr={`False`} > -If true, don't use shfmt when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +If true, don't use shfmt when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.15/reference/subsystems/shunit2.mdx b/versioned_docs/version-2.15/reference/subsystems/shunit2.mdx index 3734eec9f..fceab0fc1 100644 --- a/versioned_docs/version-2.15/reference/subsystems/shunit2.mdx +++ b/versioned_docs/version-2.15/reference/subsystems/shunit2.mdx @@ -25,7 +25,7 @@ Config section: `[shunit2]` default_repr={`False`} > -If true, don't use shunit2 when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 test`. +If true, don't use shunit2 when running `/home/josh/work/scie-pants/dist/pants test`. diff --git a/versioned_docs/version-2.15/reference/subsystems/spectral.mdx b/versioned_docs/version-2.15/reference/subsystems/spectral.mdx index 7d020f831..b1ca87595 100644 --- a/versioned_docs/version-2.15/reference/subsystems/spectral.mdx +++ b/versioned_docs/version-2.15/reference/subsystems/spectral.mdx @@ -25,7 +25,7 @@ Config section: `[spectral]` default_repr={`False`} > -If true, don't use Spectral when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +If true, don't use Spectral when running `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.15/reference/subsystems/terraform-fmt.mdx b/versioned_docs/version-2.15/reference/subsystems/terraform-fmt.mdx index a846d1f40..6082dec1a 100644 --- a/versioned_docs/version-2.15/reference/subsystems/terraform-fmt.mdx +++ b/versioned_docs/version-2.15/reference/subsystems/terraform-fmt.mdx @@ -25,7 +25,7 @@ Config section: `[terraform-fmt]` default_repr={`False`} > -If true, don't use `terraform fmt` when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +If true, don't use `terraform fmt` when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.15/reference/subsystems/terraform-hcl2-parser.mdx b/versioned_docs/version-2.15/reference/subsystems/terraform-hcl2-parser.mdx index 290142722..75c22b88f 100644 --- a/versioned_docs/version-2.15/reference/subsystems/terraform-hcl2-parser.mdx +++ b/versioned_docs/version-2.15/reference/subsystems/terraform-hcl2-parser.mdx @@ -71,7 +71,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=terraform-hcl2-parser`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=terraform-hcl2-parser`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.15/reference/subsystems/terraform-validate.mdx b/versioned_docs/version-2.15/reference/subsystems/terraform-validate.mdx index 05288ff5d..8b679e12f 100644 --- a/versioned_docs/version-2.15/reference/subsystems/terraform-validate.mdx +++ b/versioned_docs/version-2.15/reference/subsystems/terraform-validate.mdx @@ -25,7 +25,7 @@ Config section: `[terraform-validate]` default_repr={`False`} > -If true, don't use `terraform validate` when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 check`. +If true, don't use `terraform validate` when running `/home/josh/work/scie-pants/dist/pants check`. diff --git a/versioned_docs/version-2.15/reference/subsystems/twine.mdx b/versioned_docs/version-2.15/reference/subsystems/twine.mdx index a28203fb6..25516aa95 100644 --- a/versioned_docs/version-2.15/reference/subsystems/twine.mdx +++ b/versioned_docs/version-2.15/reference/subsystems/twine.mdx @@ -25,7 +25,7 @@ Config section: `[twine]` default_repr={`False`} > -If true, don't use Twine when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 publish`. +If true, don't use Twine when running `/home/josh/work/scie-pants/dist/pants publish`. @@ -93,7 +93,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=twine`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=twine`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.15/reference/subsystems/yapf.mdx b/versioned_docs/version-2.15/reference/subsystems/yapf.mdx index ec0a12c5f..3d8acfbfc 100644 --- a/versioned_docs/version-2.15/reference/subsystems/yapf.mdx +++ b/versioned_docs/version-2.15/reference/subsystems/yapf.mdx @@ -25,7 +25,7 @@ Config section: `[yapf]` default_repr={`False`} > -If true, don't use yapf when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +If true, don't use yapf when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. @@ -95,7 +95,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=yapf`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `/home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=yapf`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. @@ -165,7 +165,7 @@ Use `[yapf].config` instead if your config is in a non-standard location. removal_hint={'Use the export goal\'s --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.'} > -If true, export a virtual environment with yapf when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 export`. +If true, export a virtual environment with yapf when running `/home/josh/work/scie-pants/dist/pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. diff --git a/versioned_docs/version-2.15/reference/targets/archive.mdx b/versioned_docs/version-2.15/reference/targets/archive.mdx index eee2b5712..801685458 100644 --- a/versioned_docs/version-2.15/reference/targets/archive.mdx +++ b/versioned_docs/version-2.15/reference/targets/archive.mdx @@ -24,7 +24,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -52,7 +52,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. @@ -65,11 +65,11 @@ Warning: setting this value risks naming collisions with other package targets y default_repr={`None`} > -Addresses to any targets that can be built with `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, e.g. `["project:app"]`. +Addresses to any targets that can be built with `/home/josh/work/scie-pants/dist/pants package`, e.g. `["project:app"]`. -Pants will build the assets as if you had run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`. It will include the results in your archive using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). +Pants will build the assets as if you had run `/home/josh/work/scie-pants/dist/pants package`. It will include the results in your archive using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). -You can include anything that can be built by `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or even another `archive`. +You can include anything that can be built by `/home/josh/work/scie-pants/dist/pants package`, e.g. a `pex_binary`, `python_awslambda`, or even another `archive`. diff --git a/versioned_docs/version-2.15/reference/targets/deploy_jar.mdx b/versioned_docs/version-2.15/reference/targets/deploy_jar.mdx index b2acbdf93..5e415c198 100644 --- a/versioned_docs/version-2.15/reference/targets/deploy_jar.mdx +++ b/versioned_docs/version-2.15/reference/targets/deploy_jar.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.experimental.java` @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -52,9 +52,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -73,7 +73,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. diff --git a/versioned_docs/version-2.15/reference/targets/docker_environment.mdx b/versioned_docs/version-2.15/reference/targets/docker_environment.mdx index 8b4ff58da..ba2eb355e 100644 --- a/versioned_docs/version-2.15/reference/targets/docker_environment.mdx +++ b/versioned_docs/version-2.15/reference/targets/docker_environment.mdx @@ -28,7 +28,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.15/reference/targets/docker_image.mdx b/versioned_docs/version-2.15/reference/targets/docker_image.mdx index 371a81f1e..fef80da55 100644 --- a/versioned_docs/version-2.15/reference/targets/docker_image.mdx +++ b/versioned_docs/version-2.15/reference/targets/docker_image.mdx @@ -39,7 +39,7 @@ Backend: `pants.backend.docker` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -52,7 +52,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -78,9 +78,9 @@ Use `[docker].build_args` to set default build args for all images. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -277,7 +277,7 @@ See [Docker documentation](https://docs.docker.com/develop/develop-images/build_ default_repr={`False`} > -If set to true, do not push this image to registries when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 publish`. +If set to true, do not push this image to registries when running `/home/josh/work/scie-pants/dist/pants publish`. diff --git a/versioned_docs/version-2.15/reference/targets/experimental_run_shell_command.mdx b/versioned_docs/version-2.15/reference/targets/experimental_run_shell_command.mdx index 2d3b307e9..9a5cb2137 100644 --- a/versioned_docs/version-2.15/reference/targets/experimental_run_shell_command.mdx +++ b/versioned_docs/version-2.15/reference/targets/experimental_run_shell_command.mdx @@ -37,7 +37,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -50,7 +50,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -63,9 +63,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.15/reference/targets/experimental_shell_command.mdx b/versioned_docs/version-2.15/reference/targets/experimental_shell_command.mdx index bb9fdc097..79e3cab64 100644 --- a/versioned_docs/version-2.15/reference/targets/experimental_shell_command.mdx +++ b/versioned_docs/version-2.15/reference/targets/experimental_shell_command.mdx @@ -41,7 +41,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -54,7 +54,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -67,9 +67,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.15/reference/targets/file.mdx b/versioned_docs/version-2.15/reference/targets/file.mdx index 092c17811..d33bb3531 100644 --- a/versioned_docs/version-2.15/reference/targets/file.mdx +++ b/versioned_docs/version-2.15/reference/targets/file.mdx @@ -26,7 +26,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -52,9 +52,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.15/reference/targets/files.mdx b/versioned_docs/version-2.15/reference/targets/files.mdx index f74a6877c..aadc23144 100644 --- a/versioned_docs/version-2.15/reference/targets/files.mdx +++ b/versioned_docs/version-2.15/reference/targets/files.mdx @@ -24,7 +24,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -91,9 +91,9 @@ You can specify the same file name in multiple keys, so long as you don't o Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.15/reference/targets/go_binary.mdx b/versioned_docs/version-2.15/reference/targets/go_binary.mdx index 3f172d7d0..26351b1ff 100644 --- a/versioned_docs/version-2.15/reference/targets/go_binary.mdx +++ b/versioned_docs/version-2.15/reference/targets/go_binary.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.go` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -52,7 +52,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. diff --git a/versioned_docs/version-2.15/reference/targets/go_mod.mdx b/versioned_docs/version-2.15/reference/targets/go_mod.mdx index 605db3545..caeac0e75 100644 --- a/versioned_docs/version-2.15/reference/targets/go_mod.mdx +++ b/versioned_docs/version-2.15/reference/targets/go_mod.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.go` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.15/reference/targets/go_package.mdx b/versioned_docs/version-2.15/reference/targets/go_package.mdx index 06a2c9bc2..31ffac9ae 100644 --- a/versioned_docs/version-2.15/reference/targets/go_package.mdx +++ b/versioned_docs/version-2.15/reference/targets/go_package.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.experimental.go` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -52,9 +52,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.15/reference/targets/go_third_party_package.mdx b/versioned_docs/version-2.15/reference/targets/go_third_party_package.mdx index 5ba8d0f08..883529445 100644 --- a/versioned_docs/version-2.15/reference/targets/go_third_party_package.mdx +++ b/versioned_docs/version-2.15/reference/targets/go_third_party_package.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.go` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -54,9 +54,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.15/reference/targets/helm_artifact.mdx b/versioned_docs/version-2.15/reference/targets/helm_artifact.mdx index 62850ffdf..33546af67 100644 --- a/versioned_docs/version-2.15/reference/targets/helm_artifact.mdx +++ b/versioned_docs/version-2.15/reference/targets/helm_artifact.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.helm` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.15/reference/targets/helm_chart.mdx b/versioned_docs/version-2.15/reference/targets/helm_chart.mdx index e644d328c..4b9a1657e 100644 --- a/versioned_docs/version-2.15/reference/targets/helm_chart.mdx +++ b/versioned_docs/version-2.15/reference/targets/helm_chart.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.helm` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -76,9 +76,9 @@ Example: `sources=['values.yaml', 'templates/*.yaml', '!values_ignore.yaml']` Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -99,7 +99,7 @@ If undefined, this will use the path to the BUILD file, For example, `src/charts Regardless of whether you use the default or set this field, the path will end with Helms's file format of `-.tgz`, where `chart_name` and `chart_version` are the values extracted from the Chart.yaml file. So, using the default for this field, the target `src/charts/mychart:tgt_name` might have a final path like `src.charts.mychart/tgt_name/mychart-0.1.0.tgz`. -When running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. @@ -170,7 +170,7 @@ The above example shows two valid `registry` options: using an alias to a config default_repr={`False`} > -If set to true, do not push this Helm chart to registries when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 publish`. +If set to true, do not push this Helm chart to registries when running `/home/josh/work/scie-pants/dist/pants publish`. @@ -181,7 +181,7 @@ If set to true, do not push this Helm chart to registries when running `/home/jo default_repr={`False`} > -If set to true, do not run any linting in this Helm chart when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +If set to true, do not run any linting in this Helm chart when running `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.15/reference/targets/helm_deployment.mdx b/versioned_docs/version-2.15/reference/targets/helm_deployment.mdx index 8d9a9d47b..2df6545bb 100644 --- a/versioned_docs/version-2.15/reference/targets/helm_deployment.mdx +++ b/versioned_docs/version-2.15/reference/targets/helm_deployment.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.helm` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -61,9 +61,9 @@ Name of the release used in the deployment. If not set, the target name will be Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.15/reference/targets/helm_unittest_test.mdx b/versioned_docs/version-2.15/reference/targets/helm_unittest_test.mdx index b9c38eebb..959af3e8b 100644 --- a/versioned_docs/version-2.15/reference/targets/helm_unittest_test.mdx +++ b/versioned_docs/version-2.15/reference/targets/helm_unittest_test.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.helm` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -63,9 +63,9 @@ Path is relative to the BUILD file's directory, e.g. `source='example.ext'` Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.15/reference/targets/helm_unittest_tests.mdx b/versioned_docs/version-2.15/reference/targets/helm_unittest_tests.mdx index 83decb6c4..12615a4bd 100644 --- a/versioned_docs/version-2.15/reference/targets/helm_unittest_tests.mdx +++ b/versioned_docs/version-2.15/reference/targets/helm_unittest_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.helm` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -65,9 +65,9 @@ Example: `sources=['*_test.yaml', '!ignore_test.yaml']` Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -109,9 +109,9 @@ You can specify the same file name in multiple keys, so long as you don't o Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.15/reference/targets/java_source.mdx b/versioned_docs/version-2.15/reference/targets/java_source.mdx index 44365bc60..e061fc382 100644 --- a/versioned_docs/version-2.15/reference/targets/java_source.mdx +++ b/versioned_docs/version-2.15/reference/targets/java_source.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.java` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.15/reference/targets/java_sources.mdx b/versioned_docs/version-2.15/reference/targets/java_sources.mdx index 6760a754e..683689b3a 100644 --- a/versioned_docs/version-2.15/reference/targets/java_sources.mdx +++ b/versioned_docs/version-2.15/reference/targets/java_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.java` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -77,9 +77,9 @@ If true, don't run Google Java Format on this target's code. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.15/reference/targets/junit_test.mdx b/versioned_docs/version-2.15/reference/targets/junit_test.mdx index 7a6066235..6658107d1 100644 --- a/versioned_docs/version-2.15/reference/targets/junit_test.mdx +++ b/versioned_docs/version-2.15/reference/targets/junit_test.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.java` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -91,9 +91,9 @@ This will be merged with and override values from `[test].extra_env_vars`. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.15/reference/targets/junit_tests.mdx b/versioned_docs/version-2.15/reference/targets/junit_tests.mdx index f4668ef77..bed3bc8f3 100644 --- a/versioned_docs/version-2.15/reference/targets/junit_tests.mdx +++ b/versioned_docs/version-2.15/reference/targets/junit_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.java` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -93,9 +93,9 @@ This will be merged with and override values from `[test].extra_env_vars`. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.15/reference/targets/jvm_artifact.mdx b/versioned_docs/version-2.15/reference/targets/jvm_artifact.mdx index bda290c15..754a5b761 100644 --- a/versioned_docs/version-2.15/reference/targets/jvm_artifact.mdx +++ b/versioned_docs/version-2.15/reference/targets/jvm_artifact.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.java` @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.15/reference/targets/jvm_war.mdx b/versioned_docs/version-2.15/reference/targets/jvm_war.mdx index 9921f7f7c..c3dfaed9f 100644 --- a/versioned_docs/version-2.15/reference/targets/jvm_war.mdx +++ b/versioned_docs/version-2.15/reference/targets/jvm_war.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.java` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -74,9 +74,9 @@ A list of addresses to `resources` and `files` targets with content to place in Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -106,7 +106,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. diff --git a/versioned_docs/version-2.15/reference/targets/kotlin_junit_test.mdx b/versioned_docs/version-2.15/reference/targets/kotlin_junit_test.mdx index 20e650e8c..d831d86c6 100644 --- a/versioned_docs/version-2.15/reference/targets/kotlin_junit_test.mdx +++ b/versioned_docs/version-2.15/reference/targets/kotlin_junit_test.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.kotlin` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.15/reference/targets/kotlin_junit_tests.mdx b/versioned_docs/version-2.15/reference/targets/kotlin_junit_tests.mdx index 330c28a4b..ca082a886 100644 --- a/versioned_docs/version-2.15/reference/targets/kotlin_junit_tests.mdx +++ b/versioned_docs/version-2.15/reference/targets/kotlin_junit_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.kotlin` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -65,9 +65,9 @@ Example: `sources=['*Test.kt', '!TestIgnore.kt']` Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.15/reference/targets/kotlin_source.mdx b/versioned_docs/version-2.15/reference/targets/kotlin_source.mdx index 36173e92c..a107c641a 100644 --- a/versioned_docs/version-2.15/reference/targets/kotlin_source.mdx +++ b/versioned_docs/version-2.15/reference/targets/kotlin_source.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.kotlin` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.15/reference/targets/kotlin_sources.mdx b/versioned_docs/version-2.15/reference/targets/kotlin_sources.mdx index e4ed32a2b..7771c226a 100644 --- a/versioned_docs/version-2.15/reference/targets/kotlin_sources.mdx +++ b/versioned_docs/version-2.15/reference/targets/kotlin_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.kotlin` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -77,9 +77,9 @@ If true, don't run Ktlint on this target's code. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.15/reference/targets/kotlinc_plugin.mdx b/versioned_docs/version-2.15/reference/targets/kotlinc_plugin.mdx index c60cbe5c3..a4095066e 100644 --- a/versioned_docs/version-2.15/reference/targets/kotlinc_plugin.mdx +++ b/versioned_docs/version-2.15/reference/targets/kotlinc_plugin.mdx @@ -33,7 +33,7 @@ Backend: `pants.backend.experimental.kotlin` @@ -46,7 +46,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.15/reference/targets/local_environment.mdx b/versioned_docs/version-2.15/reference/targets/local_environment.mdx index 799b04473..f58e048aa 100644 --- a/versioned_docs/version-2.15/reference/targets/local_environment.mdx +++ b/versioned_docs/version-2.15/reference/targets/local_environment.mdx @@ -30,7 +30,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.15/reference/targets/openapi_document.mdx b/versioned_docs/version-2.15/reference/targets/openapi_document.mdx index 4e70ab10a..5e70ac15b 100644 --- a/versioned_docs/version-2.15/reference/targets/openapi_document.mdx +++ b/versioned_docs/version-2.15/reference/targets/openapi_document.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.openapi` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.15/reference/targets/openapi_documents.mdx b/versioned_docs/version-2.15/reference/targets/openapi_documents.mdx index 4ce2ae986..583e5b7dd 100644 --- a/versioned_docs/version-2.15/reference/targets/openapi_documents.mdx +++ b/versioned_docs/version-2.15/reference/targets/openapi_documents.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.openapi` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -77,9 +77,9 @@ If true, don't run `spectral lint` on this target's code. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.15/reference/targets/openapi_source.mdx b/versioned_docs/version-2.15/reference/targets/openapi_source.mdx index d7f3cb182..208c57b30 100644 --- a/versioned_docs/version-2.15/reference/targets/openapi_source.mdx +++ b/versioned_docs/version-2.15/reference/targets/openapi_source.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.openapi` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.15/reference/targets/openapi_sources.mdx b/versioned_docs/version-2.15/reference/targets/openapi_sources.mdx index 90f3aeb1e..f7801667a 100644 --- a/versioned_docs/version-2.15/reference/targets/openapi_sources.mdx +++ b/versioned_docs/version-2.15/reference/targets/openapi_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.openapi` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -65,9 +65,9 @@ Example: `sources=['*.json']` Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.15/reference/targets/pants_requirements.mdx b/versioned_docs/version-2.15/reference/targets/pants_requirements.mdx index 26d1ab1a6..e2626fb8b 100644 --- a/versioned_docs/version-2.15/reference/targets/pants_requirements.mdx +++ b/versioned_docs/version-2.15/reference/targets/pants_requirements.mdx @@ -30,7 +30,7 @@ Backend: `pants.backend.plugin_development` @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.15/reference/targets/pex_binaries.mdx b/versioned_docs/version-2.15/reference/targets/pex_binaries.mdx index 04df962d8..7beb5d1bf 100644 --- a/versioned_docs/version-2.15/reference/targets/pex_binaries.mdx +++ b/versioned_docs/version-2.15/reference/targets/pex_binaries.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -147,9 +147,9 @@ All dependencies must share the same value for their `resolve` field. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.15/reference/targets/pex_binary.mdx b/versioned_docs/version-2.15/reference/targets/pex_binary.mdx index 8739b3fcf..f33978fe0 100644 --- a/versioned_docs/version-2.15/reference/targets/pex_binary.mdx +++ b/versioned_docs/version-2.15/reference/targets/pex_binary.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -101,9 +101,9 @@ All dependencies must share the same value for their `resolve` field. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -365,7 +365,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. diff --git a/versioned_docs/version-2.15/reference/targets/pipenv_requirements.mdx b/versioned_docs/version-2.15/reference/targets/pipenv_requirements.mdx index e87501d1a..1a319f31a 100644 --- a/versioned_docs/version-2.15/reference/targets/pipenv_requirements.mdx +++ b/versioned_docs/version-2.15/reference/targets/pipenv_requirements.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.15/reference/targets/poetry_requirements.mdx b/versioned_docs/version-2.15/reference/targets/poetry_requirements.mdx index 4d8346512..344c86b2f 100644 --- a/versioned_docs/version-2.15/reference/targets/poetry_requirements.mdx +++ b/versioned_docs/version-2.15/reference/targets/poetry_requirements.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.15/reference/targets/protobuf_source.mdx b/versioned_docs/version-2.15/reference/targets/protobuf_source.mdx index a396bd483..be8233fe6 100644 --- a/versioned_docs/version-2.15/reference/targets/protobuf_source.mdx +++ b/versioned_docs/version-2.15/reference/targets/protobuf_source.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.codegen.protobuf.python Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -54,9 +54,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.15/reference/targets/protobuf_sources.mdx b/versioned_docs/version-2.15/reference/targets/protobuf_sources.mdx index 8f7b41466..ab136120f 100644 --- a/versioned_docs/version-2.15/reference/targets/protobuf_sources.mdx +++ b/versioned_docs/version-2.15/reference/targets/protobuf_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.codegen.protobuf.python Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -218,9 +218,9 @@ Whether to generate gRPC code or not. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.15/reference/targets/pyoxidizer_binary.mdx b/versioned_docs/version-2.15/reference/targets/pyoxidizer_binary.mdx index 99671ae38..181b77d0e 100644 --- a/versioned_docs/version-2.15/reference/targets/pyoxidizer_binary.mdx +++ b/versioned_docs/version-2.15/reference/targets/pyoxidizer_binary.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.python.pac Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -58,7 +58,7 @@ If undefined, this will use the path to the BUILD file, followed by the target n Regardless of whether you use the default or set this field, the path will end with PyOxidizer's file format of `/{debug,release}/install/`, where `platform` is a Rust platform triplet like `aarch-64-apple-darwin` and `binary_name` is the value of the `binary_name` field. So, using the default for this field, the target `src/python/project:bin` might have a final path like `src.python.project/bin/aarch-64-apple-darwin/release/bin`. -When running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. diff --git a/versioned_docs/version-2.15/reference/targets/python_awslambda.mdx b/versioned_docs/version-2.15/reference/targets/python_awslambda.mdx index 65c573454..0758ce93f 100644 --- a/versioned_docs/version-2.15/reference/targets/python_awslambda.mdx +++ b/versioned_docs/version-2.15/reference/targets/python_awslambda.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.awslambda.python` @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -54,7 +54,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. @@ -69,9 +69,9 @@ Warning: setting this value risks naming collisions with other package targets y Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.15/reference/targets/python_distribution.mdx b/versioned_docs/version-2.15/reference/targets/python_distribution.mdx index 6bd1f7180..ccfcc68d9 100644 --- a/versioned_docs/version-2.15/reference/targets/python_distribution.mdx +++ b/versioned_docs/version-2.15/reference/targets/python_distribution.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -71,9 +71,9 @@ See https://www.pantsbuild.org/v2.15/docs/python-interpreter-compatibility for h Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -108,7 +108,7 @@ Note that Pants will assume that any value that either starts with `:` or has `/ Pants will attempt to infer dependencies, which you can confirm by running: ``` -/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies +/home/josh/work/scie-pants/dist/pants dependencies ``` diff --git a/versioned_docs/version-2.15/reference/targets/python_google_cloud_function.mdx b/versioned_docs/version-2.15/reference/targets/python_google_cloud_function.mdx index 93687f7a2..6c37fc2e4 100644 --- a/versioned_docs/version-2.15/reference/targets/python_google_cloud_function.mdx +++ b/versioned_docs/version-2.15/reference/targets/python_google_cloud_function.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.google_cloud_function.p Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -54,7 +54,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `/home/josh/work/scie-pants/dist/pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. @@ -69,9 +69,9 @@ Warning: setting this value risks naming collisions with other package targets y Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.15/reference/targets/python_requirement.mdx b/versioned_docs/version-2.15/reference/targets/python_requirement.mdx index 30e7fe6e0..6d0fbb688 100644 --- a/versioned_docs/version-2.15/reference/targets/python_requirement.mdx +++ b/versioned_docs/version-2.15/reference/targets/python_requirement.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -69,9 +69,9 @@ If the requirement depends on some other requirement to work, such as needing `s Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.15/reference/targets/python_requirements.mdx b/versioned_docs/version-2.15/reference/targets/python_requirements.mdx index 2691c18c2..6fba0b9aa 100644 --- a/versioned_docs/version-2.15/reference/targets/python_requirements.mdx +++ b/versioned_docs/version-2.15/reference/targets/python_requirements.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.15/reference/targets/python_source.mdx b/versioned_docs/version-2.15/reference/targets/python_source.mdx index 5b94f1874..7689405c6 100644 --- a/versioned_docs/version-2.15/reference/targets/python_source.mdx +++ b/versioned_docs/version-2.15/reference/targets/python_source.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -69,9 +69,9 @@ See https://www.pantsbuild.org/v2.15/docs/python-interpreter-compatibility for h Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.15/reference/targets/python_sources.mdx b/versioned_docs/version-2.15/reference/targets/python_sources.mdx index 2cbf14f2d..2242df48e 100644 --- a/versioned_docs/version-2.15/reference/targets/python_sources.mdx +++ b/versioned_docs/version-2.15/reference/targets/python_sources.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -259,9 +259,9 @@ The latter mode is similar to creating, activating, and using a virtual environm Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.15/reference/targets/python_test.mdx b/versioned_docs/version-2.15/reference/targets/python_test.mdx index 1c53bb677..432255063 100644 --- a/versioned_docs/version-2.15/reference/targets/python_test.mdx +++ b/versioned_docs/version-2.15/reference/targets/python_test.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -54,9 +54,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -161,11 +161,11 @@ When tests with the same `batch_compatibility_tag` have incompatibilities in som default_repr={`None`} > -Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run. +Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/pants package` goal and whose resulting artifacts should be included in the test run. -Pants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). +Pants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). -You can include anything that can be built by `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`. +You can include anything that can be built by `/home/josh/work/scie-pants/dist/pants package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`. diff --git a/versioned_docs/version-2.15/reference/targets/python_test_utils.mdx b/versioned_docs/version-2.15/reference/targets/python_test_utils.mdx index d2476779e..0048aba55 100644 --- a/versioned_docs/version-2.15/reference/targets/python_test_utils.mdx +++ b/versioned_docs/version-2.15/reference/targets/python_test_utils.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -259,9 +259,9 @@ The latter mode is similar to creating, activating, and using a virtual environm Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.15/reference/targets/python_tests.mdx b/versioned_docs/version-2.15/reference/targets/python_tests.mdx index 5e3e02709..4d1b03a64 100644 --- a/versioned_docs/version-2.15/reference/targets/python_tests.mdx +++ b/versioned_docs/version-2.15/reference/targets/python_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -223,9 +223,9 @@ If true, don't run MyPy on this target's code. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -330,11 +330,11 @@ When tests with the same `batch_compatibility_tag` have incompatibilities in som default_repr={`None`} > -Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run. +Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/pants package` goal and whose resulting artifacts should be included in the test run. -Pants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). +Pants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). -You can include anything that can be built by `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`. +You can include anything that can be built by `/home/josh/work/scie-pants/dist/pants package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`. diff --git a/versioned_docs/version-2.15/reference/targets/relocated_files.mdx b/versioned_docs/version-2.15/reference/targets/relocated_files.mdx index 73ed0c422..b920f40cd 100644 --- a/versioned_docs/version-2.15/reference/targets/relocated_files.mdx +++ b/versioned_docs/version-2.15/reference/targets/relocated_files.mdx @@ -61,7 +61,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -74,7 +74,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.15/reference/targets/remote_environment.mdx b/versioned_docs/version-2.15/reference/targets/remote_environment.mdx index 4fc794ce2..1240f745e 100644 --- a/versioned_docs/version-2.15/reference/targets/remote_environment.mdx +++ b/versioned_docs/version-2.15/reference/targets/remote_environment.mdx @@ -32,7 +32,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -45,7 +45,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.15/reference/targets/resource.mdx b/versioned_docs/version-2.15/reference/targets/resource.mdx index 1e615e1e2..d14f752c5 100644 --- a/versioned_docs/version-2.15/reference/targets/resource.mdx +++ b/versioned_docs/version-2.15/reference/targets/resource.mdx @@ -26,7 +26,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -52,9 +52,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.15/reference/targets/resources.mdx b/versioned_docs/version-2.15/reference/targets/resources.mdx index 59f2a5963..c1b22a6e0 100644 --- a/versioned_docs/version-2.15/reference/targets/resources.mdx +++ b/versioned_docs/version-2.15/reference/targets/resources.mdx @@ -24,7 +24,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -91,9 +91,9 @@ You can specify the same file name in multiple keys, so long as you don't o Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.15/reference/targets/scala_junit_test.mdx b/versioned_docs/version-2.15/reference/targets/scala_junit_test.mdx index e904a4d79..3e9bf812e 100644 --- a/versioned_docs/version-2.15/reference/targets/scala_junit_test.mdx +++ b/versioned_docs/version-2.15/reference/targets/scala_junit_test.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.scala` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.15/reference/targets/scala_junit_tests.mdx b/versioned_docs/version-2.15/reference/targets/scala_junit_tests.mdx index 102c89c1a..45517bbe7 100644 --- a/versioned_docs/version-2.15/reference/targets/scala_junit_tests.mdx +++ b/versioned_docs/version-2.15/reference/targets/scala_junit_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.scala` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -104,9 +104,9 @@ If unset, will default to `[test].timeout_default`; if that option is also unset Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.15/reference/targets/scala_source.mdx b/versioned_docs/version-2.15/reference/targets/scala_source.mdx index 60364f919..662081a92 100644 --- a/versioned_docs/version-2.15/reference/targets/scala_source.mdx +++ b/versioned_docs/version-2.15/reference/targets/scala_source.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.scala` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.15/reference/targets/scala_sources.mdx b/versioned_docs/version-2.15/reference/targets/scala_sources.mdx index 892e99a2e..12e99e4ea 100644 --- a/versioned_docs/version-2.15/reference/targets/scala_sources.mdx +++ b/versioned_docs/version-2.15/reference/targets/scala_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.scala` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -103,9 +103,9 @@ If true, don't run `scalafmt` on this target's code. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.15/reference/targets/scalac_plugin.mdx b/versioned_docs/version-2.15/reference/targets/scalac_plugin.mdx index 53c633e66..2d5fa0e60 100644 --- a/versioned_docs/version-2.15/reference/targets/scalac_plugin.mdx +++ b/versioned_docs/version-2.15/reference/targets/scalac_plugin.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.scala` @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.15/reference/targets/scalatest_test.mdx b/versioned_docs/version-2.15/reference/targets/scalatest_test.mdx index 036519400..073cd14eb 100644 --- a/versioned_docs/version-2.15/reference/targets/scalatest_test.mdx +++ b/versioned_docs/version-2.15/reference/targets/scalatest_test.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.scala` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.15/reference/targets/scalatest_tests.mdx b/versioned_docs/version-2.15/reference/targets/scalatest_tests.mdx index 09f52853f..298c2197e 100644 --- a/versioned_docs/version-2.15/reference/targets/scalatest_tests.mdx +++ b/versioned_docs/version-2.15/reference/targets/scalatest_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.scala` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -91,9 +91,9 @@ You can specify the same file name in multiple keys, so long as you don't o Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.15/reference/targets/shell_source.mdx b/versioned_docs/version-2.15/reference/targets/shell_source.mdx index 5dc1460d8..e06de7d06 100644 --- a/versioned_docs/version-2.15/reference/targets/shell_source.mdx +++ b/versioned_docs/version-2.15/reference/targets/shell_source.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.15/reference/targets/shell_sources.mdx b/versioned_docs/version-2.15/reference/targets/shell_sources.mdx index f463c7662..219fdc94b 100644 --- a/versioned_docs/version-2.15/reference/targets/shell_sources.mdx +++ b/versioned_docs/version-2.15/reference/targets/shell_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -115,9 +115,9 @@ If true, don't run shfmt on this target's code. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.15/reference/targets/shunit2_test.mdx b/versioned_docs/version-2.15/reference/targets/shunit2_test.mdx index bf9d1d90c..27d7f5359 100644 --- a/versioned_docs/version-2.15/reference/targets/shunit2_test.mdx +++ b/versioned_docs/version-2.15/reference/targets/shunit2_test.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -67,9 +67,9 @@ Path is relative to the BUILD file's directory, e.g. `source='example.ext'` Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -119,11 +119,11 @@ Which shell to run the tests with. If unspecified, Pants will look for a shebang default_repr={`None`} > -Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run. +Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/pants package` goal and whose resulting artifacts should be included in the test run. -Pants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). +Pants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). -You can include anything that can be built by `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`. +You can include anything that can be built by `/home/josh/work/scie-pants/dist/pants package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`. diff --git a/versioned_docs/version-2.15/reference/targets/shunit2_tests.mdx b/versioned_docs/version-2.15/reference/targets/shunit2_tests.mdx index 30d924938..7af12b3c6 100644 --- a/versioned_docs/version-2.15/reference/targets/shunit2_tests.mdx +++ b/versioned_docs/version-2.15/reference/targets/shunit2_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -115,9 +115,9 @@ If true, don't run shfmt on this target's code. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -167,11 +167,11 @@ Which shell to run the tests with. If unspecified, Pants will look for a shebang default_repr={`None`} > -Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run. +Addresses to targets that can be built with the `/home/josh/work/scie-pants/dist/pants package` goal and whose resulting artifacts should be included in the test run. -Pants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). +Pants will build the artifacts as if you had run `/home/josh/work/scie-pants/dist/pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). -You can include anything that can be built by `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`. +You can include anything that can be built by `/home/josh/work/scie-pants/dist/pants package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`. diff --git a/versioned_docs/version-2.15/reference/targets/target.mdx b/versioned_docs/version-2.15/reference/targets/target.mdx index 73b092146..2592c1a00 100644 --- a/versioned_docs/version-2.15/reference/targets/target.mdx +++ b/versioned_docs/version-2.15/reference/targets/target.mdx @@ -26,7 +26,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -52,9 +52,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.15/reference/targets/terraform_module.mdx b/versioned_docs/version-2.15/reference/targets/terraform_module.mdx index 1b15fdb98..abfb2c32e 100644 --- a/versioned_docs/version-2.15/reference/targets/terraform_module.mdx +++ b/versioned_docs/version-2.15/reference/targets/terraform_module.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.terraform` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -54,9 +54,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.15/reference/targets/thrift_source.mdx b/versioned_docs/version-2.15/reference/targets/thrift_source.mdx index ab84e5dcd..41f96f851 100644 --- a/versioned_docs/version-2.15/reference/targets/thrift_source.mdx +++ b/versioned_docs/version-2.15/reference/targets/thrift_source.mdx @@ -27,7 +27,7 @@ Backend: `pants.backend.codegen.thrift.apache.p Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -40,7 +40,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -53,9 +53,9 @@ Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented : Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.15/reference/targets/thrift_sources.mdx b/versioned_docs/version-2.15/reference/targets/thrift_sources.mdx index c2fec7227..be7fe743a 100644 --- a/versioned_docs/version-2.15/reference/targets/thrift_sources.mdx +++ b/versioned_docs/version-2.15/reference/targets/thrift_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.codegen.thrift.apache.p Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `/home/josh/work/scie-pants/dist/pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. @@ -106,9 +106,9 @@ All dependencies must share the same value for their `resolve` field. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 dependencies` or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `/home/josh/work/scie-pants/dist/pants dependencies` or `/home/josh/work/scie-pants/dist/pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.15/docs/targets for more about how addresses are formed, including for generated targets. You can also run `/home/josh/work/scie-pants/dist/pants list ::` to find all addresses in your project, or `/home/josh/work/scie-pants/dist/pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.15/reference/targets/vcs_version.mdx b/versioned_docs/version-2.15/reference/targets/vcs_version.mdx index 0d640759c..885841a53 100644 --- a/versioned_docs/version-2.15/reference/targets/vcs_version.mdx +++ b/versioned_docs/version-2.15/reference/targets/vcs_version.mdx @@ -30,7 +30,7 @@ Backend: `pants.backend.experimental.python` @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `/home/josh/work/scie-pants/dist/pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.16/reference/global-options.mdx b/versioned_docs/version-2.16/reference/global-options.mdx index 2d0dcf521..cff24fa85 100644 --- a/versioned_docs/version-2.16/reference/global-options.mdx +++ b/versioned_docs/version-2.16/reference/global-options.mdx @@ -317,9 +317,9 @@ ignore_warnings = [ Use this Pants version. Note that Pants only uses this to verify that you are using the requested version, as Pants cannot dynamically change the version it is using once the program is already running. -If you use the `scie-pants-linux-x86_64` script from https://www.pantsbuild.org/v2.16/docs/installation, however, changing the value in your `pants.toml` will cause the new version to be installed and run automatically. +If you use the `pants` script from https://www.pantsbuild.org/v2.16/docs/installation, however, changing the value in your `pants.toml` will cause the new version to be installed and run automatically. -Run `scie-pants-linux-x86_64 --version` to check what is being used. +Run `pants --version` to check what is being used. @@ -824,7 +824,7 @@ Whether or not to use nailgun to run JVM requests that are marked as supporting default_repr={`3`} > -The time in seconds to wait when gracefully shutting down an interactive process (such as one opened using `scie-pants-linux-x86_64 run`) before killing it. +The time in seconds to wait when gracefully shutting down an interactive process (such as one opened using `pants run`) before killing it. diff --git a/versioned_docs/version-2.16/reference/goals/experimental-bsp.mdx b/versioned_docs/version-2.16/reference/goals/experimental-bsp.mdx index 5362d9e2f..501fe81ee 100644 --- a/versioned_docs/version-2.16/reference/goals/experimental-bsp.mdx +++ b/versioned_docs/version-2.16/reference/goals/experimental-bsp.mdx @@ -79,7 +79,7 @@ Run the Build Server Protocol server. Pants will receive BSP RPC requests via th Environment variables to set in the BSP runner script when setting up BSP in a repository. Entries are either strings in the form `ENV_VAR=value` to set an explicit value; or just `ENV_VAR` to copy the value from Pants' own environment when the experimental-bsp goal was run. -This option only takes effect when the BSP runner script is written. If the option changes, you must run `scie-pants-linux-x86_64 experimental-bsp` again to write a new copy of the BSP runner script. +This option only takes effect when the BSP runner script is written. If the option changes, you must run `pants experimental-bsp` again to write a new copy of the BSP runner script. Note: The environment variables passed to the Pants BSP server will be those set for your IDE and not your shell. For example, on macOS, the IDE is generally launched by `launchd` after clicking on a Dock icon, and not from the shell. Thus, any environment variables set for your shell will likely not be seen by the Pants BSP server. At the very least, on macOS consider writing an explicit PATH into the BSP runner script via this option. diff --git a/versioned_docs/version-2.16/reference/goals/fix.mdx b/versioned_docs/version-2.16/reference/goals/fix.mdx index 3d3070e5c..27e6876f3 100644 --- a/versioned_docs/version-2.16/reference/goals/fix.mdx +++ b/versioned_docs/version-2.16/reference/goals/fix.mdx @@ -47,7 +47,7 @@ You can repeat this option, e.g. `fix --only=autoflake --only=pyupgrade` or `fix If true, skip running all formatters. -FYI: when running `scie-pants-linux-x86_64 fix fmt ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `fix` where possible. +FYI: when running `pants fix fmt ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `fix` where possible. diff --git a/versioned_docs/version-2.16/reference/goals/generate-lockfiles.mdx b/versioned_docs/version-2.16/reference/goals/generate-lockfiles.mdx index 4b1f0a8cb..022833e0f 100644 --- a/versioned_docs/version-2.16/reference/goals/generate-lockfiles.mdx +++ b/versioned_docs/version-2.16/reference/goals/generate-lockfiles.mdx @@ -33,7 +33,7 @@ Only generate lockfiles for the specified resolve(s). Resolves are the logical names for the different lockfiles used in your project. For your own code's dependencies, these come from backend-specific configuration such as `[python].resolves`. For tool lockfiles, resolve names are the options scope for that tool such as `black`, `pytest`, and `mypy-protobuf`. -For example, you can run `scie-pants-linux-x86_64 generate-lockfiles --resolve=black --resolve=pytest --resolve=data-science` to only generate lockfiles for those two tools and your resolve named `data-science`. +For example, you can run `pants generate-lockfiles --resolve=black --resolve=pytest --resolve=data-science` to only generate lockfiles for those two tools and your resolve named `data-science`. If you specify an invalid resolve name, like 'fake', Pants will output all possible values. @@ -75,7 +75,7 @@ Include unchanged distributions in the diff summary output. Implies `diff=true`. default_repr={`None`} > -If set, lockfile headers will say to run this command to regenerate the lockfile, rather than running `scie-pants-linux-x86_64 generate-lockfiles --resolve=` like normal. +If set, lockfile headers will say to run this command to regenerate the lockfile, rather than running `pants generate-lockfiles --resolve=` like normal. diff --git a/versioned_docs/version-2.16/reference/goals/lint.mdx b/versioned_docs/version-2.16/reference/goals/lint.mdx index e9e09a67b..21b78f2d4 100644 --- a/versioned_docs/version-2.16/reference/goals/lint.mdx +++ b/versioned_docs/version-2.16/reference/goals/lint.mdx @@ -47,7 +47,7 @@ You can repeat this option, e.g. `lint --only=flake8 --only=shellcheck` or `lint If true, skip running all formatters in check-only mode. -FYI: when running `scie-pants-linux-x86_64 fmt lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `lint` where possible. +FYI: when running `pants fmt lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `lint` where possible. @@ -61,7 +61,7 @@ FYI: when running `scie-pants-linux-x86_64 fmt lint ::`, there should be diminis If true, skip running all fixers in check-only mode. -FYI: when running `scie-pants-linux-x86_64 fix lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fix` when running `lint` where possible. +FYI: when running `pants fix lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fix` when running `lint` where possible. diff --git a/versioned_docs/version-2.16/reference/help-all.json b/versioned_docs/version-2.16/reference/help-all.json index 785a1e75f..51005dd05 100644 --- a/versioned_docs/version-2.16/reference/help-all.json +++ b/versioned_docs/version-2.16/reference/help-all.json @@ -37304,7 +37304,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -37312,7 +37312,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -37336,7 +37336,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -37344,7 +37344,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -37360,7 +37360,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -37376,7 +37376,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -37384,7 +37384,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -37400,7 +37400,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -37416,7 +37416,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -37424,7 +37424,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -37560,7 +37560,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -37568,7 +37568,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -37576,7 +37576,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -37584,7 +37584,7 @@ { "alias": "packages", "default": null, - "description": "Addresses to any targets that can be built with `scie-pants-linux-x86_64 package`, e.g. `[\"project:app\"]`.\n\nPants will build the assets as if you had run `scie-pants-linux-x86_64 package`. It will include the results in your archive using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or even another `archive`.", + "description": "Addresses to any targets that can be built with `pants package`, e.g. `[\"project:app\"]`.\n\nPants will build the assets as if you had run `pants package`. It will include the results in your archive using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `pants package`, e.g. a `pex_binary`, `python_awslambda`, or even another `archive`.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -37616,7 +37616,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -37624,7 +37624,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -37640,7 +37640,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -37648,7 +37648,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -37704,7 +37704,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -37712,7 +37712,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -37944,7 +37944,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -37952,7 +37952,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -37968,7 +37968,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -38048,7 +38048,7 @@ { "alias": "skip_push", "default": "False", - "description": "If set to true, do not push this image to registries when running `scie-pants-linux-x86_64 publish`.", + "description": "If set to true, do not push this image to registries when running `pants publish`.", "provider": "", "required": false, "type_hint": "bool" @@ -38080,7 +38080,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -38112,7 +38112,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -38120,7 +38120,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -38208,7 +38208,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -38216,7 +38216,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -38248,7 +38248,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -38256,7 +38256,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -38288,7 +38288,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -38296,7 +38296,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -38328,7 +38328,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -38336,7 +38336,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -38368,7 +38368,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -38376,7 +38376,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -38408,7 +38408,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -38416,7 +38416,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -38448,7 +38448,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -38456,7 +38456,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -38464,7 +38464,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -38488,7 +38488,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -38496,7 +38496,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -38520,7 +38520,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -38536,7 +38536,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -38544,7 +38544,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -38552,7 +38552,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -38648,7 +38648,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -38656,7 +38656,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -38728,7 +38728,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -38736,7 +38736,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -38744,7 +38744,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -38840,7 +38840,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -38848,7 +38848,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -38856,7 +38856,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -38880,7 +38880,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -38888,7 +38888,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -38936,7 +38936,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -38944,7 +38944,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -38968,7 +38968,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -38976,7 +38976,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built directory tree should be located.\n\nIf undefined, this will use the path to the BUILD file, For example, `src/charts/mychart:tgt_name` would be `src.charts.mychart/tgt_name/`.\n\nRegardless of whether you use the default or set this field, the path will end with Helms's file format of `-.tgz`, where `chart_name` and `chart_version` are the values extracted from the Chart.yaml file. So, using the default for this field, the target `src/charts/mychart:tgt_name` might have a final path like `src.charts.mychart/tgt_name/mychart-0.1.0.tgz`.\n\nWhen running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built directory tree should be located.\n\nIf undefined, this will use the path to the BUILD file, For example, `src/charts/mychart:tgt_name` would be `src.charts.mychart/tgt_name/`.\n\nRegardless of whether you use the default or set this field, the path will end with Helms's file format of `-.tgz`, where `chart_name` and `chart_version` are the values extracted from the Chart.yaml file. So, using the default for this field, the target `src/charts/mychart:tgt_name` might have a final path like `src.charts.mychart/tgt_name/mychart-0.1.0.tgz`.\n\nWhen running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -39008,7 +39008,7 @@ { "alias": "skip_push", "default": "False", - "description": "If set to true, do not push this Helm chart to registries when running `scie-pants-linux-x86_64 publish`.", + "description": "If set to true, do not push this Helm chart to registries when running `pants publish`.", "provider": "", "required": false, "type_hint": "bool" @@ -39016,7 +39016,7 @@ { "alias": "skip_lint", "default": "False", - "description": "If set to true, do not run any linting in this Helm chart when running `scie-pants-linux-x86_64 lint`.", + "description": "If set to true, do not run any linting in this Helm chart when running `pants lint`.", "provider": "", "required": false, "type_hint": "bool" @@ -39032,7 +39032,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -39040,7 +39040,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -39056,7 +39056,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -39136,7 +39136,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -39144,7 +39144,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -39160,7 +39160,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -39192,7 +39192,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -39200,7 +39200,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -39216,7 +39216,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -39232,7 +39232,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -39264,7 +39264,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -39272,7 +39272,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -39280,7 +39280,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -39344,7 +39344,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -39352,7 +39352,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -39376,7 +39376,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -39424,7 +39424,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -39432,7 +39432,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -39464,7 +39464,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -39504,7 +39504,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -39512,7 +39512,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -39544,7 +39544,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -39584,7 +39584,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -39592,7 +39592,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -39688,7 +39688,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -39696,7 +39696,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -39720,7 +39720,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -39744,7 +39744,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -39760,7 +39760,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -39768,7 +39768,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -39776,7 +39776,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -39848,7 +39848,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -39856,7 +39856,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -39872,7 +39872,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -39936,7 +39936,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -39944,7 +39944,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -39952,7 +39952,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -40024,7 +40024,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -40032,7 +40032,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -40056,7 +40056,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -40112,7 +40112,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -40120,7 +40120,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -40160,7 +40160,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -40168,7 +40168,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -40392,7 +40392,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -40400,7 +40400,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -40408,7 +40408,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -40440,7 +40440,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -40448,7 +40448,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -40472,7 +40472,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -40488,7 +40488,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -40496,7 +40496,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -40504,7 +40504,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -40528,7 +40528,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -40536,7 +40536,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -40552,7 +40552,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -40568,7 +40568,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -40576,7 +40576,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -40608,7 +40608,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -40616,7 +40616,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -40664,7 +40664,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -40808,7 +40808,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -40816,7 +40816,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -40848,7 +40848,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -41016,7 +41016,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -41032,7 +41032,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -41040,7 +41040,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -41096,7 +41096,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -41104,7 +41104,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -41160,7 +41160,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -41168,7 +41168,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -41176,7 +41176,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -41272,7 +41272,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -41280,7 +41280,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -41376,7 +41376,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -41392,7 +41392,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -41400,7 +41400,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -41408,7 +41408,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built directory tree should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:bin` would be `src.python.project/bin/`.\n\nRegardless of whether you use the default or set this field, the path will end with PyOxidizer's file format of `/{debug,release}/install/`, where `platform` is a Rust platform triplet like `aarch-64-apple-darwin` and `binary_name` is the value of the `binary_name` field. So, using the default for this field, the target `src/python/project:bin` might have a final path like `src.python.project/bin/aarch-64-apple-darwin/release/bin`.\n\nWhen running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built directory tree should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:bin` would be `src.python.project/bin/`.\n\nRegardless of whether you use the default or set this field, the path will end with PyOxidizer's file format of `/{debug,release}/install/`, where `platform` is a Rust platform triplet like `aarch-64-apple-darwin` and `binary_name` is the value of the `binary_name` field. So, using the default for this field, the target `src/python/project:bin` might have a final path like `src.python.project/bin/aarch-64-apple-darwin/release/bin`.\n\nWhen running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -41472,7 +41472,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -41480,7 +41480,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -41488,7 +41488,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -41496,7 +41496,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -41560,7 +41560,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -41568,7 +41568,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -41584,7 +41584,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -41592,7 +41592,7 @@ { "alias": "entry_points", "default": null, - "description": "Any entry points, such as `console_scripts` and `gui_scripts`.\n\nSpecify as a nested dictionary, with a dictionary for each type of entry point, e.g. `console_scripts` vs. `gui_scripts`. Each dictionary maps the entry point name to either a setuptools entry point (\"path.to.module:func\") or a Pants target address to a pex_binary target.\n\n Example:\n\n entry_points={\n \"console_scripts\": {\n \"my-script\": \"project.app:main\",\n \"another-script\": \"project/subdir:pex_binary_tgt\"\n }\n }\n\nNote that Pants will assume that any value that either starts with `:` or has `/` in it, is a target address to a pex_binary target. Otherwise, it will assume it's a setuptools entry point as defined by https://packaging.python.org/specifications/entry-points/#entry-points-specification. Use `//` as a prefix for target addresses if you need to disambiguate.\n\nPants will attempt to infer dependencies, which you can confirm by running:\n\n scie-pants-linux-x86_64 dependencies ", + "description": "Any entry points, such as `console_scripts` and `gui_scripts`.\n\nSpecify as a nested dictionary, with a dictionary for each type of entry point, e.g. `console_scripts` vs. `gui_scripts`. Each dictionary maps the entry point name to either a setuptools entry point (\"path.to.module:func\") or a Pants target address to a pex_binary target.\n\n Example:\n\n entry_points={\n \"console_scripts\": {\n \"my-script\": \"project.app:main\",\n \"another-script\": \"project/subdir:pex_binary_tgt\"\n }\n }\n\nNote that Pants will assume that any value that either starts with `:` or has `/` in it, is a target address to a pex_binary target. Otherwise, it will assume it's a setuptools entry point as defined by https://packaging.python.org/specifications/entry-points/#entry-points-specification. Use `//` as a prefix for target addresses if you need to disambiguate.\n\nPants will attempt to infer dependencies, which you can confirm by running:\n\n pants dependencies ", "provider": "", "required": false, "type_hint": "Dict[str, Dict[str, str]] | None" @@ -41704,7 +41704,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -41712,7 +41712,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -41720,7 +41720,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -41728,7 +41728,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -41792,7 +41792,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -41800,7 +41800,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -41816,7 +41816,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -41864,7 +41864,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -41872,7 +41872,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -41928,7 +41928,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -41936,7 +41936,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -41952,7 +41952,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -42104,7 +42104,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -42112,7 +42112,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -42256,7 +42256,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -42288,7 +42288,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -42296,7 +42296,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -42304,7 +42304,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -42352,7 +42352,7 @@ { "alias": "runtime_package_dependencies", "default": null, - "description": "Addresses to targets that can be built with the `scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`.", + "description": "Addresses to targets that can be built with the `pants package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `pants package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -42520,7 +42520,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -42528,7 +42528,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -42672,7 +42672,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -42696,7 +42696,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -42704,7 +42704,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -42840,7 +42840,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -42888,7 +42888,7 @@ { "alias": "runtime_package_dependencies", "default": null, - "description": "Addresses to targets that can be built with the `scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`.", + "description": "Addresses to targets that can be built with the `pants package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `pants package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -42936,7 +42936,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -42944,7 +42944,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -42984,7 +42984,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -42992,7 +42992,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -43232,7 +43232,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -43240,7 +43240,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -43248,7 +43248,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -43272,7 +43272,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -43280,7 +43280,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -43304,7 +43304,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -43320,7 +43320,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -43328,7 +43328,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -43376,7 +43376,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -43384,7 +43384,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -43392,7 +43392,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -43464,7 +43464,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -43472,7 +43472,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -43504,7 +43504,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -43568,7 +43568,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -43576,7 +43576,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -43584,7 +43584,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -43656,7 +43656,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -43664,7 +43664,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -43696,7 +43696,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -43752,7 +43752,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -43760,7 +43760,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -43792,7 +43792,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -43800,7 +43800,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -43808,7 +43808,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -43880,7 +43880,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -43888,7 +43888,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -43912,7 +43912,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -43976,7 +43976,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -43984,7 +43984,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -44104,7 +44104,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -44112,7 +44112,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -44120,7 +44120,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -44160,7 +44160,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -44168,7 +44168,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -44208,7 +44208,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -44224,7 +44224,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -44232,7 +44232,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -44248,7 +44248,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -44280,7 +44280,7 @@ { "alias": "runtime_package_dependencies", "default": null, - "description": "Addresses to targets that can be built with the `scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`.", + "description": "Addresses to targets that can be built with the `pants package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `pants package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -44312,7 +44312,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -44320,7 +44320,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -44360,7 +44360,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -44392,7 +44392,7 @@ { "alias": "runtime_package_dependencies", "default": null, - "description": "Addresses to targets that can be built with the `scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`.", + "description": "Addresses to targets that can be built with the `pants package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `pants package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -44408,7 +44408,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -44416,7 +44416,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -44472,7 +44472,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -44480,7 +44480,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -44488,7 +44488,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -44504,7 +44504,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -44512,7 +44512,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -44520,7 +44520,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -44544,7 +44544,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -44552,7 +44552,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -44560,7 +44560,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -44592,7 +44592,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -44600,7 +44600,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -44632,7 +44632,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -44648,7 +44648,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -44656,7 +44656,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -45021,7 +45021,7 @@ "display_args": ["--pants-version="], "env_var": "PANTS_VERSION", "fromfile": false, - "help": "Use this Pants version. Note that Pants only uses this to verify that you are using the requested version, as Pants cannot dynamically change the version it is using once the program is already running.\n\nIf you use the `scie-pants-linux-x86_64` script from https://www.pantsbuild.org/v2.16/docs/installation, however, changing the value in your `pants.toml` will cause the new version to be installed and run automatically.\n\nRun `scie-pants-linux-x86_64 --version` to check what is being used.", + "help": "Use this Pants version. Note that Pants only uses this to verify that you are using the requested version, as Pants cannot dynamically change the version it is using once the program is already running.\n\nIf you use the `pants` script from https://www.pantsbuild.org/v2.16/docs/installation, however, changing the value in your `pants.toml` will cause the new version to be installed and run automatically.\n\nRun `pants --version` to check what is being used.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pants-version"], @@ -45081,7 +45081,7 @@ { "details": "from env var PANTS_BIN_NAME", "rank": "ENVIRONMENT", - "value": "/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64" + "value": "/home/josh/work/scie-pants/dist/pants" } ] } @@ -46282,7 +46282,7 @@ ], "env_var": "PANTS_PROCESS_EXECUTION_GRACEFUL_SHUTDOWN_TIMEOUT", "fromfile": false, - "help": "The time in seconds to wait when gracefully shutting down an interactive process (such as one opened using `scie-pants-linux-x86_64 run`) before killing it.", + "help": "The time in seconds to wait when gracefully shutting down an interactive process (such as one opened using `pants run`) before killing it.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -48155,7 +48155,7 @@ "display_args": ["--[no-]add-trailing-comma-skip"], "env_var": "PANTS_ADD_TRAILING_COMMA_SKIP", "fromfile": false, - "help": "If true, don't use add-trailing-comma when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use add-trailing-comma when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -48296,7 +48296,7 @@ "display_args": ["--add-trailing-comma-lockfile="], "env_var": "PANTS_ADD_TRAILING_COMMA_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/python/lint/add_trailing_comma/add_trailing_comma.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=add-trailing-comma`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/python/lint/add_trailing_comma/add_trailing_comma.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=add-trailing-comma`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": "Custom tool versions are now installed from named resolves, as described at https://www.pantsbuild.org/v2.16/docs/python-lockfiles.\n\n1. If you have an existing resolve that includes the requirements for this tool,\n you can set `[add-trailing-comma].install_from_resolve = \"\".\n This may be the case if the tool also provides a runtime library, and you want\n to specify the version in just one place.\n2. If not, you can set up a new resolve as described at the link above.\n\nEither way, the resolve you choose should provide the requirements currently set by the `version` and `extra-requirements` options for this tool, which you can see by running `pants help-advanced add-trailing-comma`.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--add-trailing-comma-lockfile"], @@ -48329,7 +48329,7 @@ "display_args": ["--[no-]add-trailing-comma-export"], "env_var": "PANTS_ADD_TRAILING_COMMA_EXPORT", "fromfile": false, - "help": "If true, export a virtual environment with add-trailing-comma when running `scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with add-trailing-comma when running `pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": "Use the export goal's --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": [ @@ -48689,7 +48689,7 @@ "display_args": ["--[no-]autoflake-skip"], "env_var": "PANTS_AUTOFLAKE_SKIP", "fromfile": false, - "help": "If true, don't use Autoflake when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Autoflake when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--autoflake-skip", "--no-autoflake-skip"], @@ -48827,7 +48827,7 @@ "display_args": ["--autoflake-lockfile="], "env_var": "PANTS_AUTOFLAKE_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/python/lint/autoflake/autoflake.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=autoflake`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/python/lint/autoflake/autoflake.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=autoflake`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": "Custom tool versions are now installed from named resolves, as described at https://www.pantsbuild.org/v2.16/docs/python-lockfiles.\n\n1. If you have an existing resolve that includes the requirements for this tool,\n you can set `[autoflake].install_from_resolve = \"\".\n This may be the case if the tool also provides a runtime library, and you want\n to specify the version in just one place.\n2. If not, you can set up a new resolve as described at the link above.\n\nEither way, the resolve you choose should provide the requirements currently set by the `version` and `extra-requirements` options for this tool, which you can see by running `pants help-advanced autoflake`.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--autoflake-lockfile"], @@ -48860,7 +48860,7 @@ "display_args": ["--[no-]autoflake-export"], "env_var": "PANTS_AUTOFLAKE_EXPORT", "fromfile": false, - "help": "If true, export a virtual environment with Autoflake when running `scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with Autoflake when running `pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": "Use the export goal's --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": [ @@ -49057,7 +49057,7 @@ "display_args": ["--[no-]bandit-skip"], "env_var": "PANTS_BANDIT_SKIP", "fromfile": false, - "help": "If true, don't use Bandit when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Bandit when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--bandit-skip", "--no-bandit-skip"], @@ -49193,7 +49193,7 @@ "display_args": ["--bandit-lockfile="], "env_var": "PANTS_BANDIT_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/python/lint/bandit/bandit.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=bandit`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/python/lint/bandit/bandit.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=bandit`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": "Custom tool versions are now installed from named resolves, as described at https://www.pantsbuild.org/v2.16/docs/python-lockfiles.\n\n1. If you have an existing resolve that includes the requirements for this tool,\n you can set `[bandit].install_from_resolve = \"\".\n This may be the case if the tool also provides a runtime library, and you want\n to specify the version in just one place.\n2. If not, you can set up a new resolve as described at the link above.\n\nEither way, the resolve you choose should provide the requirements currently set by the `version` and `extra-requirements` options for this tool, which you can see by running `pants help-advanced bandit`.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--bandit-lockfile"], @@ -49226,7 +49226,7 @@ "display_args": ["--[no-]bandit-export"], "env_var": "PANTS_BANDIT_EXPORT", "fromfile": false, - "help": "If true, export a virtual environment with Bandit when running `scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with Bandit when running `pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": "Use the export goal's --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--bandit-export", "--no-bandit-export"], @@ -49494,7 +49494,7 @@ "display_args": ["--[no-]black-skip"], "env_var": "PANTS_BLACK_SKIP", "fromfile": false, - "help": "If true, don't use Black when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Black when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--black-skip", "--no-black-skip"], @@ -49632,7 +49632,7 @@ "display_args": ["--black-lockfile="], "env_var": "PANTS_BLACK_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/python/lint/black/black.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=black`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/python/lint/black/black.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=black`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": "Custom tool versions are now installed from named resolves, as described at https://www.pantsbuild.org/v2.16/docs/python-lockfiles.\n\n1. If you have an existing resolve that includes the requirements for this tool,\n you can set `[black].install_from_resolve = \"\".\n This may be the case if the tool also provides a runtime library, and you want\n to specify the version in just one place.\n2. If not, you can set up a new resolve as described at the link above.\n\nEither way, the resolve you choose should provide the requirements currently set by the `version` and `extra-requirements` options for this tool, which you can see by running `pants help-advanced black`.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--black-lockfile"], @@ -49665,7 +49665,7 @@ "display_args": ["--[no-]black-export"], "env_var": "PANTS_BLACK_EXPORT", "fromfile": false, - "help": "If true, export a virtual environment with Black when running `scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with Black when running `pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": "Use the export goal's --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--black-export", "--no-black-export"], @@ -49965,7 +49965,7 @@ "display_args": ["--[no-]buf-format-skip"], "env_var": "PANTS_BUF_FORMAT_SKIP", "fromfile": false, - "help": "If true, don't use Buf when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Buf when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--buf-format-skip", "--no-buf-format-skip"], @@ -49998,7 +49998,7 @@ "display_args": ["--[no-]buf-lint-skip"], "env_var": "PANTS_BUF_LINT_SKIP", "fromfile": false, - "help": "If true, don't use Buf when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Buf when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--buf-lint-skip", "--no-buf-lint-skip"], @@ -50112,7 +50112,7 @@ "display_args": ["--[no-]build-deprecations-fixer-skip"], "env_var": "PANTS_BUILD_DEPRECATIONS_FIXER_SKIP", "fromfile": false, - "help": "If true, don't use BUILD Deprecations Fixer when running `scie-pants-linux-x86_64 fix`.", + "help": "If true, don't use BUILD Deprecations Fixer when running `pants fix`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -50351,7 +50351,7 @@ "display_args": ["--[no-]buildifier-skip"], "env_var": "PANTS_BUILDIFIER_SKIP", "fromfile": false, - "help": "If true, don't use Buildifier when running `scie-pants-linux-x86_64 fmt`.", + "help": "If true, don't use Buildifier when running `pants fmt`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--buildifier-skip", "--no-buildifier-skip"], @@ -50608,7 +50608,7 @@ "display_args": ["--cli-alias=\"{'key1': val1, 'key2': val2, ...}\""], "env_var": "PANTS_CLI_ALIAS", "fromfile": false, - "help": "Register command line aliases.\n\nExample:\n\n [cli.alias]\n green = \"fmt lint check\"\n all-changed = \"--changed-since=HEAD --changed-dependents=transitive\"\n\nThis would allow you to run `scie-pants-linux-x86_64 green all-changed`, which is shorthand for `scie-pants-linux-x86_64 fmt lint check --changed-since=HEAD --changed-dependents=transitive`.\n\nNotice: this option must be placed in a config file (e.g. `pants.toml` or `pantsrc`) to have any effect.", + "help": "Register command line aliases.\n\nExample:\n\n [cli.alias]\n green = \"fmt lint check\"\n all-changed = \"--changed-since=HEAD --changed-dependents=transitive\"\n\nThis would allow you to run `pants green all-changed`, which is shorthand for `pants fmt lint check --changed-since=HEAD --changed-dependents=transitive`.\n\nNotice: this option must be placed in a config file (e.g. `pants.toml` or `pantsrc`) to have any effect.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--cli-alias"], @@ -51374,7 +51374,7 @@ "display_args": ["--coverage-py-lockfile="], "env_var": "PANTS_COVERAGE_PY_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/python/subsystems/coverage_py.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=coverage-py`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/python/subsystems/coverage_py.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=coverage-py`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": "Custom tool versions are now installed from named resolves, as described at https://www.pantsbuild.org/v2.16/docs/python-lockfiles.\n\n1. If you have an existing resolve that includes the requirements for this tool,\n you can set `[coverage-py].install_from_resolve = \"\".\n This may be the case if the tool also provides a runtime library, and you want\n to specify the version in just one place.\n2. If not, you can set up a new resolve as described at the link above.\n\nEither way, the resolve you choose should provide the requirements currently set by the `version` and `extra-requirements` options for this tool, which you can see by running `pants help-advanced coverage-py`.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--coverage-py-lockfile"], @@ -51759,7 +51759,7 @@ "display_args": ["--debugpy-lockfile="], "env_var": "PANTS_DEBUGPY_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/python/subsystems/debugpy.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=debugpy`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/python/subsystems/debugpy.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=debugpy`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": "Custom tool versions are now installed from named resolves, as described at https://www.pantsbuild.org/v2.16/docs/python-lockfiles.\n\n1. If you have an existing resolve that includes the requirements for this tool,\n you can set `[debugpy].install_from_resolve = \"\".\n This may be the case if the tool also provides a runtime library, and you want\n to specify the version in just one place.\n2. If not, you can set up a new resolve as described at the link above.\n\nEither way, the resolve you choose should provide the requirements currently set by the `version` and `extra-requirements` options for this tool, which you can see by running `pants help-advanced debugpy`.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--debugpy-lockfile"], @@ -52394,7 +52394,7 @@ "display_args": ["--[no-]docformatter-skip"], "env_var": "PANTS_DOCFORMATTER_SKIP", "fromfile": false, - "help": "If true, don't use docformatter when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use docformatter when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -52535,7 +52535,7 @@ "display_args": ["--docformatter-lockfile="], "env_var": "PANTS_DOCFORMATTER_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/python/lint/docformatter/docformatter.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=docformatter`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/python/lint/docformatter/docformatter.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=docformatter`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": "Custom tool versions are now installed from named resolves, as described at https://www.pantsbuild.org/v2.16/docs/python-lockfiles.\n\n1. If you have an existing resolve that includes the requirements for this tool,\n you can set `[docformatter].install_from_resolve = \"\".\n This may be the case if the tool also provides a runtime library, and you want\n to specify the version in just one place.\n2. If not, you can set up a new resolve as described at the link above.\n\nEither way, the resolve you choose should provide the requirements currently set by the `version` and `extra-requirements` options for this tool, which you can see by running `pants help-advanced docformatter`.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--docformatter-lockfile"], @@ -52568,7 +52568,7 @@ "display_args": ["--[no-]docformatter-export"], "env_var": "PANTS_DOCFORMATTER_EXPORT", "fromfile": false, - "help": "If true, export a virtual environment with docformatter when running `scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with docformatter when running `pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": "Use the export goal's --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": [ @@ -52953,7 +52953,7 @@ ], "env_var": "PANTS_DOCKER_RUN_ARGS", "fromfile": false, - "help": "Additional arguments to use for `docker run` invocations.\n\nExample:\n\n $ scie-pants-linux-x86_64 run --docker-run-args=\"-p 127.0.0.1:80:8080/tcp --name demo\" src/example:image -- [image entrypoint args]\n\nTo provide the top-level options to the `docker` client, use `[docker].env_vars` to configure the [Environment variables](https://docs.docker.com/engine/reference/commandline/cli/#environment-variables) as appropriate.\n\nThe arguments for the image entrypoint may be passed on the command line after a double dash (`--`), or using the `--run-args` option.\n\nDefaults to `--interactive --tty` when stdout is connected to a terminal.", + "help": "Additional arguments to use for `docker run` invocations.\n\nExample:\n\n $ pants run --docker-run-args=\"-p 127.0.0.1:80:8080/tcp --name demo\" src/example:image -- [image entrypoint args]\n\nTo provide the top-level options to the `docker` client, use `[docker].env_vars` to configure the [Environment variables](https://docs.docker.com/engine/reference/commandline/cli/#environment-variables) as appropriate.\n\nThe arguments for the image entrypoint may be passed on the command line after a double dash (`--`), or using the `--run-args` option.\n\nDefaults to `--interactive --tty` when stdout is connected to a terminal.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--docker-run-args"], @@ -53167,7 +53167,7 @@ "display_args": ["--dockerfile-parser-lockfile="], "env_var": "PANTS_DOCKERFILE_PARSER_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/docker/subsystems/dockerfile.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=dockerfile-parser`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/docker/subsystems/dockerfile.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=dockerfile-parser`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": "Custom tool versions are now installed from named resolves, as described at https://www.pantsbuild.org/v2.16/docs/python-lockfiles.\n\n1. If you have an existing resolve that includes the requirements for this tool,\n you can set `[dockerfile-parser].install_from_resolve = \"\".\n This may be the case if the tool also provides a runtime library, and you want\n to specify the version in just one place.\n2. If not, you can set up a new resolve as described at the link above.\n\nEither way, the resolve you choose should provide the requirements currently set by the `version` and `extra-requirements` options for this tool, which you can see by running `pants help-advanced dockerfile-parser`.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--dockerfile-parser-lockfile"], @@ -53869,7 +53869,7 @@ ], "env_var": "PANTS_EXPERIMENTAL_BSP_RUNNER_ENV_VARS", "fromfile": false, - "help": "Environment variables to set in the BSP runner script when setting up BSP in a repository. Entries are either strings in the form `ENV_VAR=value` to set an explicit value; or just `ENV_VAR` to copy the value from Pants' own environment when the experimental-bsp goal was run.\n\nThis option only takes effect when the BSP runner script is written. If the option changes, you must run `scie-pants-linux-x86_64 experimental-bsp` again to write a new copy of the BSP runner script.\n\nNote: The environment variables passed to the Pants BSP server will be those set for your IDE and not your shell. For example, on macOS, the IDE is generally launched by `launchd` after clicking on a Dock icon, and not from the shell. Thus, any environment variables set for your shell will likely not be seen by the Pants BSP server. At the very least, on macOS consider writing an explicit PATH into the BSP runner script via this option.", + "help": "Environment variables to set in the BSP runner script when setting up BSP in a repository. Entries are either strings in the form `ENV_VAR=value` to set an explicit value; or just `ENV_VAR` to copy the value from Pants' own environment when the experimental-bsp goal was run.\n\nThis option only takes effect when the BSP runner script is written. If the option changes, you must run `pants experimental-bsp` again to write a new copy of the BSP runner script.\n\nNote: The environment variables passed to the Pants BSP server will be those set for your IDE and not your shell. For example, on macOS, the IDE is generally launched by `launchd` after clicking on a Dock icon, and not from the shell. Thus, any environment variables set for your shell will likely not be seen by the Pants BSP server. At the very least, on macOS consider writing an explicit PATH into the BSP runner script via this option.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--experimental-bsp-runner-env-vars"], @@ -54620,7 +54620,7 @@ "display_args": ["--[no-]fix-skip-formatters"], "env_var": "PANTS_FIX_SKIP_FORMATTERS", "fromfile": false, - "help": "If true, skip running all formatters.\n\nFYI: when running `scie-pants-linux-x86_64 fix fmt ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `fix` where possible.", + "help": "If true, skip running all formatters.\n\nFYI: when running `pants fix fmt ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `fix` where possible.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -54930,7 +54930,7 @@ "display_args": ["--[no-]flake8-skip"], "env_var": "PANTS_FLAKE8_SKIP", "fromfile": false, - "help": "If true, don't use Flake8 when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Flake8 when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--flake8-skip", "--no-flake8-skip"], @@ -55066,7 +55066,7 @@ "display_args": ["--flake8-lockfile="], "env_var": "PANTS_FLAKE8_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/python/lint/flake8/flake8.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=flake8`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/python/lint/flake8/flake8.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=flake8`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": "Custom tool versions are now installed from named resolves, as described at https://www.pantsbuild.org/v2.16/docs/python-lockfiles.\n\n1. If you have an existing resolve that includes the requirements for this tool,\n you can set `[flake8].install_from_resolve = \"\".\n This may be the case if the tool also provides a runtime library, and you want\n to specify the version in just one place.\n2. If not, you can set up a new resolve as described at the link above.\n\nEither way, the resolve you choose should provide the requirements currently set by the `version` and `extra-requirements` options for this tool, which you can see by running `pants help-advanced flake8`.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--flake8-lockfile"], @@ -55099,7 +55099,7 @@ "display_args": ["--[no-]flake8-export"], "env_var": "PANTS_FLAKE8_EXPORT", "fromfile": false, - "help": "If true, export a virtual environment with Flake8 when running `scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with Flake8 when running `pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": "Use the export goal's --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--flake8-export", "--no-flake8-export"], @@ -55219,7 +55219,7 @@ "display_args": ["--generate-lockfiles-custom-command="], "env_var": "PANTS_GENERATE_LOCKFILES_CUSTOM_COMMAND", "fromfile": false, - "help": "If set, lockfile headers will say to run this command to regenerate the lockfile, rather than running `scie-pants-linux-x86_64 generate-lockfiles --resolve=` like normal.", + "help": "If set, lockfile headers will say to run this command to regenerate the lockfile, rather than running `pants generate-lockfiles --resolve=` like normal.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--generate-lockfiles-custom-command"], @@ -55251,7 +55251,7 @@ ], "env_var": "PANTS_GENERATE_LOCKFILES_RESOLVE", "fromfile": false, - "help": "Only generate lockfiles for the specified resolve(s).\n\nResolves are the logical names for the different lockfiles used in your project. For your own code's dependencies, these come from backend-specific configuration such as `[python].resolves`. For tool lockfiles, resolve names are the options scope for that tool such as `black`, `pytest`, and `mypy-protobuf`.\n\nFor example, you can run `scie-pants-linux-x86_64 generate-lockfiles --resolve=black --resolve=pytest --resolve=data-science` to only generate lockfiles for those two tools and your resolve named `data-science`.\n\nIf you specify an invalid resolve name, like 'fake', Pants will output all possible values.\n\nIf not specified, Pants will generate lockfiles for all resolves.", + "help": "Only generate lockfiles for the specified resolve(s).\n\nResolves are the logical names for the different lockfiles used in your project. For your own code's dependencies, these come from backend-specific configuration such as `[python].resolves`. For tool lockfiles, resolve names are the options scope for that tool such as `black`, `pytest`, and `mypy-protobuf`.\n\nFor example, you can run `pants generate-lockfiles --resolve=black --resolve=pytest --resolve=data-science` to only generate lockfiles for those two tools and your resolve named `data-science`.\n\nIf you specify an invalid resolve name, like 'fake', Pants will output all possible values.\n\nIf not specified, Pants will generate lockfiles for all resolves.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--generate-lockfiles-resolve"], @@ -55629,7 +55629,7 @@ "display_args": ["--[no-]go-test-skip"], "env_var": "PANTS_GO_TEST_SKIP", "fromfile": false, - "help": "If true, don't use Go test binary when running `scie-pants-linux-x86_64 test`.", + "help": "If true, don't use Go test binary when running `pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--go-test-skip", "--no-go-test-skip"], @@ -55958,7 +55958,7 @@ "display_args": ["--[no-]gofmt-skip"], "env_var": "PANTS_GOFMT_SKIP", "fromfile": false, - "help": "If true, don't use gofmt when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use gofmt when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--gofmt-skip", "--no-gofmt-skip"], @@ -56745,7 +56745,7 @@ "display_args": ["--google-java-format-lockfile="], "env_var": "PANTS_GOOGLE_JAVA_FORMAT_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/java/lint/google_java_format/google_java_format.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=google-java-format`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/java/lint/google_java_format/google_java_format.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=google-java-format`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--google-java-format-lockfile"], @@ -56815,7 +56815,7 @@ "display_args": ["--[no-]google-java-format-skip"], "env_var": "PANTS_GOOGLE_JAVA_FORMAT_SKIP", "fromfile": false, - "help": "If true, don't use Google Java Format when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Google Java Format when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -57361,7 +57361,7 @@ "display_args": ["--[no-]hadolint-skip"], "env_var": "PANTS_HADOLINT_SKIP", "fromfile": false, - "help": "If true, don't use Hadolint when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Hadolint when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--hadolint-skip", "--no-hadolint-skip"], @@ -58018,7 +58018,7 @@ "display_args": ["--helm-k8s-parser-lockfile="], "env_var": "PANTS_HELM_K8S_PARSER_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/helm/subsystems/k8s_parser.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=helm-k8s-parser`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/helm/subsystems/k8s_parser.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=helm-k8s-parser`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": "Custom tool versions are now installed from named resolves, as described at https://www.pantsbuild.org/v2.16/docs/python-lockfiles.\n\n1. If you have an existing resolve that includes the requirements for this tool,\n you can set `[helm-k8s-parser].install_from_resolve = \"\".\n This may be the case if the tool also provides a runtime library, and you want\n to specify the version in just one place.\n2. If not, you can set up a new resolve as described at the link above.\n\nEither way, the resolve you choose should provide the requirements currently set by the `version` and `extra-requirements` options for this tool, which you can see by running `pants help-advanced helm-k8s-parser`.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--helm-k8s-parser-lockfile"], @@ -58235,7 +58235,7 @@ "display_args": ["--helm-post-renderer-lockfile="], "env_var": "PANTS_HELM_POST_RENDERER_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/helm/subsystems/post_renderer.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=helm-post-renderer`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/helm/subsystems/post_renderer.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=helm-post-renderer`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": "Custom tool versions are now installed from named resolves, as described at https://www.pantsbuild.org/v2.16/docs/python-lockfiles.\n\n1. If you have an existing resolve that includes the requirements for this tool,\n you can set `[helm-post-renderer].install_from_resolve = \"\".\n This may be the case if the tool also provides a runtime library, and you want\n to specify the version in just one place.\n2. If not, you can set up a new resolve as described at the link above.\n\nEither way, the resolve you choose should provide the requirements currently set by the `version` and `extra-requirements` options for this tool, which you can see by running `pants help-advanced helm-post-renderer`.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--helm-post-renderer-lockfile"], @@ -58541,7 +58541,7 @@ "display_args": ["--[no-]helm-unittest-skip"], "env_var": "PANTS_HELM_UNITTEST_SKIP", "fromfile": false, - "help": "If true, don't use helmunittestsubsystem when running `scie-pants-linux-x86_64 test`.", + "help": "If true, don't use helmunittestsubsystem when running `pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -58848,7 +58848,7 @@ "display_args": ["--ipython-lockfile="], "env_var": "PANTS_IPYTHON_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/python/subsystems/ipython.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=ipython`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/python/subsystems/ipython.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=ipython`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": "Custom tool versions are now installed from named resolves, as described at https://www.pantsbuild.org/v2.16/docs/python-lockfiles.\n\n1. If you have an existing resolve that includes the requirements for this tool,\n you can set `[ipython].install_from_resolve = \"\".\n This may be the case if the tool also provides a runtime library, and you want\n to specify the version in just one place.\n2. If not, you can set up a new resolve as described at the link above.\n\nEither way, the resolve you choose should provide the requirements currently set by the `version` and `extra-requirements` options for this tool, which you can see by running `pants help-advanced ipython`.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--ipython-lockfile"], @@ -59123,7 +59123,7 @@ "display_args": ["--[no-]isort-skip"], "env_var": "PANTS_ISORT_SKIP", "fromfile": false, - "help": "If true, don't use isort when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use isort when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--isort-skip", "--no-isort-skip"], @@ -59259,7 +59259,7 @@ "display_args": ["--isort-lockfile="], "env_var": "PANTS_ISORT_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/python/lint/isort/isort.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=isort`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/python/lint/isort/isort.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=isort`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": "Custom tool versions are now installed from named resolves, as described at https://www.pantsbuild.org/v2.16/docs/python-lockfiles.\n\n1. If you have an existing resolve that includes the requirements for this tool,\n you can set `[isort].install_from_resolve = \"\".\n This may be the case if the tool also provides a runtime library, and you want\n to specify the version in just one place.\n2. If not, you can set up a new resolve as described at the link above.\n\nEither way, the resolve you choose should provide the requirements currently set by the `version` and `extra-requirements` options for this tool, which you can see by running `pants help-advanced isort`.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--isort-lockfile"], @@ -59292,7 +59292,7 @@ "display_args": ["--[no-]isort-export"], "env_var": "PANTS_ISORT_EXPORT", "fromfile": false, - "help": "If true, export a virtual environment with isort when running `scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with isort when running `pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": "Use the export goal's --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--isort-export", "--no-isort-export"], @@ -59400,7 +59400,7 @@ "display_args": ["--jarjar-lockfile="], "env_var": "PANTS_JARJAR_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/jvm/shading/jarjar.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=jarjar`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/jvm/shading/jarjar.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=jarjar`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--jarjar-lockfile"], @@ -59820,7 +59820,7 @@ "display_args": ["--junit-lockfile="], "env_var": "PANTS_JUNIT_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/jvm/test/junit.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=junit`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/jvm/test/junit.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=junit`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--junit-lockfile"], @@ -59924,7 +59924,7 @@ "display_args": ["--[no-]junit-skip"], "env_var": "PANTS_JUNIT_SKIP", "fromfile": false, - "help": "If true, don't use JUnit when running `scie-pants-linux-x86_64 test`.", + "help": "If true, don't use JUnit when running `pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--junit-skip", "--no-junit-skip"], @@ -60577,7 +60577,7 @@ "display_args": ["--ktlint-lockfile="], "env_var": "PANTS_KTLINT_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/kotlin/lint/ktlint/ktlint.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=ktlint`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/kotlin/lint/ktlint/ktlint.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=ktlint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--ktlint-lockfile"], @@ -60645,7 +60645,7 @@ "display_args": ["--[no-]ktlint-skip"], "env_var": "PANTS_KTLINT_SKIP", "fromfile": false, - "help": "If true, don't use Ktlint when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Ktlint when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--ktlint-skip", "--no-ktlint-skip"], @@ -60918,7 +60918,7 @@ "display_args": ["--lambdex-lockfile="], "env_var": "PANTS_LAMBDEX_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/python/subsystems/lambdex.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=lambdex`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/python/subsystems/lambdex.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=lambdex`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": "Custom tool versions are now installed from named resolves, as described at https://www.pantsbuild.org/v2.16/docs/python-lockfiles.\n\n1. If you have an existing resolve that includes the requirements for this tool,\n you can set `[lambdex].install_from_resolve = \"\".\n This may be the case if the tool also provides a runtime library, and you want\n to specify the version in just one place.\n2. If not, you can set up a new resolve as described at the link above.\n\nEither way, the resolve you choose should provide the requirements currently set by the `version` and `extra-requirements` options for this tool, which you can see by running `pants help-advanced lambdex`.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--lambdex-lockfile"], @@ -61028,7 +61028,7 @@ "display_args": ["--[no-]lint-skip-formatters"], "env_var": "PANTS_LINT_SKIP_FORMATTERS", "fromfile": false, - "help": "If true, skip running all formatters in check-only mode.\n\nFYI: when running `scie-pants-linux-x86_64 fmt lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `lint` where possible.", + "help": "If true, skip running all formatters in check-only mode.\n\nFYI: when running `pants fmt lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `lint` where possible.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -61067,7 +61067,7 @@ "display_args": ["--[no-]lint-skip-fixers"], "env_var": "PANTS_LINT_SKIP_FIXERS", "fromfile": false, - "help": "If true, skip running all fixers in check-only mode.\n\nFYI: when running `scie-pants-linux-x86_64 fix lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fix` when running `lint` where possible.", + "help": "If true, skip running all fixers in check-only mode.\n\nFYI: when running `pants fix lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fix` when running `lint` where possible.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -61479,7 +61479,7 @@ "display_args": ["--[no-]mypy-skip"], "env_var": "PANTS_MYPY_SKIP", "fromfile": false, - "help": "If true, don't use MyPy when running `scie-pants-linux-x86_64 check`.", + "help": "If true, don't use MyPy when running `pants check`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--mypy-skip", "--no-mypy-skip"], @@ -61615,7 +61615,7 @@ "display_args": ["--mypy-lockfile="], "env_var": "PANTS_MYPY_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/python/typecheck/mypy/mypy.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=mypy`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/python/typecheck/mypy/mypy.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=mypy`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": "Custom tool versions are now installed from named resolves, as described at https://www.pantsbuild.org/v2.16/docs/python-lockfiles.\n\n1. If you have an existing resolve that includes the requirements for this tool,\n you can set `[mypy].install_from_resolve = \"\".\n This may be the case if the tool also provides a runtime library, and you want\n to specify the version in just one place.\n2. If not, you can set up a new resolve as described at the link above.\n\nEither way, the resolve you choose should provide the requirements currently set by the `version` and `extra-requirements` options for this tool, which you can see by running `pants help-advanced mypy`.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--mypy-lockfile"], @@ -61648,7 +61648,7 @@ "display_args": ["--[no-]mypy-export"], "env_var": "PANTS_MYPY_EXPORT", "fromfile": false, - "help": "If true, export a virtual environment with MyPy when running `scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with MyPy when running `pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": "Use the export goal's --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--mypy-export", "--no-mypy-export"], @@ -61716,7 +61716,7 @@ "display_args": ["--mypy-extra-type-stubs-lockfile="], "env_var": "PANTS_MYPY_EXTRA_TYPE_STUBS_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile for the option `[mypy].extra_type_stubs`.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this if you use `[mypy].extra_type_stubs`, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=mypy-extra-type-stubs`.", + "help": "Path to a lockfile for the option `[mypy].extra_type_stubs`.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this if you use `[mypy].extra_type_stubs`, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=mypy-extra-type-stubs`.", "removal_hint": "Extra type stubs are now installed from a named resolve, as described at https://www.pantsbuild.org/v2.16/docs/python-lockfiles.", "removal_version": "2.18.0dev0", "scoped_cmd_line_args": ["--mypy-extra-type-stubs-lockfile"], @@ -61927,7 +61927,7 @@ "display_args": ["--mypy-protobuf-lockfile="], "env_var": "PANTS_MYPY_PROTOBUF_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/codegen/protobuf/python/mypy_protobuf.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=mypy-protobuf`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/codegen/protobuf/python/mypy_protobuf.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=mypy-protobuf`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": "Custom tool versions are now installed from named resolves, as described at https://www.pantsbuild.org/v2.16/docs/python-lockfiles.\n\n1. If you have an existing resolve that includes the requirements for this tool,\n you can set `[mypy-protobuf].install_from_resolve = \"\".\n This may be the case if the tool also provides a runtime library, and you want\n to specify the version in just one place.\n2. If not, you can set up a new resolve as described at the link above.\n\nEither way, the resolve you choose should provide the requirements currently set by the `version` and `extra-requirements` options for this tool, which you can see by running `pants help-advanced mypy-protobuf`.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--mypy-protobuf-lockfile"], @@ -62834,7 +62834,7 @@ "display_args": ["--[no-]preamble-skip"], "env_var": "PANTS_PREAMBLE_SKIP", "fromfile": false, - "help": "If true, don't use preamble when running `scie-pants-linux-x86_64 fmt`.", + "help": "If true, don't use preamble when running `pants fmt`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--preamble-skip", "--no-preamble-skip"], @@ -62990,7 +62990,7 @@ "display_args": ["--protobuf-java-grpc-lockfile="], "env_var": "PANTS_PROTOBUF_JAVA_GRPC_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/codegen/protobuf/java/grpc-java.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=protobuf-java-grpc`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/codegen/protobuf/java/grpc-java.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=protobuf-java-grpc`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--protobuf-java-grpc-lockfile"], @@ -63725,7 +63725,7 @@ "display_args": ["--[no-]pydocstyle-skip"], "env_var": "PANTS_PYDOCSTYLE_SKIP", "fromfile": false, - "help": "If true, don't use Pydocstyle when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Pydocstyle when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pydocstyle-skip", "--no-pydocstyle-skip"], @@ -63863,7 +63863,7 @@ "display_args": ["--pydocstyle-lockfile="], "env_var": "PANTS_PYDOCSTYLE_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/python/lint/pydocstyle/pydocstyle.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=pydocstyle`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/python/lint/pydocstyle/pydocstyle.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=pydocstyle`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": "Custom tool versions are now installed from named resolves, as described at https://www.pantsbuild.org/v2.16/docs/python-lockfiles.\n\n1. If you have an existing resolve that includes the requirements for this tool,\n you can set `[pydocstyle].install_from_resolve = \"\".\n This may be the case if the tool also provides a runtime library, and you want\n to specify the version in just one place.\n2. If not, you can set up a new resolve as described at the link above.\n\nEither way, the resolve you choose should provide the requirements currently set by the `version` and `extra-requirements` options for this tool, which you can see by running `pants help-advanced pydocstyle`.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--pydocstyle-lockfile"], @@ -63896,7 +63896,7 @@ "display_args": ["--[no-]pydocstyle-export"], "env_var": "PANTS_PYDOCSTYLE_EXPORT", "fromfile": false, - "help": "If true, export a virtual environment with Pydocstyle when running `scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with Pydocstyle when running `pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": "Use the export goal's --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": [ @@ -64167,7 +64167,7 @@ "display_args": ["--[no-]pylint-skip"], "env_var": "PANTS_PYLINT_SKIP", "fromfile": false, - "help": "If true, don't use Pylint when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Pylint when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pylint-skip", "--no-pylint-skip"], @@ -64303,7 +64303,7 @@ "display_args": ["--pylint-lockfile="], "env_var": "PANTS_PYLINT_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/python/lint/pylint/pylint.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=pylint`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/python/lint/pylint/pylint.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=pylint`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": "Custom tool versions are now installed from named resolves, as described at https://www.pantsbuild.org/v2.16/docs/python-lockfiles.\n\n1. If you have an existing resolve that includes the requirements for this tool,\n you can set `[pylint].install_from_resolve = \"\".\n This may be the case if the tool also provides a runtime library, and you want\n to specify the version in just one place.\n2. If not, you can set up a new resolve as described at the link above.\n\nEither way, the resolve you choose should provide the requirements currently set by the `version` and `extra-requirements` options for this tool, which you can see by running `pants help-advanced pylint`.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--pylint-lockfile"], @@ -64336,7 +64336,7 @@ "display_args": ["--[no-]pylint-export"], "env_var": "PANTS_PYLINT_EXPORT", "fromfile": false, - "help": "If true, export a virtual environment with Pylint when running `scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with Pylint when running `pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": "Use the export goal's --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--pylint-export", "--no-pylint-export"], @@ -64644,7 +64644,7 @@ "display_args": ["--pyoxidizer-lockfile="], "env_var": "PANTS_PYOXIDIZER_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/python/packaging/pyoxidizer/pyoxidizer.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=pyoxidizer`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/python/packaging/pyoxidizer/pyoxidizer.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=pyoxidizer`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": "Custom tool versions are now installed from named resolves, as described at https://www.pantsbuild.org/v2.16/docs/python-lockfiles.\n\n1. If you have an existing resolve that includes the requirements for this tool,\n you can set `[pyoxidizer].install_from_resolve = \"\".\n This may be the case if the tool also provides a runtime library, and you want\n to specify the version in just one place.\n2. If not, you can set up a new resolve as described at the link above.\n\nEither way, the resolve you choose should provide the requirements currently set by the `version` and `extra-requirements` options for this tool, which you can see by running `pants help-advanced pyoxidizer`.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--pyoxidizer-lockfile"], @@ -65010,7 +65010,7 @@ "display_args": ["--[no-]pytest-skip"], "env_var": "PANTS_PYTEST_SKIP", "fromfile": false, - "help": "If true, don't use Pytest when running `scie-pants-linux-x86_64 test`.", + "help": "If true, don't use Pytest when running `pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pytest-skip", "--no-pytest-skip"], @@ -65116,7 +65116,7 @@ "display_args": ["--pytest-lockfile="], "env_var": "PANTS_PYTEST_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/python/subsystems/pytest.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=pytest`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/python/subsystems/pytest.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=pytest`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": "Custom tool versions are now installed from named resolves, as described at https://www.pantsbuild.org/v2.16/docs/python-lockfiles.\n\n1. If you have an existing resolve that includes the requirements for this tool,\n you can set `[pytest].install_from_resolve = \"\".\n This may be the case if the tool also provides a runtime library, and you want\n to specify the version in just one place.\n2. If not, you can set up a new resolve as described at the link above.\n\nEither way, the resolve you choose should provide the requirements currently set by the `version` and `extra-requirements` options for this tool, which you can see by running `pants help-advanced pytest`.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--pytest-lockfile"], @@ -65149,7 +65149,7 @@ "display_args": ["--[no-]pytest-export"], "env_var": "PANTS_PYTEST_EXPORT", "fromfile": false, - "help": "If true, export a virtual environment with Pytest when running `scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with Pytest when running `pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": "Use the export goal's --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--pytest-export", "--no-pytest-export"], @@ -65313,7 +65313,7 @@ ], "env_var": "PANTS_PYTHON_RESOLVES", "fromfile": false, - "help": "A mapping of logical names to lockfile paths used in your project.\n\nMany organizations only need a single resolve for their whole project, which is a good default and often the simplest thing to do. However, you may need multiple resolves, such as if you use two conflicting versions of a requirement in your repository.\n\nIf you only need a single resolve, run `scie-pants-linux-x86_64 generate-lockfiles` to generate the lockfile.\n\nIf you need multiple resolves:\n\n 1. Via this option, define multiple resolve names and their lockfile paths. The names should be meaningful to your repository, such as `data-science` or `pants-plugins`.\n 2. Set the default with `[python].default_resolve`.\n 3. Update your `python_requirement` targets with the `resolve` field to declare which resolve they should be available in. They default to `[python].default_resolve`, so you only need to update targets that you want in non-default resolves. (Often you'll set this via the `python_requirements` or `poetry_requirements` target generators)\n 4. Run `scie-pants-linux-x86_64 generate-lockfiles` to generate the lockfiles. If the results aren't what you'd expect, adjust the prior step.\n 5. Update any targets like `python_source` / `python_sources`, `python_test` / `python_tests`, and `pex_binary` which need to set a non-default resolve with the `resolve` field.\n\nIf a target can work with multiple resolves, you can either use the `parametrize` mechanism or manually create a distinct target per resolve. See https://www.pantsbuild.org/v2.16/docs/targets for information about `parametrize`.\n\nFor example:\n\n python_sources(\n resolve=parametrize(\"data-science\", \"web-app\"),\n )\n\nYou can name the lockfile paths what you would like; Pants does not expect a certain file extension or location.\n\nOnly applies if `[python].enable_resolves` is true.", + "help": "A mapping of logical names to lockfile paths used in your project.\n\nMany organizations only need a single resolve for their whole project, which is a good default and often the simplest thing to do. However, you may need multiple resolves, such as if you use two conflicting versions of a requirement in your repository.\n\nIf you only need a single resolve, run `pants generate-lockfiles` to generate the lockfile.\n\nIf you need multiple resolves:\n\n 1. Via this option, define multiple resolve names and their lockfile paths. The names should be meaningful to your repository, such as `data-science` or `pants-plugins`.\n 2. Set the default with `[python].default_resolve`.\n 3. Update your `python_requirement` targets with the `resolve` field to declare which resolve they should be available in. They default to `[python].default_resolve`, so you only need to update targets that you want in non-default resolves. (Often you'll set this via the `python_requirements` or `poetry_requirements` target generators)\n 4. Run `pants generate-lockfiles` to generate the lockfiles. If the results aren't what you'd expect, adjust the prior step.\n 5. Update any targets like `python_source` / `python_sources`, `python_test` / `python_tests`, and `pex_binary` which need to set a non-default resolve with the `resolve` field.\n\nIf a target can work with multiple resolves, you can either use the `parametrize` mechanism or manually create a distinct target per resolve. See https://www.pantsbuild.org/v2.16/docs/targets for information about `parametrize`.\n\nFor example:\n\n python_sources(\n resolve=parametrize(\"data-science\", \"web-app\"),\n )\n\nYou can name the lockfile paths what you would like; Pants does not expect a certain file extension or location.\n\nOnly applies if `[python].enable_resolves` is true.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--python-resolves"], @@ -66062,7 +66062,7 @@ "env_var": "PANTS_PYTHON_REQUIREMENT_CONSTRAINTS", "fromfile": false, "help": "When resolving third-party requirements for your own code (vs. tools you run), use this constraints file to determine which versions to use.\n\nMutually exclusive with `[python].enable_resolves`, which we generally recommend as an improvement over constraints file.\n\nSee https://pip.pypa.io/en/stable/user_guide/#constraints-files for more information on the format of constraint files and how constraints are applied in Pex and pip.\n\nThis only applies when resolving user requirements, rather than tools you run like Black and Pytest. To constrain tools, set `[tool].lockfile`, e.g. `[black].lockfile`.", - "removal_hint": "We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.\n\nTo migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `scie-pants-linux-x86_64 generate-lockfiles`.", + "removal_hint": "We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.\n\nTo migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `pants generate-lockfiles`.", "removal_version": "3.0.0.dev0", "scoped_cmd_line_args": ["--python-requirement-constraints"], "target_field_name": null, @@ -66090,7 +66090,7 @@ "env_var": "PANTS_PYTHON_RESOLVE_ALL_CONSTRAINTS", "fromfile": false, "help": "(Only relevant when using `[python].requirement_constraints.`) If enabled, when resolving requirements, Pants will first resolve your entire constraints file as a single global resolve. Then, if the code uses a subset of your constraints file, Pants will extract the relevant requirements from that global resolve so that only what's actually needed gets used. If disabled, Pants will not use a global resolve and will resolve each subset of your requirements independently.\n\nUsually this option should be enabled because it can result in far fewer resolves.", - "removal_hint": "We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.\n\nTo migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `scie-pants-linux-x86_64 generate-lockfiles`.", + "removal_hint": "We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.\n\nTo migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `pants generate-lockfiles`.", "removal_version": "3.0.0.dev0", "scoped_cmd_line_args": [ "--python-resolve-all-constraints", @@ -66520,7 +66520,7 @@ "display_args": ["--python-infer-init-files="], "env_var": "PANTS_PYTHON_INFER_INIT_FILES", "fromfile": false, - "help": "Infer a target's dependencies on any `__init__.py` files in the packages it is located in (recursively upward in the directory structure).\n\nEven if this is set to `never` or `content_only`, Pants will still always include any ancestor `__init__.py` files in the sandbox. Only, they will not be \"proper\" dependencies, e.g. they will not show up in `scie-pants-linux-x86_64 dependencies` and their own dependencies will not be used.\n\nBy default, Pants only adds a \"proper\" dependency if there is content in the `__init__.py` file. This makes sure that dependencies are added when likely necessary to build, while also avoiding adding unnecessary dependencies. While accurate, those unnecessary dependencies can complicate setting metadata like the `interpreter_constraints` and `resolve` fields.", + "help": "Infer a target's dependencies on any `__init__.py` files in the packages it is located in (recursively upward in the directory structure).\n\nEven if this is set to `never` or `content_only`, Pants will still always include any ancestor `__init__.py` files in the sandbox. Only, they will not be \"proper\" dependencies, e.g. they will not show up in `pants dependencies` and their own dependencies will not be used.\n\nBy default, Pants only adds a \"proper\" dependency if there is content in the `__init__.py` file. This makes sure that dependencies are added when likely necessary to build, while also avoiding adding unnecessary dependencies. While accurate, those unnecessary dependencies can complicate setting metadata like the `interpreter_constraints` and `resolve` fields.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--python-infer-init-files"], @@ -67308,7 +67308,7 @@ "display_args": ["--[no-]pyupgrade-skip"], "env_var": "PANTS_PYUPGRADE_SKIP", "fromfile": false, - "help": "If true, don't use pyupgrade when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use pyupgrade when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pyupgrade-skip", "--no-pyupgrade-skip"], @@ -67446,7 +67446,7 @@ "display_args": ["--pyupgrade-lockfile="], "env_var": "PANTS_PYUPGRADE_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/python/lint/pyupgrade/pyupgrade.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=pyupgrade`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/python/lint/pyupgrade/pyupgrade.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=pyupgrade`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": "Custom tool versions are now installed from named resolves, as described at https://www.pantsbuild.org/v2.16/docs/python-lockfiles.\n\n1. If you have an existing resolve that includes the requirements for this tool,\n you can set `[pyupgrade].install_from_resolve = \"\".\n This may be the case if the tool also provides a runtime library, and you want\n to specify the version in just one place.\n2. If not, you can set up a new resolve as described at the link above.\n\nEither way, the resolve you choose should provide the requirements currently set by the `version` and `extra-requirements` options for this tool, which you can see by running `pants help-advanced pyupgrade`.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--pyupgrade-lockfile"], @@ -67479,7 +67479,7 @@ "display_args": ["--[no-]pyupgrade-export"], "env_var": "PANTS_PYUPGRADE_EXPORT", "fromfile": false, - "help": "If true, export a virtual environment with pyupgrade when running `scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with pyupgrade when running `pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": "Use the export goal's --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": [ @@ -67525,7 +67525,7 @@ "display_args": ["--[no-]regex-lint-skip"], "env_var": "PANTS_REGEX_LINT_SKIP", "fromfile": false, - "help": "If true, don't use regex-lint when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use regex-lint when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--regex-lint-skip", "--no-regex-lint-skip"], @@ -68009,7 +68009,7 @@ "display_args": ["--[no-]ruff-skip"], "env_var": "PANTS_RUFF_SKIP", "fromfile": false, - "help": "If true, don't use Ruff when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Ruff when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--ruff-skip", "--no-ruff-skip"], @@ -68145,7 +68145,7 @@ "display_args": ["--ruff-lockfile="], "env_var": "PANTS_RUFF_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/python/lint/ruff/ruff.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=ruff`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/python/lint/ruff/ruff.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=ruff`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": "Custom tool versions are now installed from named resolves, as described at https://www.pantsbuild.org/v2.16/docs/python-lockfiles.\n\n1. If you have an existing resolve that includes the requirements for this tool,\n you can set `[ruff].install_from_resolve = \"\".\n This may be the case if the tool also provides a runtime library, and you want\n to specify the version in just one place.\n2. If not, you can set up a new resolve as described at the link above.\n\nEither way, the resolve you choose should provide the requirements currently set by the `version` and `extra-requirements` options for this tool, which you can see by running `pants help-advanced ruff`.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--ruff-lockfile"], @@ -68178,7 +68178,7 @@ "display_args": ["--[no-]ruff-export"], "env_var": "PANTS_RUFF_EXPORT", "fromfile": false, - "help": "If true, export a virtual environment with Ruff when running `scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with Ruff when running `pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": "Use the export goal's --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--ruff-export", "--no-ruff-export"], @@ -68697,7 +68697,7 @@ "display_args": ["--scalafmt-lockfile="], "env_var": "PANTS_SCALAFMT_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/scala/lint/scalafmt/scalafmt.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalafmt`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/scala/lint/scalafmt/scalafmt.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=scalafmt`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalafmt-lockfile"], @@ -68767,7 +68767,7 @@ "display_args": ["--[no-]scalafmt-skip"], "env_var": "PANTS_SCALAFMT_SKIP", "fromfile": false, - "help": "If true, don't use scalafmt when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use scalafmt when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalafmt-skip", "--no-scalafmt-skip"], @@ -68876,7 +68876,7 @@ "display_args": ["--scalapb-lockfile="], "env_var": "PANTS_SCALAPB_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/codegen/protobuf/scala/scalapbc.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalapb`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/codegen/protobuf/scala/scalapbc.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=scalapb`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalapb-lockfile"], @@ -69053,7 +69053,7 @@ "display_args": ["--scalatest-lockfile="], "env_var": "PANTS_SCALATEST_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/scala/subsystems/scalatest.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalatest`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/scala/subsystems/scalatest.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=scalatest`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalatest-lockfile"], @@ -69159,7 +69159,7 @@ "display_args": ["--[no-]scalatest-skip"], "env_var": "PANTS_SCALATEST_SKIP", "fromfile": false, - "help": "If true, don't use Scalatest when running `scie-pants-linux-x86_64 test`.", + "help": "If true, don't use Scalatest when running `pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalatest-skip", "--no-scalatest-skip"], @@ -69660,7 +69660,7 @@ "display_args": ["--setuptools-lockfile="], "env_var": "PANTS_SETUPTOOLS_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/python/subsystems/setuptools.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=setuptools`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/python/subsystems/setuptools.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=setuptools`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": "Custom tool versions are now installed from named resolves, as described at https://www.pantsbuild.org/v2.16/docs/python-lockfiles.\n\n1. If you have an existing resolve that includes the requirements for this tool,\n you can set `[setuptools].install_from_resolve = \"\".\n This may be the case if the tool also provides a runtime library, and you want\n to specify the version in just one place.\n2. If not, you can set up a new resolve as described at the link above.\n\nEither way, the resolve you choose should provide the requirements currently set by the `version` and `extra-requirements` options for this tool, which you can see by running `pants help-advanced setuptools`.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--setuptools-lockfile"], @@ -69932,7 +69932,7 @@ "display_args": ["--setuptools-scm-lockfile="], "env_var": "PANTS_SETUPTOOLS_SCM_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/python/subsystems/setuptools_scm.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=setuptools-scm`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/python/subsystems/setuptools_scm.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=setuptools-scm`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": "Custom tool versions are now installed from named resolves, as described at https://www.pantsbuild.org/v2.16/docs/python-lockfiles.\n\n1. If you have an existing resolve that includes the requirements for this tool,\n you can set `[setuptools-scm].install_from_resolve = \"\".\n This may be the case if the tool also provides a runtime library, and you want\n to specify the version in just one place.\n2. If not, you can set up a new resolve as described at the link above.\n\nEither way, the resolve you choose should provide the requirements currently set by the `version` and `extra-requirements` options for this tool, which you can see by running `pants help-advanced setuptools-scm`.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--setuptools-scm-lockfile"], @@ -70096,7 +70096,7 @@ "display_args": ["--[no-]shell-test-skip"], "env_var": "PANTS_SHELL_TEST_SKIP", "fromfile": false, - "help": "If true, don't use Test with shell scripts when running `scie-pants-linux-x86_64 test`.", + "help": "If true, don't use Test with shell scripts when running `pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--shell-test-skip", "--no-shell-test-skip"], @@ -70371,7 +70371,7 @@ "display_args": ["--[no-]shellcheck-skip"], "env_var": "PANTS_SHELLCHECK_SKIP", "fromfile": false, - "help": "If true, don't use Shellcheck when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Shellcheck when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--shellcheck-skip", "--no-shellcheck-skip"], @@ -70689,7 +70689,7 @@ "display_args": ["--[no-]shfmt-skip"], "env_var": "PANTS_SHFMT_SKIP", "fromfile": false, - "help": "If true, don't use shfmt when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use shfmt when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--shfmt-skip", "--no-shfmt-skip"], @@ -70943,7 +70943,7 @@ "display_args": ["--[no-]shunit2-skip"], "env_var": "PANTS_SHUNIT2_SKIP", "fromfile": false, - "help": "If true, don't use shunit2 when running `scie-pants-linux-x86_64 test`.", + "help": "If true, don't use shunit2 when running `pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--shunit2-skip", "--no-shunit2-skip"], @@ -71122,7 +71122,7 @@ "display_args": ["--[no-]spectral-skip"], "env_var": "PANTS_SPECTRAL_SKIP", "fromfile": false, - "help": "If true, don't use Spectral when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Spectral when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--spectral-skip", "--no-spectral-skip"], @@ -71581,7 +71581,7 @@ "display_args": ["--[no-]terraform-fmt-skip"], "env_var": "PANTS_TERRAFORM_FMT_SKIP", "fromfile": false, - "help": "If true, don't use `terraform fmt` when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use `terraform fmt` when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -71804,7 +71804,7 @@ "display_args": ["--terraform-hcl2-parser-lockfile="], "env_var": "PANTS_TERRAFORM_HCL2_PARSER_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/terraform/hcl2.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=terraform-hcl2-parser`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/terraform/hcl2.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=terraform-hcl2-parser`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": "Custom tool versions are now installed from named resolves, as described at https://www.pantsbuild.org/v2.16/docs/python-lockfiles.\n\n1. If you have an existing resolve that includes the requirements for this tool,\n you can set `[terraform-hcl2-parser].install_from_resolve = \"\".\n This may be the case if the tool also provides a runtime library, and you want\n to specify the version in just one place.\n2. If not, you can set up a new resolve as described at the link above.\n\nEither way, the resolve you choose should provide the requirements currently set by the `version` and `extra-requirements` options for this tool, which you can see by running `pants help-advanced terraform-hcl2-parser`.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--terraform-hcl2-parser-lockfile"], @@ -71847,7 +71847,7 @@ "display_args": ["--[no-]terraform-validate-skip"], "env_var": "PANTS_TERRAFORM_VALIDATE_SKIP", "fromfile": false, - "help": "If true, don't use `terraform validate` when running `scie-pants-linux-x86_64 check`.", + "help": "If true, don't use `terraform validate` when running `pants check`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -72709,7 +72709,7 @@ "display_args": ["--[no-]twine-skip"], "env_var": "PANTS_TWINE_SKIP", "fromfile": false, - "help": "If true, don't use Twine when running `scie-pants-linux-x86_64 publish`.", + "help": "If true, don't use Twine when running `pants publish`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--twine-skip", "--no-twine-skip"], @@ -72845,7 +72845,7 @@ "display_args": ["--twine-lockfile="], "env_var": "PANTS_TWINE_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/python/subsystems/twine.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=twine`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/python/subsystems/twine.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=twine`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": "Custom tool versions are now installed from named resolves, as described at https://www.pantsbuild.org/v2.16/docs/python-lockfiles.\n\n1. If you have an existing resolve that includes the requirements for this tool,\n you can set `[twine].install_from_resolve = \"\".\n This may be the case if the tool also provides a runtime library, and you want\n to specify the version in just one place.\n2. If not, you can set up a new resolve as described at the link above.\n\nEither way, the resolve you choose should provide the requirements currently set by the `version` and `extra-requirements` options for this tool, which you can see by running `pants help-advanced twine`.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--twine-lockfile"], @@ -73347,7 +73347,7 @@ "display_args": ["--[no-]yamllint-skip"], "env_var": "PANTS_YAMLLINT_SKIP", "fromfile": false, - "help": "If true, don't use Yamllint when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Yamllint when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--yamllint-skip", "--no-yamllint-skip"], @@ -73450,7 +73450,7 @@ "display_args": ["--yamllint-lockfile="], "env_var": "PANTS_YAMLLINT_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/tools/yamllint/yamllint.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=yamllint`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/tools/yamllint/yamllint.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=yamllint`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": "Custom tool versions are now installed from named resolves, as described at https://www.pantsbuild.org/v2.16/docs/python-lockfiles.\n\n1. If you have an existing resolve that includes the requirements for this tool,\n you can set `[yamllint].install_from_resolve = \"\".\n This may be the case if the tool also provides a runtime library, and you want\n to specify the version in just one place.\n2. If not, you can set up a new resolve as described at the link above.\n\nEither way, the resolve you choose should provide the requirements currently set by the `version` and `extra-requirements` options for this tool, which you can see by running `pants help-advanced yamllint`.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--yamllint-lockfile"], @@ -73483,7 +73483,7 @@ "display_args": ["--[no-]yamllint-export"], "env_var": "PANTS_YAMLLINT_EXPORT", "fromfile": false, - "help": "If true, export a virtual environment with Yamllint when running `scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with Yamllint when running `pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": "Use the export goal's --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--yamllint-export", "--no-yamllint-export"], @@ -73751,7 +73751,7 @@ "display_args": ["--[no-]yapf-skip"], "env_var": "PANTS_YAPF_SKIP", "fromfile": false, - "help": "If true, don't use yapf when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use yapf when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--yapf-skip", "--no-yapf-skip"], @@ -73887,7 +73887,7 @@ "display_args": ["--yapf-lockfile="], "env_var": "PANTS_YAPF_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/python/lint/yapf/yapf.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=yapf`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/python/lint/yapf/yapf.lock for the default lockfile contents.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=yapf`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": "Custom tool versions are now installed from named resolves, as described at https://www.pantsbuild.org/v2.16/docs/python-lockfiles.\n\n1. If you have an existing resolve that includes the requirements for this tool,\n you can set `[yapf].install_from_resolve = \"\".\n This may be the case if the tool also provides a runtime library, and you want\n to specify the version in just one place.\n2. If not, you can set up a new resolve as described at the link above.\n\nEither way, the resolve you choose should provide the requirements currently set by the `version` and `extra-requirements` options for this tool, which you can see by running `pants help-advanced yapf`.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--yapf-lockfile"], @@ -73920,7 +73920,7 @@ "display_args": ["--[no-]yapf-export"], "env_var": "PANTS_YAPF_EXPORT", "fromfile": false, - "help": "If true, export a virtual environment with yapf when running `scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with yapf when running `pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": "Use the export goal's --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--yapf-export", "--no-yapf-export"], diff --git a/versioned_docs/version-2.16/reference/subsystems/add-trailing-comma.mdx b/versioned_docs/version-2.16/reference/subsystems/add-trailing-comma.mdx index 212459e32..893573c5a 100644 --- a/versioned_docs/version-2.16/reference/subsystems/add-trailing-comma.mdx +++ b/versioned_docs/version-2.16/reference/subsystems/add-trailing-comma.mdx @@ -25,7 +25,7 @@ Config section: `[add-trailing-comma]` default_repr={`False`} > -If true, don't use add-trailing-comma when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use add-trailing-comma when running `pants fmt` and `pants lint`. @@ -163,7 +163,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=add-trailing-comma`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=add-trailing-comma`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. @@ -179,7 +179,7 @@ Alternatively, you can set this option to the path to a custom lockfile using pi removal_hint={'Use the export goal\'s --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.'} > -If true, export a virtual environment with add-trailing-comma when running `scie-pants-linux-x86_64 export`. +If true, export a virtual environment with add-trailing-comma when running `pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. diff --git a/versioned_docs/version-2.16/reference/subsystems/autoflake.mdx b/versioned_docs/version-2.16/reference/subsystems/autoflake.mdx index 6b06402ef..7265279be 100644 --- a/versioned_docs/version-2.16/reference/subsystems/autoflake.mdx +++ b/versioned_docs/version-2.16/reference/subsystems/autoflake.mdx @@ -25,7 +25,7 @@ Config section: `[autoflake]` default_repr={`False`} > -If true, don't use Autoflake when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use Autoflake when running `pants fmt` and `pants lint`. @@ -163,7 +163,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=autoflake`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=autoflake`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. @@ -179,7 +179,7 @@ Alternatively, you can set this option to the path to a custom lockfile using pi removal_hint={'Use the export goal\'s --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.'} > -If true, export a virtual environment with Autoflake when running `scie-pants-linux-x86_64 export`. +If true, export a virtual environment with Autoflake when running `pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. diff --git a/versioned_docs/version-2.16/reference/subsystems/bandit.mdx b/versioned_docs/version-2.16/reference/subsystems/bandit.mdx index 5237e3112..b923d1e5f 100644 --- a/versioned_docs/version-2.16/reference/subsystems/bandit.mdx +++ b/versioned_docs/version-2.16/reference/subsystems/bandit.mdx @@ -25,7 +25,7 @@ Config section: `[bandit]` default_repr={`False`} > -If true, don't use Bandit when running `scie-pants-linux-x86_64 lint`. +If true, don't use Bandit when running `pants lint`. @@ -163,7 +163,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=bandit`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=bandit`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. @@ -179,7 +179,7 @@ Alternatively, you can set this option to the path to a custom lockfile using pi removal_hint={'Use the export goal\'s --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.'} > -If true, export a virtual environment with Bandit when running `scie-pants-linux-x86_64 export`. +If true, export a virtual environment with Bandit when running `pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. diff --git a/versioned_docs/version-2.16/reference/subsystems/black.mdx b/versioned_docs/version-2.16/reference/subsystems/black.mdx index ca1f67aba..00bd7d929 100644 --- a/versioned_docs/version-2.16/reference/subsystems/black.mdx +++ b/versioned_docs/version-2.16/reference/subsystems/black.mdx @@ -25,7 +25,7 @@ Config section: `[black]` default_repr={`False`} > -If true, don't use Black when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use Black when running `pants fmt` and `pants lint`. @@ -191,7 +191,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=black`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=black`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. @@ -207,7 +207,7 @@ Alternatively, you can set this option to the path to a custom lockfile using pi removal_hint={'Use the export goal\'s --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.'} > -If true, export a virtual environment with Black when running `scie-pants-linux-x86_64 export`. +If true, export a virtual environment with Black when running `pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. diff --git a/versioned_docs/version-2.16/reference/subsystems/buf.mdx b/versioned_docs/version-2.16/reference/subsystems/buf.mdx index 189a20a5e..a653e48fc 100644 --- a/versioned_docs/version-2.16/reference/subsystems/buf.mdx +++ b/versioned_docs/version-2.16/reference/subsystems/buf.mdx @@ -25,7 +25,7 @@ Config section: `[buf]` default_repr={`False`} > -If true, don't use Buf when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use Buf when running `pants fmt` and `pants lint`. @@ -37,7 +37,7 @@ If true, don't use Buf when running `scie-pants-linux-x86_64 fmt` and `scie default_repr={`False`} > -If true, don't use Buf when running `scie-pants-linux-x86_64 lint`. +If true, don't use Buf when running `pants lint`. diff --git a/versioned_docs/version-2.16/reference/subsystems/build-deprecations-fixer.mdx b/versioned_docs/version-2.16/reference/subsystems/build-deprecations-fixer.mdx index b3a4e372b..8fa169ffe 100644 --- a/versioned_docs/version-2.16/reference/subsystems/build-deprecations-fixer.mdx +++ b/versioned_docs/version-2.16/reference/subsystems/build-deprecations-fixer.mdx @@ -27,7 +27,7 @@ Config section: `[build-deprecations-fixer]` -If true, don't use BUILD Deprecations Fixer when running `scie-pants-linux-x86_64 fix`. +If true, don't use BUILD Deprecations Fixer when running `pants fix`. diff --git a/versioned_docs/version-2.16/reference/subsystems/buildifier.mdx b/versioned_docs/version-2.16/reference/subsystems/buildifier.mdx index 7979d4f23..2b32d5d0a 100644 --- a/versioned_docs/version-2.16/reference/subsystems/buildifier.mdx +++ b/versioned_docs/version-2.16/reference/subsystems/buildifier.mdx @@ -32,7 +32,7 @@ Config section: `[buildifier]` default_repr={`False`} > -If true, don't use Buildifier when running `scie-pants-linux-x86_64 fmt`. +If true, don't use Buildifier when running `pants fmt`. diff --git a/versioned_docs/version-2.16/reference/subsystems/cli.mdx b/versioned_docs/version-2.16/reference/subsystems/cli.mdx index c73472624..e471cf70f 100644 --- a/versioned_docs/version-2.16/reference/subsystems/cli.mdx +++ b/versioned_docs/version-2.16/reference/subsystems/cli.mdx @@ -35,7 +35,7 @@ green = "fmt lint check" all-changed = "--changed-since=HEAD --changed-dependents=transitive" ``` -This would allow you to run `scie-pants-linux-x86_64 green all-changed`, which is shorthand for `scie-pants-linux-x86_64 fmt lint check --changed-since=HEAD --changed-dependents=transitive`. +This would allow you to run `pants green all-changed`, which is shorthand for `pants fmt lint check --changed-since=HEAD --changed-dependents=transitive`. Notice: this option must be placed in a config file (e.g. `pants.toml` or `pantsrc`) to have any effect. diff --git a/versioned_docs/version-2.16/reference/subsystems/coverage-py.mdx b/versioned_docs/version-2.16/reference/subsystems/coverage-py.mdx index 1782ff69c..f161a39d1 100644 --- a/versioned_docs/version-2.16/reference/subsystems/coverage-py.mdx +++ b/versioned_docs/version-2.16/reference/subsystems/coverage-py.mdx @@ -240,7 +240,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=coverage-py`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=coverage-py`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.16/reference/subsystems/debugpy.mdx b/versioned_docs/version-2.16/reference/subsystems/debugpy.mdx index 572d62796..c66f7971e 100644 --- a/versioned_docs/version-2.16/reference/subsystems/debugpy.mdx +++ b/versioned_docs/version-2.16/reference/subsystems/debugpy.mdx @@ -151,7 +151,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=debugpy`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=debugpy`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.16/reference/subsystems/docformatter.mdx b/versioned_docs/version-2.16/reference/subsystems/docformatter.mdx index 1dd3784c8..c7cda4494 100644 --- a/versioned_docs/version-2.16/reference/subsystems/docformatter.mdx +++ b/versioned_docs/version-2.16/reference/subsystems/docformatter.mdx @@ -25,7 +25,7 @@ Config section: `[docformatter]` default_repr={`False`} > -If true, don't use docformatter when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use docformatter when running `pants fmt` and `pants lint`. @@ -163,7 +163,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=docformatter`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=docformatter`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. @@ -179,7 +179,7 @@ Alternatively, you can set this option to the path to a custom lockfile using pi removal_hint={'Use the export goal\'s --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.'} > -If true, export a virtual environment with docformatter when running `scie-pants-linux-x86_64 export`. +If true, export a virtual environment with docformatter when running `pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. diff --git a/versioned_docs/version-2.16/reference/subsystems/docker.mdx b/versioned_docs/version-2.16/reference/subsystems/docker.mdx index 08df2a996..f88f0cb6e 100644 --- a/versioned_docs/version-2.16/reference/subsystems/docker.mdx +++ b/versioned_docs/version-2.16/reference/subsystems/docker.mdx @@ -169,7 +169,7 @@ Additional arguments to use for `docker run` invocations. Example: ``` -$ scie-pants-linux-x86_64 run --docker-run-args="-p 127.0.0.1:80:8080/tcp --name demo" src/example:image -- [image entrypoint args] +$ pants run --docker-run-args="-p 127.0.0.1:80:8080/tcp --name demo" src/example:image -- [image entrypoint args] ``` To provide the top-level options to the `docker` client, use `[docker].env_vars` to configure the [Environment variables](https://docs.docker.com/engine/reference/commandline/cli/#environment-variables) as appropriate. diff --git a/versioned_docs/version-2.16/reference/subsystems/dockerfile-parser.mdx b/versioned_docs/version-2.16/reference/subsystems/dockerfile-parser.mdx index e96592b44..6f159bb42 100644 --- a/versioned_docs/version-2.16/reference/subsystems/dockerfile-parser.mdx +++ b/versioned_docs/version-2.16/reference/subsystems/dockerfile-parser.mdx @@ -117,7 +117,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=dockerfile-parser`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=dockerfile-parser`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.16/reference/subsystems/flake8.mdx b/versioned_docs/version-2.16/reference/subsystems/flake8.mdx index d8338093f..e9b17d469 100644 --- a/versioned_docs/version-2.16/reference/subsystems/flake8.mdx +++ b/versioned_docs/version-2.16/reference/subsystems/flake8.mdx @@ -25,7 +25,7 @@ Config section: `[flake8]` default_repr={`False`} > -If true, don't use Flake8 when running `scie-pants-linux-x86_64 lint`. +If true, don't use Flake8 when running `pants lint`. @@ -222,7 +222,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=flake8`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=flake8`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. @@ -238,7 +238,7 @@ Alternatively, you can set this option to the path to a custom lockfile using pi removal_hint={'Use the export goal\'s --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.'} > -If true, export a virtual environment with Flake8 when running `scie-pants-linux-x86_64 export`. +If true, export a virtual environment with Flake8 when running `pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. diff --git a/versioned_docs/version-2.16/reference/subsystems/go-test.mdx b/versioned_docs/version-2.16/reference/subsystems/go-test.mdx index ed16475ac..feb2073e9 100644 --- a/versioned_docs/version-2.16/reference/subsystems/go-test.mdx +++ b/versioned_docs/version-2.16/reference/subsystems/go-test.mdx @@ -90,7 +90,7 @@ This option is similar to the `go test -coverpkg` option, but without support cu default_repr={`False`} > -If true, don't use Go test binary when running `scie-pants-linux-x86_64 test`. +If true, don't use Go test binary when running `pants test`. diff --git a/versioned_docs/version-2.16/reference/subsystems/gofmt.mdx b/versioned_docs/version-2.16/reference/subsystems/gofmt.mdx index 0e737213e..b4fad02eb 100644 --- a/versioned_docs/version-2.16/reference/subsystems/gofmt.mdx +++ b/versioned_docs/version-2.16/reference/subsystems/gofmt.mdx @@ -25,7 +25,7 @@ Config section: `[gofmt]` default_repr={`False`} > -If true, don't use gofmt when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use gofmt when running `pants fmt` and `pants lint`. diff --git a/versioned_docs/version-2.16/reference/subsystems/google-java-format.mdx b/versioned_docs/version-2.16/reference/subsystems/google-java-format.mdx index ced5484aa..ed19c6180 100644 --- a/versioned_docs/version-2.16/reference/subsystems/google-java-format.mdx +++ b/versioned_docs/version-2.16/reference/subsystems/google-java-format.mdx @@ -25,7 +25,7 @@ Config section: `[google-java-format]` default_repr={`False`} > -If true, don't use Google Java Format when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use Google Java Format when running `pants fmt` and `pants lint`. @@ -79,7 +79,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/java/lint/google_java_format/google_java_format.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=google-java-format`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=google-java-format`. diff --git a/versioned_docs/version-2.16/reference/subsystems/hadolint.mdx b/versioned_docs/version-2.16/reference/subsystems/hadolint.mdx index f65b1de32..f832d9bcf 100644 --- a/versioned_docs/version-2.16/reference/subsystems/hadolint.mdx +++ b/versioned_docs/version-2.16/reference/subsystems/hadolint.mdx @@ -25,7 +25,7 @@ Config section: `[hadolint]` default_repr={`False`} > -If true, don't use Hadolint when running `scie-pants-linux-x86_64 lint`. +If true, don't use Hadolint when running `pants lint`. diff --git a/versioned_docs/version-2.16/reference/subsystems/helm-k8s-parser.mdx b/versioned_docs/version-2.16/reference/subsystems/helm-k8s-parser.mdx index d691f262a..17edee685 100644 --- a/versioned_docs/version-2.16/reference/subsystems/helm-k8s-parser.mdx +++ b/versioned_docs/version-2.16/reference/subsystems/helm-k8s-parser.mdx @@ -117,7 +117,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=helm-k8s-parser`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=helm-k8s-parser`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.16/reference/subsystems/helm-post-renderer.mdx b/versioned_docs/version-2.16/reference/subsystems/helm-post-renderer.mdx index 6fdcd52de..6fd06af6b 100644 --- a/versioned_docs/version-2.16/reference/subsystems/helm-post-renderer.mdx +++ b/versioned_docs/version-2.16/reference/subsystems/helm-post-renderer.mdx @@ -117,7 +117,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=helm-post-renderer`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=helm-post-renderer`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.16/reference/subsystems/helm-unittest.mdx b/versioned_docs/version-2.16/reference/subsystems/helm-unittest.mdx index c40e50deb..3f66e1cce 100644 --- a/versioned_docs/version-2.16/reference/subsystems/helm-unittest.mdx +++ b/versioned_docs/version-2.16/reference/subsystems/helm-unittest.mdx @@ -50,7 +50,7 @@ Output type used for the test report. default_repr={`False`} > -If true, don't use helmunittestsubsystem when running `scie-pants-linux-x86_64 test`. +If true, don't use helmunittestsubsystem when running `pants test`. diff --git a/versioned_docs/version-2.16/reference/subsystems/ipython.mdx b/versioned_docs/version-2.16/reference/subsystems/ipython.mdx index 95eb02d72..54a9aa87e 100644 --- a/versioned_docs/version-2.16/reference/subsystems/ipython.mdx +++ b/versioned_docs/version-2.16/reference/subsystems/ipython.mdx @@ -145,7 +145,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=ipython`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=ipython`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.16/reference/subsystems/isort.mdx b/versioned_docs/version-2.16/reference/subsystems/isort.mdx index 24901e253..fee2e289f 100644 --- a/versioned_docs/version-2.16/reference/subsystems/isort.mdx +++ b/versioned_docs/version-2.16/reference/subsystems/isort.mdx @@ -25,7 +25,7 @@ Config section: `[isort]` default_repr={`False`} > -If true, don't use isort when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use isort when running `pants fmt` and `pants lint`. @@ -193,7 +193,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=isort`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=isort`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. @@ -209,7 +209,7 @@ Alternatively, you can set this option to the path to a custom lockfile using pi removal_hint={'Use the export goal\'s --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.'} > -If true, export a virtual environment with isort when running `scie-pants-linux-x86_64 export`. +If true, export a virtual environment with isort when running `pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. diff --git a/versioned_docs/version-2.16/reference/subsystems/jarjar.mdx b/versioned_docs/version-2.16/reference/subsystems/jarjar.mdx index c408f56e9..1fdd841e6 100644 --- a/versioned_docs/version-2.16/reference/subsystems/jarjar.mdx +++ b/versioned_docs/version-2.16/reference/subsystems/jarjar.mdx @@ -80,7 +80,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/jvm/shading/jarjar.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=jarjar`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=jarjar`. diff --git a/versioned_docs/version-2.16/reference/subsystems/junit.mdx b/versioned_docs/version-2.16/reference/subsystems/junit.mdx index 7e0f88d18..0d0b118ae 100644 --- a/versioned_docs/version-2.16/reference/subsystems/junit.mdx +++ b/versioned_docs/version-2.16/reference/subsystems/junit.mdx @@ -37,7 +37,7 @@ Arguments to pass directly to JUnit, e.g. `--junit-args='--disable-ansi-colors'` default_repr={`False`} > -If true, don't use JUnit when running `scie-pants-linux-x86_64 test`. +If true, don't use JUnit when running `pants test`. @@ -79,7 +79,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/jvm/test/junit.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=junit`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=junit`. diff --git a/versioned_docs/version-2.16/reference/subsystems/ktlint.mdx b/versioned_docs/version-2.16/reference/subsystems/ktlint.mdx index 50f109e22..20464806d 100644 --- a/versioned_docs/version-2.16/reference/subsystems/ktlint.mdx +++ b/versioned_docs/version-2.16/reference/subsystems/ktlint.mdx @@ -25,7 +25,7 @@ Config section: `[ktlint]` default_repr={`False`} > -If true, don't use Ktlint when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use Ktlint when running `pants fmt` and `pants lint`. @@ -67,7 +67,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/kotlin/lint/ktlint/ktlint.lock for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=ktlint`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=ktlint`. diff --git a/versioned_docs/version-2.16/reference/subsystems/lambdex.mdx b/versioned_docs/version-2.16/reference/subsystems/lambdex.mdx index e35e5c0b5..29e8d05eb 100644 --- a/versioned_docs/version-2.16/reference/subsystems/lambdex.mdx +++ b/versioned_docs/version-2.16/reference/subsystems/lambdex.mdx @@ -141,7 +141,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=lambdex`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=lambdex`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.16/reference/subsystems/mypy-protobuf.mdx b/versioned_docs/version-2.16/reference/subsystems/mypy-protobuf.mdx index 38928e87c..c38206c8f 100644 --- a/versioned_docs/version-2.16/reference/subsystems/mypy-protobuf.mdx +++ b/versioned_docs/version-2.16/reference/subsystems/mypy-protobuf.mdx @@ -117,7 +117,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=mypy-protobuf`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=mypy-protobuf`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.16/reference/subsystems/mypy.mdx b/versioned_docs/version-2.16/reference/subsystems/mypy.mdx index 7a572c3dc..862b16f6a 100644 --- a/versioned_docs/version-2.16/reference/subsystems/mypy.mdx +++ b/versioned_docs/version-2.16/reference/subsystems/mypy.mdx @@ -25,7 +25,7 @@ Config section: `[mypy]` default_repr={`False`} > -If true, don't use MyPy when running `scie-pants-linux-x86_64 check`. +If true, don't use MyPy when running `pants check`. @@ -207,7 +207,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=mypy`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=mypy`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. @@ -223,7 +223,7 @@ Alternatively, you can set this option to the path to a custom lockfile using pi removal_hint={'Use the export goal\'s --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.'} > -If true, export a virtual environment with MyPy when running `scie-pants-linux-x86_64 export`. +If true, export a virtual environment with MyPy when running `pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. @@ -265,7 +265,7 @@ Path to a lockfile for the option `[mypy].extra_type_stubs`. Set to the string `` to opt out of using a lockfile. We do not recommend this if you use `[mypy].extra_type_stubs`, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=mypy-extra-type-stubs`. +To use a lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=mypy-extra-type-stubs`. diff --git a/versioned_docs/version-2.16/reference/subsystems/preamble.mdx b/versioned_docs/version-2.16/reference/subsystems/preamble.mdx index 8a4007fbf..2a12e42f3 100644 --- a/versioned_docs/version-2.16/reference/subsystems/preamble.mdx +++ b/versioned_docs/version-2.16/reference/subsystems/preamble.mdx @@ -29,7 +29,7 @@ Config section: `[preamble]` default_repr={`False`} > -If true, don't use preamble when running `scie-pants-linux-x86_64 fmt`. +If true, don't use preamble when running `pants fmt`. diff --git a/versioned_docs/version-2.16/reference/subsystems/protobuf-java-grpc.mdx b/versioned_docs/version-2.16/reference/subsystems/protobuf-java-grpc.mdx index a30827732..e3e256f5e 100644 --- a/versioned_docs/version-2.16/reference/subsystems/protobuf-java-grpc.mdx +++ b/versioned_docs/version-2.16/reference/subsystems/protobuf-java-grpc.mdx @@ -57,7 +57,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/codegen/protobuf/java/grpc-java.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=protobuf-java-grpc`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=protobuf-java-grpc`. diff --git a/versioned_docs/version-2.16/reference/subsystems/pydocstyle.mdx b/versioned_docs/version-2.16/reference/subsystems/pydocstyle.mdx index 7979a6c73..e3b935f0f 100644 --- a/versioned_docs/version-2.16/reference/subsystems/pydocstyle.mdx +++ b/versioned_docs/version-2.16/reference/subsystems/pydocstyle.mdx @@ -25,7 +25,7 @@ Config section: `[pydocstyle]` default_repr={`False`} > -If true, don't use Pydocstyle when running `scie-pants-linux-x86_64 lint`. +If true, don't use Pydocstyle when running `pants lint`. @@ -191,7 +191,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=pydocstyle`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=pydocstyle`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. @@ -207,7 +207,7 @@ Alternatively, you can set this option to the path to a custom lockfile using pi removal_hint={'Use the export goal\'s --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.'} > -If true, export a virtual environment with Pydocstyle when running `scie-pants-linux-x86_64 export`. +If true, export a virtual environment with Pydocstyle when running `pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. diff --git a/versioned_docs/version-2.16/reference/subsystems/pylint.mdx b/versioned_docs/version-2.16/reference/subsystems/pylint.mdx index b5308c254..fb5c8b73f 100644 --- a/versioned_docs/version-2.16/reference/subsystems/pylint.mdx +++ b/versioned_docs/version-2.16/reference/subsystems/pylint.mdx @@ -25,7 +25,7 @@ Config section: `[pylint]` default_repr={`False`} > -If true, don't use Pylint when running `scie-pants-linux-x86_64 lint`. +If true, don't use Pylint when running `pants lint`. @@ -201,7 +201,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=pylint`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=pylint`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. @@ -217,7 +217,7 @@ Alternatively, you can set this option to the path to a custom lockfile using pi removal_hint={'Use the export goal\'s --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.'} > -If true, export a virtual environment with Pylint when running `scie-pants-linux-x86_64 export`. +If true, export a virtual environment with Pylint when running `pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. diff --git a/versioned_docs/version-2.16/reference/subsystems/pyoxidizer.mdx b/versioned_docs/version-2.16/reference/subsystems/pyoxidizer.mdx index 1038d1b82..2a9b91e71 100644 --- a/versioned_docs/version-2.16/reference/subsystems/pyoxidizer.mdx +++ b/versioned_docs/version-2.16/reference/subsystems/pyoxidizer.mdx @@ -153,7 +153,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=pyoxidizer`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=pyoxidizer`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.16/reference/subsystems/pytest.mdx b/versioned_docs/version-2.16/reference/subsystems/pytest.mdx index 10919d68a..1c68b4c93 100644 --- a/versioned_docs/version-2.16/reference/subsystems/pytest.mdx +++ b/versioned_docs/version-2.16/reference/subsystems/pytest.mdx @@ -51,7 +51,7 @@ NOTE: Enabling `pytest-xdist` can cause high-level scoped fixtures (for example default_repr={`False`} > -If true, don't use Pytest when running `scie-pants-linux-x86_64 test`. +If true, don't use Pytest when running `pants test`. @@ -215,7 +215,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=pytest`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=pytest`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. @@ -231,7 +231,7 @@ Alternatively, you can set this option to the path to a custom lockfile using pi removal_hint={'Use the export goal\'s --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.'} > -If true, export a virtual environment with Pytest when running `scie-pants-linux-x86_64 export`. +If true, export a virtual environment with Pytest when running `pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. diff --git a/versioned_docs/version-2.16/reference/subsystems/python-infer.mdx b/versioned_docs/version-2.16/reference/subsystems/python-infer.mdx index d838d7281..b58e7c79b 100644 --- a/versioned_docs/version-2.16/reference/subsystems/python-infer.mdx +++ b/versioned_docs/version-2.16/reference/subsystems/python-infer.mdx @@ -94,7 +94,7 @@ If --assets is True, treat valid-looking strings with at least this many forward Infer a target's dependencies on any `__init__.py` files in the packages it is located in (recursively upward in the directory structure). -Even if this is set to `never` or `content_only`, Pants will still always include any ancestor `__init__.py` files in the sandbox. Only, they will not be "proper" dependencies, e.g. they will not show up in `scie-pants-linux-x86_64 dependencies` and their own dependencies will not be used. +Even if this is set to `never` or `content_only`, Pants will still always include any ancestor `__init__.py` files in the sandbox. Only, they will not be "proper" dependencies, e.g. they will not show up in `pants dependencies` and their own dependencies will not be used. By default, Pants only adds a "proper" dependency if there is content in the `__init__.py` file. This makes sure that dependencies are added when likely necessary to build, while also avoiding adding unnecessary dependencies. While accurate, those unnecessary dependencies can complicate setting metadata like the `interpreter_constraints` and `resolve` fields. diff --git a/versioned_docs/version-2.16/reference/subsystems/python.mdx b/versioned_docs/version-2.16/reference/subsystems/python.mdx index 2630c3c67..6bf37ea8d 100644 --- a/versioned_docs/version-2.16/reference/subsystems/python.mdx +++ b/versioned_docs/version-2.16/reference/subsystems/python.mdx @@ -107,14 +107,14 @@ A mapping of logical names to lockfile paths used in your project. Many organizations only need a single resolve for their whole project, which is a good default and often the simplest thing to do. However, you may need multiple resolves, such as if you use two conflicting versions of a requirement in your repository. -If you only need a single resolve, run `scie-pants-linux-x86_64 generate-lockfiles` to generate the lockfile. +If you only need a single resolve, run `pants generate-lockfiles` to generate the lockfile. If you need multiple resolves: 1. Via this option, define multiple resolve names and their lockfile paths. The names should be meaningful to your repository, such as `data-science` or `pants-plugins`. 2. Set the default with `[python].default_resolve`. 3. Update your `python_requirement` targets with the `resolve` field to declare which resolve they should be available in. They default to `[python].default_resolve`, so you only need to update targets that you want in non-default resolves. (Often you'll set this via the `python_requirements` or `poetry_requirements` target generators) -4. Run `scie-pants-linux-x86_64 generate-lockfiles` to generate the lockfiles. If the results aren't what you'd expect, adjust the prior step. +4. Run `pants generate-lockfiles` to generate the lockfiles. If the results aren't what you'd expect, adjust the prior step. 5. Update any targets like `python_source` / `python_sources`, `python_test` / `python_tests`, and `pex_binary` which need to set a non-default resolve with the `resolve` field. If a target can work with multiple resolves, you can either use the `parametrize` mechanism or manually create a distinct target per resolve. See https://www.pantsbuild.org/v2.16/docs/targets for information about `parametrize`. @@ -414,7 +414,7 @@ If another targets address is in conflict with the created lockfile target, it w env_repr='PANTS_PYTHON_REQUIREMENT_CONSTRAINTS' default_repr={`None`} removal_version='3.0.0.dev0' - removal_hint={'We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.

To migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `scie-pants-linux-x86_64 generate-lockfiles`.'} + removal_hint={'We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.

To migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `pants generate-lockfiles`.'} > When resolving third-party requirements for your own code (vs. tools you run), use this constraints file to determine which versions to use. @@ -434,7 +434,7 @@ This only applies when resolving user requirements, rather than tools you run li env_repr='PANTS_PYTHON_RESOLVE_ALL_CONSTRAINTS' default_repr={`True`} removal_version='3.0.0.dev0' - removal_hint={'We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.

To migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `scie-pants-linux-x86_64 generate-lockfiles`.'} + removal_hint={'We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.

To migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `pants generate-lockfiles`.'} > (Only relevant when using `[python].requirement_constraints.`) If enabled, when resolving requirements, Pants will first resolve your entire constraints file as a single global resolve. Then, if the code uses a subset of your constraints file, Pants will extract the relevant requirements from that global resolve so that only what's actually needed gets used. If disabled, Pants will not use a global resolve and will resolve each subset of your requirements independently. diff --git a/versioned_docs/version-2.16/reference/subsystems/pyupgrade.mdx b/versioned_docs/version-2.16/reference/subsystems/pyupgrade.mdx index 7b97fce28..4e67157eb 100644 --- a/versioned_docs/version-2.16/reference/subsystems/pyupgrade.mdx +++ b/versioned_docs/version-2.16/reference/subsystems/pyupgrade.mdx @@ -25,7 +25,7 @@ Config section: `[pyupgrade]` default_repr={`False`} > -If true, don't use pyupgrade when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use pyupgrade when running `pants fmt` and `pants lint`. @@ -163,7 +163,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=pyupgrade`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=pyupgrade`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. @@ -179,7 +179,7 @@ Alternatively, you can set this option to the path to a custom lockfile using pi removal_hint={'Use the export goal\'s --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.'} > -If true, export a virtual environment with pyupgrade when running `scie-pants-linux-x86_64 export`. +If true, export a virtual environment with pyupgrade when running `pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. diff --git a/versioned_docs/version-2.16/reference/subsystems/regex-lint.mdx b/versioned_docs/version-2.16/reference/subsystems/regex-lint.mdx index a919e6ff4..20d8d1542 100644 --- a/versioned_docs/version-2.16/reference/subsystems/regex-lint.mdx +++ b/versioned_docs/version-2.16/reference/subsystems/regex-lint.mdx @@ -29,7 +29,7 @@ Config section: `[regex-lint]` default_repr={`False`} > -If true, don't use regex-lint when running `scie-pants-linux-x86_64 lint`. +If true, don't use regex-lint when running `pants lint`. diff --git a/versioned_docs/version-2.16/reference/subsystems/ruff.mdx b/versioned_docs/version-2.16/reference/subsystems/ruff.mdx index b7ebba6b0..b7480954b 100644 --- a/versioned_docs/version-2.16/reference/subsystems/ruff.mdx +++ b/versioned_docs/version-2.16/reference/subsystems/ruff.mdx @@ -25,7 +25,7 @@ Config section: `[ruff]` default_repr={`False`} > -If true, don't use Ruff when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use Ruff when running `pants fmt` and `pants lint`. @@ -191,7 +191,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=ruff`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=ruff`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. @@ -207,7 +207,7 @@ Alternatively, you can set this option to the path to a custom lockfile using pi removal_hint={'Use the export goal\'s --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.'} > -If true, export a virtual environment with Ruff when running `scie-pants-linux-x86_64 export`. +If true, export a virtual environment with Ruff when running `pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. diff --git a/versioned_docs/version-2.16/reference/subsystems/scalafmt.mdx b/versioned_docs/version-2.16/reference/subsystems/scalafmt.mdx index a82dd0747..9470110b2 100644 --- a/versioned_docs/version-2.16/reference/subsystems/scalafmt.mdx +++ b/versioned_docs/version-2.16/reference/subsystems/scalafmt.mdx @@ -25,7 +25,7 @@ Config section: `[scalafmt]` default_repr={`False`} > -If true, don't use scalafmt when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use scalafmt when running `pants fmt` and `pants lint`. @@ -67,7 +67,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/scala/lint/scalafmt/scalafmt.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalafmt`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=scalafmt`. diff --git a/versioned_docs/version-2.16/reference/subsystems/scalapb.mdx b/versioned_docs/version-2.16/reference/subsystems/scalapb.mdx index 47f3877b7..7e5d3ce87 100644 --- a/versioned_docs/version-2.16/reference/subsystems/scalapb.mdx +++ b/versioned_docs/version-2.16/reference/subsystems/scalapb.mdx @@ -69,7 +69,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/codegen/protobuf/scala/scalapbc.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalapb`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=scalapb`. diff --git a/versioned_docs/version-2.16/reference/subsystems/scalatest.mdx b/versioned_docs/version-2.16/reference/subsystems/scalatest.mdx index 5e64faa77..f2cd762f4 100644 --- a/versioned_docs/version-2.16/reference/subsystems/scalatest.mdx +++ b/versioned_docs/version-2.16/reference/subsystems/scalatest.mdx @@ -39,7 +39,7 @@ See https://www.scalatest.org/user_guide/using_the_runner for supported argument default_repr={`False`} > -If true, don't use Scalatest when running `scie-pants-linux-x86_64 test`. +If true, don't use Scalatest when running `pants test`. @@ -81,7 +81,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.16.1rc4/src/python/pants/backend/scala/subsystems/scalatest.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalatest`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=scalatest`. diff --git a/versioned_docs/version-2.16/reference/subsystems/setuptools-scm.mdx b/versioned_docs/version-2.16/reference/subsystems/setuptools-scm.mdx index df0293513..8986dd7c8 100644 --- a/versioned_docs/version-2.16/reference/subsystems/setuptools-scm.mdx +++ b/versioned_docs/version-2.16/reference/subsystems/setuptools-scm.mdx @@ -141,7 +141,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=setuptools-scm`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=setuptools-scm`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.16/reference/subsystems/setuptools.mdx b/versioned_docs/version-2.16/reference/subsystems/setuptools.mdx index 21fcac435..055542f21 100644 --- a/versioned_docs/version-2.16/reference/subsystems/setuptools.mdx +++ b/versioned_docs/version-2.16/reference/subsystems/setuptools.mdx @@ -105,7 +105,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=setuptools`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=setuptools`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.16/reference/subsystems/shell-test.mdx b/versioned_docs/version-2.16/reference/subsystems/shell-test.mdx index 3c748d702..1a371c907 100644 --- a/versioned_docs/version-2.16/reference/subsystems/shell-test.mdx +++ b/versioned_docs/version-2.16/reference/subsystems/shell-test.mdx @@ -25,7 +25,7 @@ Config section: `[shell-test]` default_repr={`False`} > -If true, don't use Test with shell scripts when running `scie-pants-linux-x86_64 test`. +If true, don't use Test with shell scripts when running `pants test`. diff --git a/versioned_docs/version-2.16/reference/subsystems/shellcheck.mdx b/versioned_docs/version-2.16/reference/subsystems/shellcheck.mdx index d703206d3..5f8ff9112 100644 --- a/versioned_docs/version-2.16/reference/subsystems/shellcheck.mdx +++ b/versioned_docs/version-2.16/reference/subsystems/shellcheck.mdx @@ -25,7 +25,7 @@ Config section: `[shellcheck]` default_repr={`False`} > -If true, don't use Shellcheck when running `scie-pants-linux-x86_64 lint`. +If true, don't use Shellcheck when running `pants lint`. diff --git a/versioned_docs/version-2.16/reference/subsystems/shfmt.mdx b/versioned_docs/version-2.16/reference/subsystems/shfmt.mdx index effe7ffa0..63371816d 100644 --- a/versioned_docs/version-2.16/reference/subsystems/shfmt.mdx +++ b/versioned_docs/version-2.16/reference/subsystems/shfmt.mdx @@ -25,7 +25,7 @@ Config section: `[shfmt]` default_repr={`False`} > -If true, don't use shfmt when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use shfmt when running `pants fmt` and `pants lint`. diff --git a/versioned_docs/version-2.16/reference/subsystems/shunit2.mdx b/versioned_docs/version-2.16/reference/subsystems/shunit2.mdx index 02c18982b..2d0c5a3f8 100644 --- a/versioned_docs/version-2.16/reference/subsystems/shunit2.mdx +++ b/versioned_docs/version-2.16/reference/subsystems/shunit2.mdx @@ -25,7 +25,7 @@ Config section: `[shunit2]` default_repr={`False`} > -If true, don't use shunit2 when running `scie-pants-linux-x86_64 test`. +If true, don't use shunit2 when running `pants test`. diff --git a/versioned_docs/version-2.16/reference/subsystems/spectral.mdx b/versioned_docs/version-2.16/reference/subsystems/spectral.mdx index 61540d8b9..040a2646c 100644 --- a/versioned_docs/version-2.16/reference/subsystems/spectral.mdx +++ b/versioned_docs/version-2.16/reference/subsystems/spectral.mdx @@ -25,7 +25,7 @@ Config section: `[spectral]` default_repr={`False`} > -If true, don't use Spectral when running `scie-pants-linux-x86_64 lint`. +If true, don't use Spectral when running `pants lint`. diff --git a/versioned_docs/version-2.16/reference/subsystems/terraform-fmt.mdx b/versioned_docs/version-2.16/reference/subsystems/terraform-fmt.mdx index 968e542ad..c675ed16b 100644 --- a/versioned_docs/version-2.16/reference/subsystems/terraform-fmt.mdx +++ b/versioned_docs/version-2.16/reference/subsystems/terraform-fmt.mdx @@ -25,7 +25,7 @@ Config section: `[terraform-fmt]` default_repr={`False`} > -If true, don't use `terraform fmt` when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use `terraform fmt` when running `pants fmt` and `pants lint`. diff --git a/versioned_docs/version-2.16/reference/subsystems/terraform-hcl2-parser.mdx b/versioned_docs/version-2.16/reference/subsystems/terraform-hcl2-parser.mdx index 8753cb174..a1057ce37 100644 --- a/versioned_docs/version-2.16/reference/subsystems/terraform-hcl2-parser.mdx +++ b/versioned_docs/version-2.16/reference/subsystems/terraform-hcl2-parser.mdx @@ -117,7 +117,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=terraform-hcl2-parser`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=terraform-hcl2-parser`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.16/reference/subsystems/terraform-validate.mdx b/versioned_docs/version-2.16/reference/subsystems/terraform-validate.mdx index a84bf5b6c..e7686bc2f 100644 --- a/versioned_docs/version-2.16/reference/subsystems/terraform-validate.mdx +++ b/versioned_docs/version-2.16/reference/subsystems/terraform-validate.mdx @@ -25,7 +25,7 @@ Config section: `[terraform-validate]` default_repr={`False`} > -If true, don't use `terraform validate` when running `scie-pants-linux-x86_64 check`. +If true, don't use `terraform validate` when running `pants check`. diff --git a/versioned_docs/version-2.16/reference/subsystems/twine.mdx b/versioned_docs/version-2.16/reference/subsystems/twine.mdx index 8a4538679..283fb876b 100644 --- a/versioned_docs/version-2.16/reference/subsystems/twine.mdx +++ b/versioned_docs/version-2.16/reference/subsystems/twine.mdx @@ -25,7 +25,7 @@ Config section: `[twine]` default_repr={`False`} > -If true, don't use Twine when running `scie-pants-linux-x86_64 publish`. +If true, don't use Twine when running `pants publish`. @@ -209,7 +209,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=twine`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=twine`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.16/reference/subsystems/yamllint.mdx b/versioned_docs/version-2.16/reference/subsystems/yamllint.mdx index e759bceba..f3a84b2f2 100644 --- a/versioned_docs/version-2.16/reference/subsystems/yamllint.mdx +++ b/versioned_docs/version-2.16/reference/subsystems/yamllint.mdx @@ -61,7 +61,7 @@ Arguments to pass directly to Yamllint, e.g. `--yamllint-args='-d relaxed'`. default_repr={`False`} > -If true, don't use Yamllint when running `scie-pants-linux-x86_64 lint`. +If true, don't use Yamllint when running `pants lint`. @@ -199,7 +199,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=yamllint`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=yamllint`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. @@ -215,7 +215,7 @@ Alternatively, you can set this option to the path to a custom lockfile using pi removal_hint={'Use the export goal\'s --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.'} > -If true, export a virtual environment with Yamllint when running `scie-pants-linux-x86_64 export`. +If true, export a virtual environment with Yamllint when running `pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. diff --git a/versioned_docs/version-2.16/reference/subsystems/yapf.mdx b/versioned_docs/version-2.16/reference/subsystems/yapf.mdx index c44427be1..78d52cb18 100644 --- a/versioned_docs/version-2.16/reference/subsystems/yapf.mdx +++ b/versioned_docs/version-2.16/reference/subsystems/yapf.mdx @@ -25,7 +25,7 @@ Config section: `[yapf]` default_repr={`False`} > -If true, don't use yapf when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use yapf when running `pants fmt` and `pants lint`. @@ -193,7 +193,7 @@ Set to the string `` to use a lockfile provided by Pants, so long as yo Set to the string `` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=yapf`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=yapf`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. @@ -209,7 +209,7 @@ Alternatively, you can set this option to the path to a custom lockfile using pi removal_hint={'Use the export goal\'s --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.'} > -If true, export a virtual environment with yapf when running `scie-pants-linux-x86_64 export`. +If true, export a virtual environment with yapf when running `pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. diff --git a/versioned_docs/version-2.16/reference/targets/adhoc_tool.mdx b/versioned_docs/version-2.16/reference/targets/adhoc_tool.mdx index 669c54da7..6612a2f1b 100644 --- a/versioned_docs/version-2.16/reference/targets/adhoc_tool.mdx +++ b/versioned_docs/version-2.16/reference/targets/adhoc_tool.mdx @@ -38,7 +38,7 @@ Backend: `pants.backend.experimental.adhoc` @@ -51,7 +51,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.16/reference/targets/archive.mdx b/versioned_docs/version-2.16/reference/targets/archive.mdx index c0c9b9ef7..b3f69629d 100644 --- a/versioned_docs/version-2.16/reference/targets/archive.mdx +++ b/versioned_docs/version-2.16/reference/targets/archive.mdx @@ -24,7 +24,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -52,7 +52,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. @@ -65,11 +65,11 @@ Warning: setting this value risks naming collisions with other package targets y default_repr={`None`} > -Addresses to any targets that can be built with `scie-pants-linux-x86_64 package`, e.g. `["project:app"]`. +Addresses to any targets that can be built with `pants package`, e.g. `["project:app"]`. -Pants will build the assets as if you had run `scie-pants-linux-x86_64 package`. It will include the results in your archive using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). +Pants will build the assets as if you had run `pants package`. It will include the results in your archive using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). -You can include anything that can be built by `scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or even another `archive`. +You can include anything that can be built by `pants package`, e.g. a `pex_binary`, `python_awslambda`, or even another `archive`. diff --git a/versioned_docs/version-2.16/reference/targets/deploy_jar.mdx b/versioned_docs/version-2.16/reference/targets/deploy_jar.mdx index 1395a61b1..19a2f2cec 100644 --- a/versioned_docs/version-2.16/reference/targets/deploy_jar.mdx +++ b/versioned_docs/version-2.16/reference/targets/deploy_jar.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.experimental.java` @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -65,7 +65,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. @@ -80,9 +80,9 @@ Warning: setting this value risks naming collisions with other package targets y Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.16/reference/targets/docker_environment.mdx b/versioned_docs/version-2.16/reference/targets/docker_environment.mdx index 3547992a7..318a734bd 100644 --- a/versioned_docs/version-2.16/reference/targets/docker_environment.mdx +++ b/versioned_docs/version-2.16/reference/targets/docker_environment.mdx @@ -28,7 +28,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.16/reference/targets/docker_image.mdx b/versioned_docs/version-2.16/reference/targets/docker_image.mdx index a0fbb1281..a56c83397 100644 --- a/versioned_docs/version-2.16/reference/targets/docker_image.mdx +++ b/versioned_docs/version-2.16/reference/targets/docker_image.mdx @@ -39,7 +39,7 @@ Backend: `pants.backend.docker` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -52,7 +52,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -78,9 +78,9 @@ Use `[docker].build_args` to set default build args for all images. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -277,7 +277,7 @@ See [Docker documentation](https://docs.docker.com/develop/develop-images/build_ default_repr={`False`} > -If set to true, do not push this image to registries when running `scie-pants-linux-x86_64 publish`. +If set to true, do not push this image to registries when running `pants publish`. @@ -333,7 +333,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. diff --git a/versioned_docs/version-2.16/reference/targets/experimental_test_shell_command.mdx b/versioned_docs/version-2.16/reference/targets/experimental_test_shell_command.mdx index 9dcf147c5..358e443a9 100644 --- a/versioned_docs/version-2.16/reference/targets/experimental_test_shell_command.mdx +++ b/versioned_docs/version-2.16/reference/targets/experimental_test_shell_command.mdx @@ -39,7 +39,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -52,7 +52,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.16/reference/targets/experimental_wrap_as_go_package_sources.mdx b/versioned_docs/version-2.16/reference/targets/experimental_wrap_as_go_package_sources.mdx index 76db3f1ba..0630639a4 100644 --- a/versioned_docs/version-2.16/reference/targets/experimental_wrap_as_go_package_sources.mdx +++ b/versioned_docs/version-2.16/reference/targets/experimental_wrap_as_go_package_sources.mdx @@ -30,7 +30,7 @@ Backend: `pants.backend.experimental.go` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.16/reference/targets/experimental_wrap_as_java_sources.mdx b/versioned_docs/version-2.16/reference/targets/experimental_wrap_as_java_sources.mdx index 940029f9b..ff3e04681 100644 --- a/versioned_docs/version-2.16/reference/targets/experimental_wrap_as_java_sources.mdx +++ b/versioned_docs/version-2.16/reference/targets/experimental_wrap_as_java_sources.mdx @@ -30,7 +30,7 @@ Backend: `pants.backend.experimental.java` @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.16/reference/targets/experimental_wrap_as_kotlin_sources.mdx b/versioned_docs/version-2.16/reference/targets/experimental_wrap_as_kotlin_sources.mdx index 003b6ad9a..bae3428a7 100644 --- a/versioned_docs/version-2.16/reference/targets/experimental_wrap_as_kotlin_sources.mdx +++ b/versioned_docs/version-2.16/reference/targets/experimental_wrap_as_kotlin_sources.mdx @@ -30,7 +30,7 @@ Backend: `pants.backend.experimental.kotlin` @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.16/reference/targets/experimental_wrap_as_python_sources.mdx b/versioned_docs/version-2.16/reference/targets/experimental_wrap_as_python_sources.mdx index a341b498b..5751ec09f 100644 --- a/versioned_docs/version-2.16/reference/targets/experimental_wrap_as_python_sources.mdx +++ b/versioned_docs/version-2.16/reference/targets/experimental_wrap_as_python_sources.mdx @@ -30,7 +30,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.16/reference/targets/experimental_wrap_as_resources.mdx b/versioned_docs/version-2.16/reference/targets/experimental_wrap_as_resources.mdx index ae83538d0..e7518c7f5 100644 --- a/versioned_docs/version-2.16/reference/targets/experimental_wrap_as_resources.mdx +++ b/versioned_docs/version-2.16/reference/targets/experimental_wrap_as_resources.mdx @@ -30,7 +30,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.16/reference/targets/experimental_wrap_as_scala_sources.mdx b/versioned_docs/version-2.16/reference/targets/experimental_wrap_as_scala_sources.mdx index df94d3733..5548c481b 100644 --- a/versioned_docs/version-2.16/reference/targets/experimental_wrap_as_scala_sources.mdx +++ b/versioned_docs/version-2.16/reference/targets/experimental_wrap_as_scala_sources.mdx @@ -30,7 +30,7 @@ Backend: `pants.backend.experimental.scala` @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.16/reference/targets/file.mdx b/versioned_docs/version-2.16/reference/targets/file.mdx index b9336264f..6e2c22b82 100644 --- a/versioned_docs/version-2.16/reference/targets/file.mdx +++ b/versioned_docs/version-2.16/reference/targets/file.mdx @@ -26,7 +26,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -52,9 +52,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.16/reference/targets/files.mdx b/versioned_docs/version-2.16/reference/targets/files.mdx index 7a448aaa5..88be067b6 100644 --- a/versioned_docs/version-2.16/reference/targets/files.mdx +++ b/versioned_docs/version-2.16/reference/targets/files.mdx @@ -24,7 +24,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -91,9 +91,9 @@ You can specify the same file name in multiple keys, so long as you don't o Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.16/reference/targets/go_binary.mdx b/versioned_docs/version-2.16/reference/targets/go_binary.mdx index 55a27e2dd..e1a85a7a6 100644 --- a/versioned_docs/version-2.16/reference/targets/go_binary.mdx +++ b/versioned_docs/version-2.16/reference/targets/go_binary.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.go` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -52,7 +52,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. diff --git a/versioned_docs/version-2.16/reference/targets/go_mod.mdx b/versioned_docs/version-2.16/reference/targets/go_mod.mdx index ea3d4e8ad..a0cfd6173 100644 --- a/versioned_docs/version-2.16/reference/targets/go_mod.mdx +++ b/versioned_docs/version-2.16/reference/targets/go_mod.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.go` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.16/reference/targets/go_package.mdx b/versioned_docs/version-2.16/reference/targets/go_package.mdx index 5453e5e5f..61338159d 100644 --- a/versioned_docs/version-2.16/reference/targets/go_package.mdx +++ b/versioned_docs/version-2.16/reference/targets/go_package.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.experimental.go` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -52,9 +52,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.16/reference/targets/go_third_party_package.mdx b/versioned_docs/version-2.16/reference/targets/go_third_party_package.mdx index cdb0cc01e..baea6e11f 100644 --- a/versioned_docs/version-2.16/reference/targets/go_third_party_package.mdx +++ b/versioned_docs/version-2.16/reference/targets/go_third_party_package.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.go` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -54,9 +54,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.16/reference/targets/helm_artifact.mdx b/versioned_docs/version-2.16/reference/targets/helm_artifact.mdx index 0c94682be..df2c66974 100644 --- a/versioned_docs/version-2.16/reference/targets/helm_artifact.mdx +++ b/versioned_docs/version-2.16/reference/targets/helm_artifact.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.helm` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.16/reference/targets/helm_chart.mdx b/versioned_docs/version-2.16/reference/targets/helm_chart.mdx index 61cb8733e..fdce24bc6 100644 --- a/versioned_docs/version-2.16/reference/targets/helm_chart.mdx +++ b/versioned_docs/version-2.16/reference/targets/helm_chart.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.helm` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -76,9 +76,9 @@ Example: `sources=['values.yaml', 'templates/*.yaml', '!values_ignore.yaml']` Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -99,7 +99,7 @@ If undefined, this will use the path to the BUILD file, For example, `src/charts Regardless of whether you use the default or set this field, the path will end with Helms's file format of `-.tgz`, where `chart_name` and `chart_version` are the values extracted from the Chart.yaml file. So, using the default for this field, the target `src/charts/mychart:tgt_name` might have a final path like `src.charts.mychart/tgt_name/mychart-0.1.0.tgz`. -When running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. @@ -170,7 +170,7 @@ The above example shows two valid `registry` options: using an alias to a config default_repr={`False`} > -If set to true, do not push this Helm chart to registries when running `scie-pants-linux-x86_64 publish`. +If set to true, do not push this Helm chart to registries when running `pants publish`. @@ -181,7 +181,7 @@ If set to true, do not push this Helm chart to registries when running `scie-pan default_repr={`False`} > -If set to true, do not run any linting in this Helm chart when running `scie-pants-linux-x86_64 lint`. +If set to true, do not run any linting in this Helm chart when running `pants lint`. diff --git a/versioned_docs/version-2.16/reference/targets/helm_deployment.mdx b/versioned_docs/version-2.16/reference/targets/helm_deployment.mdx index 05191aa75..4878fb7f4 100644 --- a/versioned_docs/version-2.16/reference/targets/helm_deployment.mdx +++ b/versioned_docs/version-2.16/reference/targets/helm_deployment.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.helm` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -61,9 +61,9 @@ Name of the release used in the deployment. If not set, the target name will be Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.16/reference/targets/helm_unittest_test.mdx b/versioned_docs/version-2.16/reference/targets/helm_unittest_test.mdx index fdd5d7417..2b690bc71 100644 --- a/versioned_docs/version-2.16/reference/targets/helm_unittest_test.mdx +++ b/versioned_docs/version-2.16/reference/targets/helm_unittest_test.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.helm` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -63,9 +63,9 @@ Path is relative to the BUILD file's directory, e.g. `source='example.ext'` Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.16/reference/targets/helm_unittest_tests.mdx b/versioned_docs/version-2.16/reference/targets/helm_unittest_tests.mdx index 6fca1368e..8a05c6a3e 100644 --- a/versioned_docs/version-2.16/reference/targets/helm_unittest_tests.mdx +++ b/versioned_docs/version-2.16/reference/targets/helm_unittest_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.helm` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -65,9 +65,9 @@ Example: `sources=['*_test.yaml', '!ignore_test.yaml']` Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -109,9 +109,9 @@ You can specify the same file name in multiple keys, so long as you don't o Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.16/reference/targets/java_source.mdx b/versioned_docs/version-2.16/reference/targets/java_source.mdx index 81c273377..8fef2f796 100644 --- a/versioned_docs/version-2.16/reference/targets/java_source.mdx +++ b/versioned_docs/version-2.16/reference/targets/java_source.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.java` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.16/reference/targets/java_sources.mdx b/versioned_docs/version-2.16/reference/targets/java_sources.mdx index 5af6a4872..ccad52d04 100644 --- a/versioned_docs/version-2.16/reference/targets/java_sources.mdx +++ b/versioned_docs/version-2.16/reference/targets/java_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.java` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -77,9 +77,9 @@ If true, don't run Google Java Format on this target's code. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.16/reference/targets/junit_test.mdx b/versioned_docs/version-2.16/reference/targets/junit_test.mdx index 071b2d563..2e7edfbb6 100644 --- a/versioned_docs/version-2.16/reference/targets/junit_test.mdx +++ b/versioned_docs/version-2.16/reference/targets/junit_test.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.java` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -91,9 +91,9 @@ This will be merged with and override values from `[test].extra_env_vars`. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.16/reference/targets/junit_tests.mdx b/versioned_docs/version-2.16/reference/targets/junit_tests.mdx index 0a66b9eaf..cf0c36400 100644 --- a/versioned_docs/version-2.16/reference/targets/junit_tests.mdx +++ b/versioned_docs/version-2.16/reference/targets/junit_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.java` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -93,9 +93,9 @@ This will be merged with and override values from `[test].extra_env_vars`. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.16/reference/targets/jvm_artifact.mdx b/versioned_docs/version-2.16/reference/targets/jvm_artifact.mdx index 6748c5c85..7364dac42 100644 --- a/versioned_docs/version-2.16/reference/targets/jvm_artifact.mdx +++ b/versioned_docs/version-2.16/reference/targets/jvm_artifact.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.java` @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.16/reference/targets/jvm_war.mdx b/versioned_docs/version-2.16/reference/targets/jvm_war.mdx index e90461bb8..7cc0571b7 100644 --- a/versioned_docs/version-2.16/reference/targets/jvm_war.mdx +++ b/versioned_docs/version-2.16/reference/targets/jvm_war.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.java` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -74,9 +74,9 @@ A list of addresses to `resources` and `files` targets with content to place in Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -126,7 +126,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. diff --git a/versioned_docs/version-2.16/reference/targets/kotlin_junit_test.mdx b/versioned_docs/version-2.16/reference/targets/kotlin_junit_test.mdx index d7bd6aa09..8a860b1a2 100644 --- a/versioned_docs/version-2.16/reference/targets/kotlin_junit_test.mdx +++ b/versioned_docs/version-2.16/reference/targets/kotlin_junit_test.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.kotlin` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.16/reference/targets/kotlin_junit_tests.mdx b/versioned_docs/version-2.16/reference/targets/kotlin_junit_tests.mdx index b053438c3..a2f9ec28e 100644 --- a/versioned_docs/version-2.16/reference/targets/kotlin_junit_tests.mdx +++ b/versioned_docs/version-2.16/reference/targets/kotlin_junit_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.kotlin` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -65,9 +65,9 @@ Example: `sources=['*Test.kt', '!TestIgnore.kt']` Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.16/reference/targets/kotlin_source.mdx b/versioned_docs/version-2.16/reference/targets/kotlin_source.mdx index 2626c317e..ec2ae18c3 100644 --- a/versioned_docs/version-2.16/reference/targets/kotlin_source.mdx +++ b/versioned_docs/version-2.16/reference/targets/kotlin_source.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.kotlin` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.16/reference/targets/kotlin_sources.mdx b/versioned_docs/version-2.16/reference/targets/kotlin_sources.mdx index d40d4f24f..feac16fbf 100644 --- a/versioned_docs/version-2.16/reference/targets/kotlin_sources.mdx +++ b/versioned_docs/version-2.16/reference/targets/kotlin_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.kotlin` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -77,9 +77,9 @@ If true, don't run Ktlint on this target's code. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.16/reference/targets/kotlinc_plugin.mdx b/versioned_docs/version-2.16/reference/targets/kotlinc_plugin.mdx index 1053e4583..c84b49d86 100644 --- a/versioned_docs/version-2.16/reference/targets/kotlinc_plugin.mdx +++ b/versioned_docs/version-2.16/reference/targets/kotlinc_plugin.mdx @@ -33,7 +33,7 @@ Backend: `pants.backend.experimental.kotlin` @@ -46,7 +46,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.16/reference/targets/local_environment.mdx b/versioned_docs/version-2.16/reference/targets/local_environment.mdx index 7153504fd..6c1ac7d2a 100644 --- a/versioned_docs/version-2.16/reference/targets/local_environment.mdx +++ b/versioned_docs/version-2.16/reference/targets/local_environment.mdx @@ -30,7 +30,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.16/reference/targets/openapi_document.mdx b/versioned_docs/version-2.16/reference/targets/openapi_document.mdx index 946e74090..e6ad1a908 100644 --- a/versioned_docs/version-2.16/reference/targets/openapi_document.mdx +++ b/versioned_docs/version-2.16/reference/targets/openapi_document.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.openapi` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.16/reference/targets/openapi_documents.mdx b/versioned_docs/version-2.16/reference/targets/openapi_documents.mdx index 24a38e3f5..33e814a04 100644 --- a/versioned_docs/version-2.16/reference/targets/openapi_documents.mdx +++ b/versioned_docs/version-2.16/reference/targets/openapi_documents.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.openapi` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -77,9 +77,9 @@ If true, don't run `spectral lint` on this target's code. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.16/reference/targets/openapi_source.mdx b/versioned_docs/version-2.16/reference/targets/openapi_source.mdx index 820aa440d..9ec4b4d20 100644 --- a/versioned_docs/version-2.16/reference/targets/openapi_source.mdx +++ b/versioned_docs/version-2.16/reference/targets/openapi_source.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.openapi` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.16/reference/targets/openapi_sources.mdx b/versioned_docs/version-2.16/reference/targets/openapi_sources.mdx index 93c5f9396..11348f03c 100644 --- a/versioned_docs/version-2.16/reference/targets/openapi_sources.mdx +++ b/versioned_docs/version-2.16/reference/targets/openapi_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.openapi` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -65,9 +65,9 @@ Example: `sources=['*.json']` Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.16/reference/targets/pants_requirements.mdx b/versioned_docs/version-2.16/reference/targets/pants_requirements.mdx index 706b22cde..8c1839d5e 100644 --- a/versioned_docs/version-2.16/reference/targets/pants_requirements.mdx +++ b/versioned_docs/version-2.16/reference/targets/pants_requirements.mdx @@ -30,7 +30,7 @@ Backend: `pants.backend.plugin_development` @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.16/reference/targets/pex_binaries.mdx b/versioned_docs/version-2.16/reference/targets/pex_binaries.mdx index 8fff06448..2ba3b0c70 100644 --- a/versioned_docs/version-2.16/reference/targets/pex_binaries.mdx +++ b/versioned_docs/version-2.16/reference/targets/pex_binaries.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -147,9 +147,9 @@ All dependencies must share the same value for their `resolve` field. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.16/reference/targets/pex_binary.mdx b/versioned_docs/version-2.16/reference/targets/pex_binary.mdx index a07275725..2a2fbce37 100644 --- a/versioned_docs/version-2.16/reference/targets/pex_binary.mdx +++ b/versioned_docs/version-2.16/reference/targets/pex_binary.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -101,9 +101,9 @@ All dependencies must share the same value for their `resolve` field. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -400,7 +400,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. diff --git a/versioned_docs/version-2.16/reference/targets/pipenv_requirements.mdx b/versioned_docs/version-2.16/reference/targets/pipenv_requirements.mdx index 210c817ab..7a90d868e 100644 --- a/versioned_docs/version-2.16/reference/targets/pipenv_requirements.mdx +++ b/versioned_docs/version-2.16/reference/targets/pipenv_requirements.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.16/reference/targets/poetry_requirements.mdx b/versioned_docs/version-2.16/reference/targets/poetry_requirements.mdx index 5a344f0f3..9903211c1 100644 --- a/versioned_docs/version-2.16/reference/targets/poetry_requirements.mdx +++ b/versioned_docs/version-2.16/reference/targets/poetry_requirements.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.16/reference/targets/protobuf_source.mdx b/versioned_docs/version-2.16/reference/targets/protobuf_source.mdx index 6838e1af2..bf3739f4a 100644 --- a/versioned_docs/version-2.16/reference/targets/protobuf_source.mdx +++ b/versioned_docs/version-2.16/reference/targets/protobuf_source.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.codegen.protobuf.python Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -54,9 +54,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.16/reference/targets/protobuf_sources.mdx b/versioned_docs/version-2.16/reference/targets/protobuf_sources.mdx index f98e39bae..1e11ade8a 100644 --- a/versioned_docs/version-2.16/reference/targets/protobuf_sources.mdx +++ b/versioned_docs/version-2.16/reference/targets/protobuf_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.codegen.protobuf.python Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -218,9 +218,9 @@ Whether to generate gRPC code or not. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.16/reference/targets/pyoxidizer_binary.mdx b/versioned_docs/version-2.16/reference/targets/pyoxidizer_binary.mdx index db1b0cbbb..8e0f38142 100644 --- a/versioned_docs/version-2.16/reference/targets/pyoxidizer_binary.mdx +++ b/versioned_docs/version-2.16/reference/targets/pyoxidizer_binary.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.python.pac Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -58,7 +58,7 @@ If undefined, this will use the path to the BUILD file, followed by the target n Regardless of whether you use the default or set this field, the path will end with PyOxidizer's file format of `/{debug,release}/install/`, where `platform` is a Rust platform triplet like `aarch-64-apple-darwin` and `binary_name` is the value of the `binary_name` field. So, using the default for this field, the target `src/python/project:bin` might have a final path like `src.python.project/bin/aarch-64-apple-darwin/release/bin`. -When running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. diff --git a/versioned_docs/version-2.16/reference/targets/python_awslambda.mdx b/versioned_docs/version-2.16/reference/targets/python_awslambda.mdx index ee71f268b..3dd2ae2d2 100644 --- a/versioned_docs/version-2.16/reference/targets/python_awslambda.mdx +++ b/versioned_docs/version-2.16/reference/targets/python_awslambda.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.awslambda.python` @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -54,7 +54,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. @@ -69,9 +69,9 @@ Warning: setting this value risks naming collisions with other package targets y Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.16/reference/targets/python_distribution.mdx b/versioned_docs/version-2.16/reference/targets/python_distribution.mdx index e0233c7b1..14923edcb 100644 --- a/versioned_docs/version-2.16/reference/targets/python_distribution.mdx +++ b/versioned_docs/version-2.16/reference/targets/python_distribution.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -71,9 +71,9 @@ See https://www.pantsbuild.org/v2.16/docs/python-interpreter-compatibility for h Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -108,7 +108,7 @@ Note that Pants will assume that any value that either starts with `:` or has `/ Pants will attempt to infer dependencies, which you can confirm by running: ``` -scie-pants-linux-x86_64 dependencies +pants dependencies ``` diff --git a/versioned_docs/version-2.16/reference/targets/python_google_cloud_function.mdx b/versioned_docs/version-2.16/reference/targets/python_google_cloud_function.mdx index f3d18a9f0..f2ce6320a 100644 --- a/versioned_docs/version-2.16/reference/targets/python_google_cloud_function.mdx +++ b/versioned_docs/version-2.16/reference/targets/python_google_cloud_function.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.google_cloud_function.p Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -54,7 +54,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. @@ -69,9 +69,9 @@ Warning: setting this value risks naming collisions with other package targets y Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.16/reference/targets/python_requirement.mdx b/versioned_docs/version-2.16/reference/targets/python_requirement.mdx index 73eedfda1..35ce8965d 100644 --- a/versioned_docs/version-2.16/reference/targets/python_requirement.mdx +++ b/versioned_docs/version-2.16/reference/targets/python_requirement.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -69,9 +69,9 @@ If the requirement depends on some other requirement to work, such as needing `s Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.16/reference/targets/python_requirements.mdx b/versioned_docs/version-2.16/reference/targets/python_requirements.mdx index acd851f5c..41a91aa43 100644 --- a/versioned_docs/version-2.16/reference/targets/python_requirements.mdx +++ b/versioned_docs/version-2.16/reference/targets/python_requirements.mdx @@ -30,7 +30,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.16/reference/targets/python_source.mdx b/versioned_docs/version-2.16/reference/targets/python_source.mdx index 2b34a0302..bbdf93def 100644 --- a/versioned_docs/version-2.16/reference/targets/python_source.mdx +++ b/versioned_docs/version-2.16/reference/targets/python_source.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -69,9 +69,9 @@ See https://www.pantsbuild.org/v2.16/docs/python-interpreter-compatibility for h Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.16/reference/targets/python_sources.mdx b/versioned_docs/version-2.16/reference/targets/python_sources.mdx index f985f44bd..2ea5e6389 100644 --- a/versioned_docs/version-2.16/reference/targets/python_sources.mdx +++ b/versioned_docs/version-2.16/reference/targets/python_sources.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -283,9 +283,9 @@ The latter mode is similar to creating, activating, and using a virtual environm Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.16/reference/targets/python_test.mdx b/versioned_docs/version-2.16/reference/targets/python_test.mdx index 9f12fe47b..c5537ab92 100644 --- a/versioned_docs/version-2.16/reference/targets/python_test.mdx +++ b/versioned_docs/version-2.16/reference/targets/python_test.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -54,9 +54,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -161,11 +161,11 @@ When tests with the same `batch_compatibility_tag` have incompatibilities in som default_repr={`None`} > -Addresses to targets that can be built with the `scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run. +Addresses to targets that can be built with the `pants package` goal and whose resulting artifacts should be included in the test run. -Pants will build the artifacts as if you had run `scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). +Pants will build the artifacts as if you had run `pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). -You can include anything that can be built by `scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`. +You can include anything that can be built by `pants package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`. diff --git a/versioned_docs/version-2.16/reference/targets/python_test_utils.mdx b/versioned_docs/version-2.16/reference/targets/python_test_utils.mdx index 6fd19fecf..5eb86e054 100644 --- a/versioned_docs/version-2.16/reference/targets/python_test_utils.mdx +++ b/versioned_docs/version-2.16/reference/targets/python_test_utils.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -283,9 +283,9 @@ The latter mode is similar to creating, activating, and using a virtual environm Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.16/reference/targets/python_tests.mdx b/versioned_docs/version-2.16/reference/targets/python_tests.mdx index 1bd4b64db..8a390d504 100644 --- a/versioned_docs/version-2.16/reference/targets/python_tests.mdx +++ b/versioned_docs/version-2.16/reference/targets/python_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -267,9 +267,9 @@ If true, don't run Black on this target's code. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -374,11 +374,11 @@ When tests with the same `batch_compatibility_tag` have incompatibilities in som default_repr={`None`} > -Addresses to targets that can be built with the `scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run. +Addresses to targets that can be built with the `pants package` goal and whose resulting artifacts should be included in the test run. -Pants will build the artifacts as if you had run `scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). +Pants will build the artifacts as if you had run `pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). -You can include anything that can be built by `scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`. +You can include anything that can be built by `pants package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`. diff --git a/versioned_docs/version-2.16/reference/targets/relocated_files.mdx b/versioned_docs/version-2.16/reference/targets/relocated_files.mdx index 62f3ec4e4..346339e69 100644 --- a/versioned_docs/version-2.16/reference/targets/relocated_files.mdx +++ b/versioned_docs/version-2.16/reference/targets/relocated_files.mdx @@ -61,7 +61,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -74,7 +74,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.16/reference/targets/remote_environment.mdx b/versioned_docs/version-2.16/reference/targets/remote_environment.mdx index 9747f0362..17b38233b 100644 --- a/versioned_docs/version-2.16/reference/targets/remote_environment.mdx +++ b/versioned_docs/version-2.16/reference/targets/remote_environment.mdx @@ -32,7 +32,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -45,7 +45,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.16/reference/targets/resource.mdx b/versioned_docs/version-2.16/reference/targets/resource.mdx index 19be80740..ff726ed52 100644 --- a/versioned_docs/version-2.16/reference/targets/resource.mdx +++ b/versioned_docs/version-2.16/reference/targets/resource.mdx @@ -26,7 +26,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -52,9 +52,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.16/reference/targets/resources.mdx b/versioned_docs/version-2.16/reference/targets/resources.mdx index a71e63180..efe77d150 100644 --- a/versioned_docs/version-2.16/reference/targets/resources.mdx +++ b/versioned_docs/version-2.16/reference/targets/resources.mdx @@ -24,7 +24,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -91,9 +91,9 @@ You can specify the same file name in multiple keys, so long as you don't o Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.16/reference/targets/run_shell_command.mdx b/versioned_docs/version-2.16/reference/targets/run_shell_command.mdx index 20f28355d..e1e36c6e7 100644 --- a/versioned_docs/version-2.16/reference/targets/run_shell_command.mdx +++ b/versioned_docs/version-2.16/reference/targets/run_shell_command.mdx @@ -37,7 +37,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -50,7 +50,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.16/reference/targets/scala_junit_test.mdx b/versioned_docs/version-2.16/reference/targets/scala_junit_test.mdx index 7e6fb9b60..5aad958d7 100644 --- a/versioned_docs/version-2.16/reference/targets/scala_junit_test.mdx +++ b/versioned_docs/version-2.16/reference/targets/scala_junit_test.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.scala` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.16/reference/targets/scala_junit_tests.mdx b/versioned_docs/version-2.16/reference/targets/scala_junit_tests.mdx index 38b6be9ef..8bd5a7976 100644 --- a/versioned_docs/version-2.16/reference/targets/scala_junit_tests.mdx +++ b/versioned_docs/version-2.16/reference/targets/scala_junit_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.scala` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -104,9 +104,9 @@ If unset, will default to `[test].timeout_default`; if that option is also unset Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.16/reference/targets/scala_source.mdx b/versioned_docs/version-2.16/reference/targets/scala_source.mdx index cab7c8b3f..4aef57641 100644 --- a/versioned_docs/version-2.16/reference/targets/scala_source.mdx +++ b/versioned_docs/version-2.16/reference/targets/scala_source.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.scala` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.16/reference/targets/scala_sources.mdx b/versioned_docs/version-2.16/reference/targets/scala_sources.mdx index 694621baf..28229364c 100644 --- a/versioned_docs/version-2.16/reference/targets/scala_sources.mdx +++ b/versioned_docs/version-2.16/reference/targets/scala_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.scala` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -103,9 +103,9 @@ If true, don't run `scalafmt` on this target's code. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.16/reference/targets/scalac_plugin.mdx b/versioned_docs/version-2.16/reference/targets/scalac_plugin.mdx index 8ac0fa920..b67cbac68 100644 --- a/versioned_docs/version-2.16/reference/targets/scalac_plugin.mdx +++ b/versioned_docs/version-2.16/reference/targets/scalac_plugin.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.scala` @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.16/reference/targets/scalatest_test.mdx b/versioned_docs/version-2.16/reference/targets/scalatest_test.mdx index 102f10b91..308e060d3 100644 --- a/versioned_docs/version-2.16/reference/targets/scalatest_test.mdx +++ b/versioned_docs/version-2.16/reference/targets/scalatest_test.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.scala` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.16/reference/targets/scalatest_tests.mdx b/versioned_docs/version-2.16/reference/targets/scalatest_tests.mdx index d2ee4c613..9462dd26f 100644 --- a/versioned_docs/version-2.16/reference/targets/scalatest_tests.mdx +++ b/versioned_docs/version-2.16/reference/targets/scalatest_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.scala` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -91,9 +91,9 @@ You can specify the same file name in multiple keys, so long as you don't o Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.16/reference/targets/shell_command.mdx b/versioned_docs/version-2.16/reference/targets/shell_command.mdx index dbd9da4c6..323774678 100644 --- a/versioned_docs/version-2.16/reference/targets/shell_command.mdx +++ b/versioned_docs/version-2.16/reference/targets/shell_command.mdx @@ -42,7 +42,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -55,7 +55,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.16/reference/targets/shell_source.mdx b/versioned_docs/version-2.16/reference/targets/shell_source.mdx index e7baec27c..78a493a6c 100644 --- a/versioned_docs/version-2.16/reference/targets/shell_source.mdx +++ b/versioned_docs/version-2.16/reference/targets/shell_source.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.16/reference/targets/shell_sources.mdx b/versioned_docs/version-2.16/reference/targets/shell_sources.mdx index b4fdb22c5..c1ab5780e 100644 --- a/versioned_docs/version-2.16/reference/targets/shell_sources.mdx +++ b/versioned_docs/version-2.16/reference/targets/shell_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -115,9 +115,9 @@ If true, don't run shfmt on this target's code. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.16/reference/targets/shunit2_test.mdx b/versioned_docs/version-2.16/reference/targets/shunit2_test.mdx index 03c9d1bee..1541552c3 100644 --- a/versioned_docs/version-2.16/reference/targets/shunit2_test.mdx +++ b/versioned_docs/version-2.16/reference/targets/shunit2_test.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -67,9 +67,9 @@ Path is relative to the BUILD file's directory, e.g. `source='example.ext'` Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -119,11 +119,11 @@ Which shell to run the tests with. If unspecified, Pants will look for a shebang default_repr={`None`} > -Addresses to targets that can be built with the `scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run. +Addresses to targets that can be built with the `pants package` goal and whose resulting artifacts should be included in the test run. -Pants will build the artifacts as if you had run `scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). +Pants will build the artifacts as if you had run `pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). -You can include anything that can be built by `scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`. +You can include anything that can be built by `pants package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`. diff --git a/versioned_docs/version-2.16/reference/targets/shunit2_tests.mdx b/versioned_docs/version-2.16/reference/targets/shunit2_tests.mdx index d754d7eb2..504634bf5 100644 --- a/versioned_docs/version-2.16/reference/targets/shunit2_tests.mdx +++ b/versioned_docs/version-2.16/reference/targets/shunit2_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -115,9 +115,9 @@ If true, don't run shfmt on this target's code. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -167,11 +167,11 @@ Which shell to run the tests with. If unspecified, Pants will look for a shebang default_repr={`None`} > -Addresses to targets that can be built with the `scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run. +Addresses to targets that can be built with the `pants package` goal and whose resulting artifacts should be included in the test run. -Pants will build the artifacts as if you had run `scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). +Pants will build the artifacts as if you had run `pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). -You can include anything that can be built by `scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`. +You can include anything that can be built by `pants package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`. diff --git a/versioned_docs/version-2.16/reference/targets/system_binary.mdx b/versioned_docs/version-2.16/reference/targets/system_binary.mdx index 9920f16b2..d7bd775a0 100644 --- a/versioned_docs/version-2.16/reference/targets/system_binary.mdx +++ b/versioned_docs/version-2.16/reference/targets/system_binary.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.adhoc` @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.16/reference/targets/target.mdx b/versioned_docs/version-2.16/reference/targets/target.mdx index 51a2011fb..581ce3561 100644 --- a/versioned_docs/version-2.16/reference/targets/target.mdx +++ b/versioned_docs/version-2.16/reference/targets/target.mdx @@ -26,7 +26,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -52,9 +52,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.16/reference/targets/terraform_module.mdx b/versioned_docs/version-2.16/reference/targets/terraform_module.mdx index 77581b28a..c910536e8 100644 --- a/versioned_docs/version-2.16/reference/targets/terraform_module.mdx +++ b/versioned_docs/version-2.16/reference/targets/terraform_module.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.terraform` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -54,9 +54,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.16/reference/targets/thrift_source.mdx b/versioned_docs/version-2.16/reference/targets/thrift_source.mdx index 6620d9f96..d4ac0fc26 100644 --- a/versioned_docs/version-2.16/reference/targets/thrift_source.mdx +++ b/versioned_docs/version-2.16/reference/targets/thrift_source.mdx @@ -27,7 +27,7 @@ Backend: `pants.backend.codegen.thrift.apache.p Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -40,7 +40,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -53,9 +53,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.16/reference/targets/thrift_sources.mdx b/versioned_docs/version-2.16/reference/targets/thrift_sources.mdx index 7987802fd..4ca3bc64c 100644 --- a/versioned_docs/version-2.16/reference/targets/thrift_sources.mdx +++ b/versioned_docs/version-2.16/reference/targets/thrift_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.codegen.thrift.apache.p Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -106,9 +106,9 @@ All dependencies must share the same value for their `resolve` field. Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.16/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.16/reference/targets/vcs_version.mdx b/versioned_docs/version-2.16/reference/targets/vcs_version.mdx index 948560922..ec23fdece 100644 --- a/versioned_docs/version-2.16/reference/targets/vcs_version.mdx +++ b/versioned_docs/version-2.16/reference/targets/vcs_version.mdx @@ -30,7 +30,7 @@ Backend: `pants.backend.experimental.python` @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.17/reference/global-options.mdx b/versioned_docs/version-2.17/reference/global-options.mdx index ed0b29c02..a0e2e212a 100644 --- a/versioned_docs/version-2.17/reference/global-options.mdx +++ b/versioned_docs/version-2.17/reference/global-options.mdx @@ -317,9 +317,9 @@ ignore_warnings = [ Use this Pants version. Note that Pants only uses this to verify that you are using the requested version, as Pants cannot dynamically change the version it is using once the program is already running. -If you use the `scie-pants-linux-x86_64` script from https://www.pantsbuild.org/v2.17/docs/installation, however, changing the value in your `pants.toml` will cause the new version to be installed and run automatically. +If you use the `pants` script from https://www.pantsbuild.org/v2.17/docs/installation, however, changing the value in your `pants.toml` will cause the new version to be installed and run automatically. -Run `scie-pants-linux-x86_64 --version` to check what is being used. +Run `pants --version` to check what is being used. @@ -832,7 +832,7 @@ Whether or not to use nailgun to run JVM requests that are marked as supporting default_repr={`3`} > -The time in seconds to wait when gracefully shutting down an interactive process (such as one opened using `scie-pants-linux-x86_64 run`) before killing it. +The time in seconds to wait when gracefully shutting down an interactive process (such as one opened using `pants run`) before killing it. diff --git a/versioned_docs/version-2.17/reference/goals/experimental-bsp.mdx b/versioned_docs/version-2.17/reference/goals/experimental-bsp.mdx index 5362d9e2f..501fe81ee 100644 --- a/versioned_docs/version-2.17/reference/goals/experimental-bsp.mdx +++ b/versioned_docs/version-2.17/reference/goals/experimental-bsp.mdx @@ -79,7 +79,7 @@ Run the Build Server Protocol server. Pants will receive BSP RPC requests via th Environment variables to set in the BSP runner script when setting up BSP in a repository. Entries are either strings in the form `ENV_VAR=value` to set an explicit value; or just `ENV_VAR` to copy the value from Pants' own environment when the experimental-bsp goal was run. -This option only takes effect when the BSP runner script is written. If the option changes, you must run `scie-pants-linux-x86_64 experimental-bsp` again to write a new copy of the BSP runner script. +This option only takes effect when the BSP runner script is written. If the option changes, you must run `pants experimental-bsp` again to write a new copy of the BSP runner script. Note: The environment variables passed to the Pants BSP server will be those set for your IDE and not your shell. For example, on macOS, the IDE is generally launched by `launchd` after clicking on a Dock icon, and not from the shell. Thus, any environment variables set for your shell will likely not be seen by the Pants BSP server. At the very least, on macOS consider writing an explicit PATH into the BSP runner script via this option. diff --git a/versioned_docs/version-2.17/reference/goals/fix.mdx b/versioned_docs/version-2.17/reference/goals/fix.mdx index 3d3070e5c..27e6876f3 100644 --- a/versioned_docs/version-2.17/reference/goals/fix.mdx +++ b/versioned_docs/version-2.17/reference/goals/fix.mdx @@ -47,7 +47,7 @@ You can repeat this option, e.g. `fix --only=autoflake --only=pyupgrade` or `fix If true, skip running all formatters. -FYI: when running `scie-pants-linux-x86_64 fix fmt ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `fix` where possible. +FYI: when running `pants fix fmt ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `fix` where possible. diff --git a/versioned_docs/version-2.17/reference/goals/generate-lockfiles.mdx b/versioned_docs/version-2.17/reference/goals/generate-lockfiles.mdx index 4b1f0a8cb..022833e0f 100644 --- a/versioned_docs/version-2.17/reference/goals/generate-lockfiles.mdx +++ b/versioned_docs/version-2.17/reference/goals/generate-lockfiles.mdx @@ -33,7 +33,7 @@ Only generate lockfiles for the specified resolve(s). Resolves are the logical names for the different lockfiles used in your project. For your own code's dependencies, these come from backend-specific configuration such as `[python].resolves`. For tool lockfiles, resolve names are the options scope for that tool such as `black`, `pytest`, and `mypy-protobuf`. -For example, you can run `scie-pants-linux-x86_64 generate-lockfiles --resolve=black --resolve=pytest --resolve=data-science` to only generate lockfiles for those two tools and your resolve named `data-science`. +For example, you can run `pants generate-lockfiles --resolve=black --resolve=pytest --resolve=data-science` to only generate lockfiles for those two tools and your resolve named `data-science`. If you specify an invalid resolve name, like 'fake', Pants will output all possible values. @@ -75,7 +75,7 @@ Include unchanged distributions in the diff summary output. Implies `diff=true`. default_repr={`None`} > -If set, lockfile headers will say to run this command to regenerate the lockfile, rather than running `scie-pants-linux-x86_64 generate-lockfiles --resolve=` like normal. +If set, lockfile headers will say to run this command to regenerate the lockfile, rather than running `pants generate-lockfiles --resolve=` like normal. diff --git a/versioned_docs/version-2.17/reference/goals/lint.mdx b/versioned_docs/version-2.17/reference/goals/lint.mdx index e9e09a67b..21b78f2d4 100644 --- a/versioned_docs/version-2.17/reference/goals/lint.mdx +++ b/versioned_docs/version-2.17/reference/goals/lint.mdx @@ -47,7 +47,7 @@ You can repeat this option, e.g. `lint --only=flake8 --only=shellcheck` or `lint If true, skip running all formatters in check-only mode. -FYI: when running `scie-pants-linux-x86_64 fmt lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `lint` where possible. +FYI: when running `pants fmt lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `lint` where possible. @@ -61,7 +61,7 @@ FYI: when running `scie-pants-linux-x86_64 fmt lint ::`, there should be diminis If true, skip running all fixers in check-only mode. -FYI: when running `scie-pants-linux-x86_64 fix lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fix` when running `lint` where possible. +FYI: when running `pants fix lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fix` when running `lint` where possible. diff --git a/versioned_docs/version-2.17/reference/help-all.json b/versioned_docs/version-2.17/reference/help-all.json index 8aedddcc9..290bd0941 100644 --- a/versioned_docs/version-2.17/reference/help-all.json +++ b/versioned_docs/version-2.17/reference/help-all.json @@ -37583,7 +37583,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -37591,7 +37591,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -37615,7 +37615,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -37623,7 +37623,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -37639,7 +37639,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -37655,7 +37655,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -37663,7 +37663,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -37679,7 +37679,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -37695,7 +37695,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -37703,7 +37703,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -37839,7 +37839,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -37847,7 +37847,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -37855,7 +37855,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -37863,7 +37863,7 @@ { "alias": "packages", "default": null, - "description": "Addresses to any targets that can be built with `scie-pants-linux-x86_64 package`, e.g. `[\"project:app\"]`.\n\nPants will build the assets as if you had run `scie-pants-linux-x86_64 package`. It will include the results in your archive using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or even another `archive`.", + "description": "Addresses to any targets that can be built with `pants package`, e.g. `[\"project:app\"]`.\n\nPants will build the assets as if you had run `pants package`. It will include the results in your archive using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `pants package`, e.g. a `pex_binary`, `python_awslambda`, or even another `archive`.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -37895,7 +37895,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -37903,7 +37903,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -37919,7 +37919,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -37927,7 +37927,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -37983,7 +37983,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -37991,7 +37991,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -38247,7 +38247,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -38255,7 +38255,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -38271,7 +38271,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -38351,7 +38351,7 @@ { "alias": "skip_push", "default": "False", - "description": "If true, do not push this image to registries when running `scie-pants-linux-x86_64 publish`.", + "description": "If true, do not push this image to registries when running `pants publish`.", "provider": "", "required": false, "type_hint": "bool" @@ -38383,7 +38383,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -38415,7 +38415,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -38423,7 +38423,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -38511,7 +38511,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -38519,7 +38519,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -38551,7 +38551,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -38559,7 +38559,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -38591,7 +38591,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -38599,7 +38599,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -38631,7 +38631,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -38639,7 +38639,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -38671,7 +38671,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -38679,7 +38679,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -38711,7 +38711,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -38719,7 +38719,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -38751,7 +38751,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -38759,7 +38759,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -38767,7 +38767,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -38791,7 +38791,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -38799,7 +38799,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -38823,7 +38823,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -38839,7 +38839,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -38847,7 +38847,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -38855,7 +38855,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -38951,7 +38951,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -38959,7 +38959,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -39031,7 +39031,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -39039,7 +39039,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -39047,7 +39047,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -39143,7 +39143,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -39151,7 +39151,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -39159,7 +39159,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -39183,7 +39183,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -39191,7 +39191,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -39239,7 +39239,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -39247,7 +39247,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -39271,7 +39271,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -39279,7 +39279,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built directory tree should be located.\n\nIf undefined, this will use the path to the BUILD file, For example, `src/charts/mychart:tgt_name` would be `src.charts.mychart/tgt_name/`.\n\nRegardless of whether you use the default or set this field, the path will end with Helms's file format of `-.tgz`, where `chart_name` and `chart_version` are the values extracted from the Chart.yaml file. So, using the default for this field, the target `src/charts/mychart:tgt_name` might have a final path like `src.charts.mychart/tgt_name/mychart-0.1.0.tgz`.\n\nWhen running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built directory tree should be located.\n\nIf undefined, this will use the path to the BUILD file, For example, `src/charts/mychart:tgt_name` would be `src.charts.mychart/tgt_name/`.\n\nRegardless of whether you use the default or set this field, the path will end with Helms's file format of `-.tgz`, where `chart_name` and `chart_version` are the values extracted from the Chart.yaml file. So, using the default for this field, the target `src/charts/mychart:tgt_name` might have a final path like `src.charts.mychart/tgt_name/mychart-0.1.0.tgz`.\n\nWhen running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -39311,7 +39311,7 @@ { "alias": "skip_push", "default": "False", - "description": "If set to true, do not push this Helm chart to registries when running `scie-pants-linux-x86_64 publish`.", + "description": "If set to true, do not push this Helm chart to registries when running `pants publish`.", "provider": "", "required": false, "type_hint": "bool" @@ -39319,7 +39319,7 @@ { "alias": "skip_lint", "default": "False", - "description": "If set to true, do not run any linting in this Helm chart when running `scie-pants-linux-x86_64 lint`.", + "description": "If set to true, do not run any linting in this Helm chart when running `pants lint`.", "provider": "", "required": false, "type_hint": "bool" @@ -39335,7 +39335,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -39343,7 +39343,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -39359,7 +39359,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -39447,7 +39447,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -39455,7 +39455,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -39471,7 +39471,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -39503,7 +39503,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -39511,7 +39511,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -39527,7 +39527,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -39567,7 +39567,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -39575,7 +39575,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -39583,7 +39583,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -39647,7 +39647,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -39655,7 +39655,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -39679,7 +39679,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -39727,7 +39727,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -39735,7 +39735,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -39767,7 +39767,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -39807,7 +39807,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -39815,7 +39815,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -39847,7 +39847,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -39887,7 +39887,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -39895,7 +39895,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -39991,7 +39991,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -39999,7 +39999,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -40023,7 +40023,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -40047,7 +40047,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -40063,7 +40063,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -40071,7 +40071,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -40079,7 +40079,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -40151,7 +40151,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -40159,7 +40159,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -40175,7 +40175,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -40239,7 +40239,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -40247,7 +40247,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -40255,7 +40255,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -40327,7 +40327,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -40335,7 +40335,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -40359,7 +40359,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -40415,7 +40415,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -40423,7 +40423,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -40463,7 +40463,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -40471,7 +40471,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -40719,7 +40719,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -40727,7 +40727,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -40735,7 +40735,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -40767,7 +40767,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -40775,7 +40775,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -40799,7 +40799,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -40815,7 +40815,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -40823,7 +40823,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -40831,7 +40831,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -40855,7 +40855,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -40863,7 +40863,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -40879,7 +40879,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -40895,7 +40895,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -40903,7 +40903,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -40935,7 +40935,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -40943,7 +40943,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -40991,7 +40991,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -41135,7 +41135,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -41143,7 +41143,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -41175,7 +41175,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -41343,7 +41343,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -41359,7 +41359,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -41367,7 +41367,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -41423,7 +41423,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -41431,7 +41431,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -41487,7 +41487,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -41495,7 +41495,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -41503,7 +41503,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -41599,7 +41599,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -41607,7 +41607,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -41703,7 +41703,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -41719,7 +41719,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -41727,7 +41727,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -41735,7 +41735,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built directory tree should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:bin` would be `src.python.project/bin/`.\n\nRegardless of whether you use the default or set this field, the path will end with PyOxidizer's file format of `/{debug,release}/install/`, where `platform` is a Rust platform triplet like `aarch-64-apple-darwin` and `binary_name` is the value of the `binary_name` field. So, using the default for this field, the target `src/python/project:bin` might have a final path like `src.python.project/bin/aarch-64-apple-darwin/release/bin`.\n\nWhen running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built directory tree should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:bin` would be `src.python.project/bin/`.\n\nRegardless of whether you use the default or set this field, the path will end with PyOxidizer's file format of `/{debug,release}/install/`, where `platform` is a Rust platform triplet like `aarch-64-apple-darwin` and `binary_name` is the value of the `binary_name` field. So, using the default for this field, the target `src/python/project:bin` might have a final path like `src.python.project/bin/aarch-64-apple-darwin/release/bin`.\n\nWhen running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -41799,7 +41799,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -41807,7 +41807,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -41815,7 +41815,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -41823,7 +41823,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -41887,7 +41887,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -41895,7 +41895,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -41911,7 +41911,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -41919,7 +41919,7 @@ { "alias": "entry_points", "default": null, - "description": "Any entry points, such as `console_scripts` and `gui_scripts`.\n\nSpecify as a nested dictionary, with a dictionary for each type of entry point, e.g. `console_scripts` vs. `gui_scripts`. Each dictionary maps the entry point name to either a setuptools entry point (`\"path.to.module:func\"`) or a Pants target address to a `pex_binary` target.\n\nExample:\n\n entry_points={\n \"console_scripts\": {\n \"my-script\": \"project.app:main\",\n \"another-script\": \"project/subdir:pex_binary_tgt\"\n }\n }\n\nNote that Pants will assume that any value that either starts with `:` or has `/` in it, is a target address to a `pex_binary` target. Otherwise, it will assume it's a setuptools entry point as defined by https://packaging.python.org/specifications/entry-points/#entry-points-specification. Use `//` as a prefix for target addresses if you need to disambiguate.\n\nPants will attempt to infer dependencies, which you can confirm by running:\n\n scie-pants-linux-x86_64 dependencies ", + "description": "Any entry points, such as `console_scripts` and `gui_scripts`.\n\nSpecify as a nested dictionary, with a dictionary for each type of entry point, e.g. `console_scripts` vs. `gui_scripts`. Each dictionary maps the entry point name to either a setuptools entry point (`\"path.to.module:func\"`) or a Pants target address to a `pex_binary` target.\n\nExample:\n\n entry_points={\n \"console_scripts\": {\n \"my-script\": \"project.app:main\",\n \"another-script\": \"project/subdir:pex_binary_tgt\"\n }\n }\n\nNote that Pants will assume that any value that either starts with `:` or has `/` in it, is a target address to a `pex_binary` target. Otherwise, it will assume it's a setuptools entry point as defined by https://packaging.python.org/specifications/entry-points/#entry-points-specification. Use `//` as a prefix for target addresses if you need to disambiguate.\n\nPants will attempt to infer dependencies, which you can confirm by running:\n\n pants dependencies ", "provider": "", "required": false, "type_hint": "Dict[str, Dict[str, str]] | None" @@ -42031,7 +42031,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -42039,7 +42039,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -42047,7 +42047,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -42055,7 +42055,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -42119,7 +42119,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -42127,7 +42127,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -42143,7 +42143,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -42191,7 +42191,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -42199,7 +42199,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -42255,7 +42255,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -42263,7 +42263,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -42279,7 +42279,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -42431,7 +42431,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -42439,7 +42439,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -42583,7 +42583,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -42615,7 +42615,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -42623,7 +42623,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -42631,7 +42631,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -42679,7 +42679,7 @@ { "alias": "runtime_package_dependencies", "default": null, - "description": "Addresses to targets that can be built with the `scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`.", + "description": "Addresses to targets that can be built with the `pants package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `pants package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -42847,7 +42847,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -42855,7 +42855,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -42999,7 +42999,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -43023,7 +43023,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -43031,7 +43031,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -43167,7 +43167,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -43215,7 +43215,7 @@ { "alias": "runtime_package_dependencies", "default": null, - "description": "Addresses to targets that can be built with the `scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`.", + "description": "Addresses to targets that can be built with the `pants package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `pants package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -43263,7 +43263,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -43271,7 +43271,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -43311,7 +43311,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -43319,7 +43319,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -43583,7 +43583,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -43591,7 +43591,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -43599,7 +43599,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -43623,7 +43623,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -43631,7 +43631,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -43655,7 +43655,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -43671,7 +43671,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -43679,7 +43679,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -43727,7 +43727,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -43735,7 +43735,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -43743,7 +43743,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -43815,7 +43815,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -43823,7 +43823,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -43855,7 +43855,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -43919,7 +43919,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -43927,7 +43927,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -43935,7 +43935,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -44007,7 +44007,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -44015,7 +44015,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -44047,7 +44047,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -44103,7 +44103,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -44111,7 +44111,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -44143,7 +44143,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -44151,7 +44151,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -44159,7 +44159,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -44231,7 +44231,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -44239,7 +44239,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -44263,7 +44263,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -44327,7 +44327,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -44335,7 +44335,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -44455,7 +44455,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -44463,7 +44463,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -44471,7 +44471,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -44511,7 +44511,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -44519,7 +44519,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -44559,7 +44559,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -44575,7 +44575,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -44583,7 +44583,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -44599,7 +44599,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -44631,7 +44631,7 @@ { "alias": "runtime_package_dependencies", "default": null, - "description": "Addresses to targets that can be built with the `scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`.", + "description": "Addresses to targets that can be built with the `pants package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `pants package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -44663,7 +44663,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -44671,7 +44671,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -44711,7 +44711,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -44743,7 +44743,7 @@ { "alias": "runtime_package_dependencies", "default": null, - "description": "Addresses to targets that can be built with the `scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`.", + "description": "Addresses to targets that can be built with the `pants package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `pants package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -44759,7 +44759,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -44767,7 +44767,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -44823,7 +44823,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -44831,7 +44831,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -44839,7 +44839,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -44855,7 +44855,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -44863,7 +44863,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -44871,7 +44871,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -44895,7 +44895,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -44903,7 +44903,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -44911,7 +44911,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -44943,7 +44943,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -44951,7 +44951,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -44983,7 +44983,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -44999,7 +44999,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -45007,7 +45007,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -45373,7 +45373,7 @@ "display_args": ["--pants-version="], "env_var": "PANTS_VERSION", "fromfile": false, - "help": "Use this Pants version. Note that Pants only uses this to verify that you are using the requested version, as Pants cannot dynamically change the version it is using once the program is already running.\n\nIf you use the `scie-pants-linux-x86_64` script from https://www.pantsbuild.org/v2.17/docs/installation, however, changing the value in your `pants.toml` will cause the new version to be installed and run automatically.\n\nRun `scie-pants-linux-x86_64 --version` to check what is being used.", + "help": "Use this Pants version. Note that Pants only uses this to verify that you are using the requested version, as Pants cannot dynamically change the version it is using once the program is already running.\n\nIf you use the `pants` script from https://www.pantsbuild.org/v2.17/docs/installation, however, changing the value in your `pants.toml` will cause the new version to be installed and run automatically.\n\nRun `pants --version` to check what is being used.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pants-version"], @@ -45433,7 +45433,7 @@ { "details": "from env var PANTS_BIN_NAME", "rank": "ENVIRONMENT", - "value": "/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64" + "value": "/home/josh/work/scie-pants/dist/pants" } ] } @@ -46634,7 +46634,7 @@ ], "env_var": "PANTS_PROCESS_EXECUTION_GRACEFUL_SHUTDOWN_TIMEOUT", "fromfile": false, - "help": "The time in seconds to wait when gracefully shutting down an interactive process (such as one opened using `scie-pants-linux-x86_64 run`) before killing it.", + "help": "The time in seconds to wait when gracefully shutting down an interactive process (such as one opened using `pants run`) before killing it.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -48507,7 +48507,7 @@ "display_args": ["--[no-]add-trailing-comma-skip"], "env_var": "PANTS_ADD_TRAILING_COMMA_SKIP", "fromfile": false, - "help": "If true, don't use add-trailing-comma when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use add-trailing-comma when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -48648,7 +48648,7 @@ "display_args": ["--add-trailing-comma-lockfile="], "env_var": "PANTS_ADD_TRAILING_COMMA_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/lint/add_trailing_comma/add_trailing_comma.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=add-trailing-comma`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/lint/add_trailing_comma/add_trailing_comma.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=add-trailing-comma`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": "Custom tool versions are now installed from named resolves, as described at https://www.pantsbuild.org/v2.17/docs/python-lockfiles.\n\n1. If you have an existing resolve that includes the requirements for this tool,\n you can set `[add-trailing-comma].install_from_resolve = \"\".\n This may be the case if the tool also provides a runtime library, and you want\n to specify the version in just one place.\n2. If not, you can set up a new resolve as described at the link above.\n\nEither way, the resolve you choose should provide the requirements currently set by the `version` and `extra-requirements` options for this tool, which you can see by running `pants help-advanced add-trailing-comma`.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--add-trailing-comma-lockfile"], @@ -48681,7 +48681,7 @@ "display_args": ["--[no-]add-trailing-comma-export"], "env_var": "PANTS_ADD_TRAILING_COMMA_EXPORT", "fromfile": false, - "help": "If true, export a virtual environment with add-trailing-comma when running `scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with add-trailing-comma when running `pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": "Use the export goal's --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": [ @@ -49041,7 +49041,7 @@ "display_args": ["--[no-]autoflake-skip"], "env_var": "PANTS_AUTOFLAKE_SKIP", "fromfile": false, - "help": "If true, don't use Autoflake when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Autoflake when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--autoflake-skip", "--no-autoflake-skip"], @@ -49179,7 +49179,7 @@ "display_args": ["--autoflake-lockfile="], "env_var": "PANTS_AUTOFLAKE_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/lint/autoflake/autoflake.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=autoflake`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/lint/autoflake/autoflake.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=autoflake`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": "Custom tool versions are now installed from named resolves, as described at https://www.pantsbuild.org/v2.17/docs/python-lockfiles.\n\n1. If you have an existing resolve that includes the requirements for this tool,\n you can set `[autoflake].install_from_resolve = \"\".\n This may be the case if the tool also provides a runtime library, and you want\n to specify the version in just one place.\n2. If not, you can set up a new resolve as described at the link above.\n\nEither way, the resolve you choose should provide the requirements currently set by the `version` and `extra-requirements` options for this tool, which you can see by running `pants help-advanced autoflake`.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--autoflake-lockfile"], @@ -49212,7 +49212,7 @@ "display_args": ["--[no-]autoflake-export"], "env_var": "PANTS_AUTOFLAKE_EXPORT", "fromfile": false, - "help": "If true, export a virtual environment with Autoflake when running `scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with Autoflake when running `pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": "Use the export goal's --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": [ @@ -49409,7 +49409,7 @@ "display_args": ["--[no-]bandit-skip"], "env_var": "PANTS_BANDIT_SKIP", "fromfile": false, - "help": "If true, don't use Bandit when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Bandit when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--bandit-skip", "--no-bandit-skip"], @@ -49545,7 +49545,7 @@ "display_args": ["--bandit-lockfile="], "env_var": "PANTS_BANDIT_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/lint/bandit/bandit.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=bandit`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/lint/bandit/bandit.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=bandit`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": "Custom tool versions are now installed from named resolves, as described at https://www.pantsbuild.org/v2.17/docs/python-lockfiles.\n\n1. If you have an existing resolve that includes the requirements for this tool,\n you can set `[bandit].install_from_resolve = \"\".\n This may be the case if the tool also provides a runtime library, and you want\n to specify the version in just one place.\n2. If not, you can set up a new resolve as described at the link above.\n\nEither way, the resolve you choose should provide the requirements currently set by the `version` and `extra-requirements` options for this tool, which you can see by running `pants help-advanced bandit`.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--bandit-lockfile"], @@ -49578,7 +49578,7 @@ "display_args": ["--[no-]bandit-export"], "env_var": "PANTS_BANDIT_EXPORT", "fromfile": false, - "help": "If true, export a virtual environment with Bandit when running `scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with Bandit when running `pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": "Use the export goal's --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--bandit-export", "--no-bandit-export"], @@ -49846,7 +49846,7 @@ "display_args": ["--[no-]black-skip"], "env_var": "PANTS_BLACK_SKIP", "fromfile": false, - "help": "If true, don't use Black when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Black when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--black-skip", "--no-black-skip"], @@ -49984,7 +49984,7 @@ "display_args": ["--black-lockfile="], "env_var": "PANTS_BLACK_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/lint/black/black.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=black`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/lint/black/black.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=black`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": "Custom tool versions are now installed from named resolves, as described at https://www.pantsbuild.org/v2.17/docs/python-lockfiles.\n\n1. If you have an existing resolve that includes the requirements for this tool,\n you can set `[black].install_from_resolve = \"\".\n This may be the case if the tool also provides a runtime library, and you want\n to specify the version in just one place.\n2. If not, you can set up a new resolve as described at the link above.\n\nEither way, the resolve you choose should provide the requirements currently set by the `version` and `extra-requirements` options for this tool, which you can see by running `pants help-advanced black`.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--black-lockfile"], @@ -50017,7 +50017,7 @@ "display_args": ["--[no-]black-export"], "env_var": "PANTS_BLACK_EXPORT", "fromfile": false, - "help": "If true, export a virtual environment with Black when running `scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with Black when running `pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": "Use the export goal's --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--black-export", "--no-black-export"], @@ -50317,7 +50317,7 @@ "display_args": ["--[no-]buf-format-skip"], "env_var": "PANTS_BUF_FORMAT_SKIP", "fromfile": false, - "help": "If true, don't use Buf when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Buf when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--buf-format-skip", "--no-buf-format-skip"], @@ -50350,7 +50350,7 @@ "display_args": ["--[no-]buf-lint-skip"], "env_var": "PANTS_BUF_LINT_SKIP", "fromfile": false, - "help": "If true, don't use Buf when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Buf when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--buf-lint-skip", "--no-buf-lint-skip"], @@ -50464,7 +50464,7 @@ "display_args": ["--[no-]build-deprecations-fixer-skip"], "env_var": "PANTS_BUILD_DEPRECATIONS_FIXER_SKIP", "fromfile": false, - "help": "If true, don't use BUILD Deprecations Fixer when running `scie-pants-linux-x86_64 fix`.", + "help": "If true, don't use BUILD Deprecations Fixer when running `pants fix`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -50703,7 +50703,7 @@ "display_args": ["--[no-]buildifier-skip"], "env_var": "PANTS_BUILDIFIER_SKIP", "fromfile": false, - "help": "If true, don't use Buildifier when running `scie-pants-linux-x86_64 fmt`.", + "help": "If true, don't use Buildifier when running `pants fmt`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--buildifier-skip", "--no-buildifier-skip"], @@ -50960,7 +50960,7 @@ "display_args": ["--cli-alias=\"{'key1': val1, 'key2': val2, ...}\""], "env_var": "PANTS_CLI_ALIAS", "fromfile": false, - "help": "Register command line aliases.\n\nExample:\n\n [cli.alias]\n green = \"fmt lint check\"\n all-changed = \"--changed-since=HEAD --changed-dependents=transitive\"\n\nThis would allow you to run `scie-pants-linux-x86_64 green all-changed`, which is shorthand for `scie-pants-linux-x86_64 fmt lint check --changed-since=HEAD --changed-dependents=transitive`.\n\nNotice: this option must be placed in a config file (e.g. `pants.toml` or `pantsrc`) to have any effect.", + "help": "Register command line aliases.\n\nExample:\n\n [cli.alias]\n green = \"fmt lint check\"\n all-changed = \"--changed-since=HEAD --changed-dependents=transitive\"\n\nThis would allow you to run `pants green all-changed`, which is shorthand for `pants fmt lint check --changed-since=HEAD --changed-dependents=transitive`.\n\nNotice: this option must be placed in a config file (e.g. `pants.toml` or `pantsrc`) to have any effect.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--cli-alias"], @@ -51726,7 +51726,7 @@ "display_args": ["--coverage-py-lockfile="], "env_var": "PANTS_COVERAGE_PY_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/subsystems/coverage_py.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=coverage-py`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/subsystems/coverage_py.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=coverage-py`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": "Custom tool versions are now installed from named resolves, as described at https://www.pantsbuild.org/v2.17/docs/python-lockfiles.\n\n1. If you have an existing resolve that includes the requirements for this tool,\n you can set `[coverage-py].install_from_resolve = \"\".\n This may be the case if the tool also provides a runtime library, and you want\n to specify the version in just one place.\n2. If not, you can set up a new resolve as described at the link above.\n\nEither way, the resolve you choose should provide the requirements currently set by the `version` and `extra-requirements` options for this tool, which you can see by running `pants help-advanced coverage-py`.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--coverage-py-lockfile"], @@ -52111,7 +52111,7 @@ "display_args": ["--debugpy-lockfile="], "env_var": "PANTS_DEBUGPY_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/subsystems/debugpy.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=debugpy`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/subsystems/debugpy.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=debugpy`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": "Custom tool versions are now installed from named resolves, as described at https://www.pantsbuild.org/v2.17/docs/python-lockfiles.\n\n1. If you have an existing resolve that includes the requirements for this tool,\n you can set `[debugpy].install_from_resolve = \"\".\n This may be the case if the tool also provides a runtime library, and you want\n to specify the version in just one place.\n2. If not, you can set up a new resolve as described at the link above.\n\nEither way, the resolve you choose should provide the requirements currently set by the `version` and `extra-requirements` options for this tool, which you can see by running `pants help-advanced debugpy`.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--debugpy-lockfile"], @@ -52746,7 +52746,7 @@ "display_args": ["--[no-]docformatter-skip"], "env_var": "PANTS_DOCFORMATTER_SKIP", "fromfile": false, - "help": "If true, don't use docformatter when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use docformatter when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -52887,7 +52887,7 @@ "display_args": ["--docformatter-lockfile="], "env_var": "PANTS_DOCFORMATTER_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/lint/docformatter/docformatter.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=docformatter`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/lint/docformatter/docformatter.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=docformatter`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": "Custom tool versions are now installed from named resolves, as described at https://www.pantsbuild.org/v2.17/docs/python-lockfiles.\n\n1. If you have an existing resolve that includes the requirements for this tool,\n you can set `[docformatter].install_from_resolve = \"\".\n This may be the case if the tool also provides a runtime library, and you want\n to specify the version in just one place.\n2. If not, you can set up a new resolve as described at the link above.\n\nEither way, the resolve you choose should provide the requirements currently set by the `version` and `extra-requirements` options for this tool, which you can see by running `pants help-advanced docformatter`.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--docformatter-lockfile"], @@ -52920,7 +52920,7 @@ "display_args": ["--[no-]docformatter-export"], "env_var": "PANTS_DOCFORMATTER_EXPORT", "fromfile": false, - "help": "If true, export a virtual environment with docformatter when running `scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with docformatter when running `pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": "Use the export goal's --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": [ @@ -53305,7 +53305,7 @@ ], "env_var": "PANTS_DOCKER_RUN_ARGS", "fromfile": false, - "help": "Additional arguments to use for `docker run` invocations.\n\nExample:\n\n $ scie-pants-linux-x86_64 run --docker-run-args=\"-p 127.0.0.1:80:8080/tcp --name demo\" src/example:image -- [image entrypoint args]\n\nTo provide the top-level options to the `docker` client, use `[docker].env_vars` to configure the [Environment variables](https://docs.docker.com/engine/reference/commandline/cli/#environment-variables) as appropriate.\n\nThe arguments for the image entrypoint may be passed on the command line after a double dash (`--`), or using the `--run-args` option.\n\nDefaults to `--interactive --tty` when stdout is connected to a terminal.", + "help": "Additional arguments to use for `docker run` invocations.\n\nExample:\n\n $ pants run --docker-run-args=\"-p 127.0.0.1:80:8080/tcp --name demo\" src/example:image -- [image entrypoint args]\n\nTo provide the top-level options to the `docker` client, use `[docker].env_vars` to configure the [Environment variables](https://docs.docker.com/engine/reference/commandline/cli/#environment-variables) as appropriate.\n\nThe arguments for the image entrypoint may be passed on the command line after a double dash (`--`), or using the `--run-args` option.\n\nDefaults to `--interactive --tty` when stdout is connected to a terminal.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--docker-run-args"], @@ -53519,7 +53519,7 @@ "display_args": ["--dockerfile-parser-lockfile="], "env_var": "PANTS_DOCKERFILE_PARSER_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/docker/subsystems/dockerfile.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=dockerfile-parser`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/docker/subsystems/dockerfile.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=dockerfile-parser`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": "Custom tool versions are now installed from named resolves, as described at https://www.pantsbuild.org/v2.17/docs/python-lockfiles.\n\n1. If you have an existing resolve that includes the requirements for this tool,\n you can set `[dockerfile-parser].install_from_resolve = \"\".\n This may be the case if the tool also provides a runtime library, and you want\n to specify the version in just one place.\n2. If not, you can set up a new resolve as described at the link above.\n\nEither way, the resolve you choose should provide the requirements currently set by the `version` and `extra-requirements` options for this tool, which you can see by running `pants help-advanced dockerfile-parser`.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--dockerfile-parser-lockfile"], @@ -54221,7 +54221,7 @@ ], "env_var": "PANTS_EXPERIMENTAL_BSP_RUNNER_ENV_VARS", "fromfile": false, - "help": "Environment variables to set in the BSP runner script when setting up BSP in a repository. Entries are either strings in the form `ENV_VAR=value` to set an explicit value; or just `ENV_VAR` to copy the value from Pants' own environment when the experimental-bsp goal was run.\n\nThis option only takes effect when the BSP runner script is written. If the option changes, you must run `scie-pants-linux-x86_64 experimental-bsp` again to write a new copy of the BSP runner script.\n\nNote: The environment variables passed to the Pants BSP server will be those set for your IDE and not your shell. For example, on macOS, the IDE is generally launched by `launchd` after clicking on a Dock icon, and not from the shell. Thus, any environment variables set for your shell will likely not be seen by the Pants BSP server. At the very least, on macOS consider writing an explicit PATH into the BSP runner script via this option.", + "help": "Environment variables to set in the BSP runner script when setting up BSP in a repository. Entries are either strings in the form `ENV_VAR=value` to set an explicit value; or just `ENV_VAR` to copy the value from Pants' own environment when the experimental-bsp goal was run.\n\nThis option only takes effect when the BSP runner script is written. If the option changes, you must run `pants experimental-bsp` again to write a new copy of the BSP runner script.\n\nNote: The environment variables passed to the Pants BSP server will be those set for your IDE and not your shell. For example, on macOS, the IDE is generally launched by `launchd` after clicking on a Dock icon, and not from the shell. Thus, any environment variables set for your shell will likely not be seen by the Pants BSP server. At the very least, on macOS consider writing an explicit PATH into the BSP runner script via this option.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--experimental-bsp-runner-env-vars"], @@ -55008,7 +55008,7 @@ "display_args": ["--[no-]fix-skip-formatters"], "env_var": "PANTS_FIX_SKIP_FORMATTERS", "fromfile": false, - "help": "If true, skip running all formatters.\n\nFYI: when running `scie-pants-linux-x86_64 fix fmt ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `fix` where possible.", + "help": "If true, skip running all formatters.\n\nFYI: when running `pants fix fmt ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `fix` where possible.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -55318,7 +55318,7 @@ "display_args": ["--[no-]flake8-skip"], "env_var": "PANTS_FLAKE8_SKIP", "fromfile": false, - "help": "If true, don't use Flake8 when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Flake8 when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--flake8-skip", "--no-flake8-skip"], @@ -55454,7 +55454,7 @@ "display_args": ["--flake8-lockfile="], "env_var": "PANTS_FLAKE8_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/lint/flake8/flake8.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=flake8`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/lint/flake8/flake8.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=flake8`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": "Custom tool versions are now installed from named resolves, as described at https://www.pantsbuild.org/v2.17/docs/python-lockfiles.\n\n1. If you have an existing resolve that includes the requirements for this tool,\n you can set `[flake8].install_from_resolve = \"\".\n This may be the case if the tool also provides a runtime library, and you want\n to specify the version in just one place.\n2. If not, you can set up a new resolve as described at the link above.\n\nEither way, the resolve you choose should provide the requirements currently set by the `version` and `extra-requirements` options for this tool, which you can see by running `pants help-advanced flake8`.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--flake8-lockfile"], @@ -55487,7 +55487,7 @@ "display_args": ["--[no-]flake8-export"], "env_var": "PANTS_FLAKE8_EXPORT", "fromfile": false, - "help": "If true, export a virtual environment with Flake8 when running `scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with Flake8 when running `pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": "Use the export goal's --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--flake8-export", "--no-flake8-export"], @@ -55607,7 +55607,7 @@ "display_args": ["--generate-lockfiles-custom-command="], "env_var": "PANTS_GENERATE_LOCKFILES_CUSTOM_COMMAND", "fromfile": false, - "help": "If set, lockfile headers will say to run this command to regenerate the lockfile, rather than running `scie-pants-linux-x86_64 generate-lockfiles --resolve=` like normal.", + "help": "If set, lockfile headers will say to run this command to regenerate the lockfile, rather than running `pants generate-lockfiles --resolve=` like normal.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--generate-lockfiles-custom-command"], @@ -55639,7 +55639,7 @@ ], "env_var": "PANTS_GENERATE_LOCKFILES_RESOLVE", "fromfile": false, - "help": "Only generate lockfiles for the specified resolve(s).\n\nResolves are the logical names for the different lockfiles used in your project. For your own code's dependencies, these come from backend-specific configuration such as `[python].resolves`. For tool lockfiles, resolve names are the options scope for that tool such as `black`, `pytest`, and `mypy-protobuf`.\n\nFor example, you can run `scie-pants-linux-x86_64 generate-lockfiles --resolve=black --resolve=pytest --resolve=data-science` to only generate lockfiles for those two tools and your resolve named `data-science`.\n\nIf you specify an invalid resolve name, like 'fake', Pants will output all possible values.\n\nIf not specified, Pants will generate lockfiles for all resolves.", + "help": "Only generate lockfiles for the specified resolve(s).\n\nResolves are the logical names for the different lockfiles used in your project. For your own code's dependencies, these come from backend-specific configuration such as `[python].resolves`. For tool lockfiles, resolve names are the options scope for that tool such as `black`, `pytest`, and `mypy-protobuf`.\n\nFor example, you can run `pants generate-lockfiles --resolve=black --resolve=pytest --resolve=data-science` to only generate lockfiles for those two tools and your resolve named `data-science`.\n\nIf you specify an invalid resolve name, like 'fake', Pants will output all possible values.\n\nIf not specified, Pants will generate lockfiles for all resolves.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--generate-lockfiles-resolve"], @@ -56017,7 +56017,7 @@ "display_args": ["--[no-]go-test-skip"], "env_var": "PANTS_GO_TEST_SKIP", "fromfile": false, - "help": "If true, don't use Go test binary when running `scie-pants-linux-x86_64 test`.", + "help": "If true, don't use Go test binary when running `pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--go-test-skip", "--no-go-test-skip"], @@ -56346,7 +56346,7 @@ "display_args": ["--[no-]gofmt-skip"], "env_var": "PANTS_GOFMT_SKIP", "fromfile": false, - "help": "If true, don't use gofmt when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use gofmt when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--gofmt-skip", "--no-gofmt-skip"], @@ -57133,7 +57133,7 @@ "display_args": ["--google-java-format-lockfile="], "env_var": "PANTS_GOOGLE_JAVA_FORMAT_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/java/lint/google_java_format/google_java_format.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=google-java-format`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/java/lint/google_java_format/google_java_format.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=google-java-format`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--google-java-format-lockfile"], @@ -57203,7 +57203,7 @@ "display_args": ["--[no-]google-java-format-skip"], "env_var": "PANTS_GOOGLE_JAVA_FORMAT_SKIP", "fromfile": false, - "help": "If true, don't use Google Java Format when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Google Java Format when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -57749,7 +57749,7 @@ "display_args": ["--[no-]hadolint-skip"], "env_var": "PANTS_HADOLINT_SKIP", "fromfile": false, - "help": "If true, don't use Hadolint when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Hadolint when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--hadolint-skip", "--no-hadolint-skip"], @@ -58414,7 +58414,7 @@ "display_args": ["--helm-k8s-parser-lockfile="], "env_var": "PANTS_HELM_K8S_PARSER_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/helm/subsystems/k8s_parser.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=helm-k8s-parser`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/helm/subsystems/k8s_parser.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=helm-k8s-parser`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": "Custom tool versions are now installed from named resolves, as described at https://www.pantsbuild.org/v2.17/docs/python-lockfiles.\n\n1. If you have an existing resolve that includes the requirements for this tool,\n you can set `[helm-k8s-parser].install_from_resolve = \"\".\n This may be the case if the tool also provides a runtime library, and you want\n to specify the version in just one place.\n2. If not, you can set up a new resolve as described at the link above.\n\nEither way, the resolve you choose should provide the requirements currently set by the `version` and `extra-requirements` options for this tool, which you can see by running `pants help-advanced helm-k8s-parser`.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--helm-k8s-parser-lockfile"], @@ -58631,7 +58631,7 @@ "display_args": ["--helm-post-renderer-lockfile="], "env_var": "PANTS_HELM_POST_RENDERER_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/helm/subsystems/post_renderer.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=helm-post-renderer`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/helm/subsystems/post_renderer.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=helm-post-renderer`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": "Custom tool versions are now installed from named resolves, as described at https://www.pantsbuild.org/v2.17/docs/python-lockfiles.\n\n1. If you have an existing resolve that includes the requirements for this tool,\n you can set `[helm-post-renderer].install_from_resolve = \"\".\n This may be the case if the tool also provides a runtime library, and you want\n to specify the version in just one place.\n2. If not, you can set up a new resolve as described at the link above.\n\nEither way, the resolve you choose should provide the requirements currently set by the `version` and `extra-requirements` options for this tool, which you can see by running `pants help-advanced helm-post-renderer`.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--helm-post-renderer-lockfile"], @@ -58937,7 +58937,7 @@ "display_args": ["--[no-]helm-unittest-skip"], "env_var": "PANTS_HELM_UNITTEST_SKIP", "fromfile": false, - "help": "If true, don't use helmunittestsubsystem when running `scie-pants-linux-x86_64 test`.", + "help": "If true, don't use helmunittestsubsystem when running `pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -59244,7 +59244,7 @@ "display_args": ["--ipython-lockfile="], "env_var": "PANTS_IPYTHON_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/subsystems/ipython.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=ipython`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/subsystems/ipython.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=ipython`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": "Custom tool versions are now installed from named resolves, as described at https://www.pantsbuild.org/v2.17/docs/python-lockfiles.\n\n1. If you have an existing resolve that includes the requirements for this tool,\n you can set `[ipython].install_from_resolve = \"\".\n This may be the case if the tool also provides a runtime library, and you want\n to specify the version in just one place.\n2. If not, you can set up a new resolve as described at the link above.\n\nEither way, the resolve you choose should provide the requirements currently set by the `version` and `extra-requirements` options for this tool, which you can see by running `pants help-advanced ipython`.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--ipython-lockfile"], @@ -59519,7 +59519,7 @@ "display_args": ["--[no-]isort-skip"], "env_var": "PANTS_ISORT_SKIP", "fromfile": false, - "help": "If true, don't use isort when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use isort when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--isort-skip", "--no-isort-skip"], @@ -59655,7 +59655,7 @@ "display_args": ["--isort-lockfile="], "env_var": "PANTS_ISORT_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/lint/isort/isort.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=isort`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/lint/isort/isort.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=isort`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": "Custom tool versions are now installed from named resolves, as described at https://www.pantsbuild.org/v2.17/docs/python-lockfiles.\n\n1. If you have an existing resolve that includes the requirements for this tool,\n you can set `[isort].install_from_resolve = \"\".\n This may be the case if the tool also provides a runtime library, and you want\n to specify the version in just one place.\n2. If not, you can set up a new resolve as described at the link above.\n\nEither way, the resolve you choose should provide the requirements currently set by the `version` and `extra-requirements` options for this tool, which you can see by running `pants help-advanced isort`.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--isort-lockfile"], @@ -59688,7 +59688,7 @@ "display_args": ["--[no-]isort-export"], "env_var": "PANTS_ISORT_EXPORT", "fromfile": false, - "help": "If true, export a virtual environment with isort when running `scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with isort when running `pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": "Use the export goal's --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--isort-export", "--no-isort-export"], @@ -59796,7 +59796,7 @@ "display_args": ["--jarjar-lockfile="], "env_var": "PANTS_JARJAR_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/jvm/shading/jarjar.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=jarjar`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/jvm/shading/jarjar.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=jarjar`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--jarjar-lockfile"], @@ -60216,7 +60216,7 @@ "display_args": ["--junit-lockfile="], "env_var": "PANTS_JUNIT_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/jvm/test/junit.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=junit`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/jvm/test/junit.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=junit`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--junit-lockfile"], @@ -60320,7 +60320,7 @@ "display_args": ["--[no-]junit-skip"], "env_var": "PANTS_JUNIT_SKIP", "fromfile": false, - "help": "If true, don't use JUnit when running `scie-pants-linux-x86_64 test`.", + "help": "If true, don't use JUnit when running `pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--junit-skip", "--no-junit-skip"], @@ -60973,7 +60973,7 @@ "display_args": ["--ktlint-lockfile="], "env_var": "PANTS_KTLINT_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/kotlin/lint/ktlint/ktlint.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=ktlint`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/kotlin/lint/ktlint/ktlint.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=ktlint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--ktlint-lockfile"], @@ -61041,7 +61041,7 @@ "display_args": ["--[no-]ktlint-skip"], "env_var": "PANTS_KTLINT_SKIP", "fromfile": false, - "help": "If true, don't use Ktlint when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Ktlint when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--ktlint-skip", "--no-ktlint-skip"], @@ -61348,7 +61348,7 @@ "display_args": ["--lambdex-lockfile="], "env_var": "PANTS_LAMBDEX_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/subsystems/lambdex.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=lambdex`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/subsystems/lambdex.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=lambdex`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": "Custom tool versions are now installed from named resolves, as described at https://www.pantsbuild.org/v2.17/docs/python-lockfiles.\n\n1. If you have an existing resolve that includes the requirements for this tool,\n you can set `[lambdex].install_from_resolve = \"\".\n This may be the case if the tool also provides a runtime library, and you want\n to specify the version in just one place.\n2. If not, you can set up a new resolve as described at the link above.\n\nEither way, the resolve you choose should provide the requirements currently set by the `version` and `extra-requirements` options for this tool, which you can see by running `pants help-advanced lambdex`.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--lambdex-lockfile"], @@ -61458,7 +61458,7 @@ "display_args": ["--[no-]lint-skip-formatters"], "env_var": "PANTS_LINT_SKIP_FORMATTERS", "fromfile": false, - "help": "If true, skip running all formatters in check-only mode.\n\nFYI: when running `scie-pants-linux-x86_64 fmt lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `lint` where possible.", + "help": "If true, skip running all formatters in check-only mode.\n\nFYI: when running `pants fmt lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `lint` where possible.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -61497,7 +61497,7 @@ "display_args": ["--[no-]lint-skip-fixers"], "env_var": "PANTS_LINT_SKIP_FIXERS", "fromfile": false, - "help": "If true, skip running all fixers in check-only mode.\n\nFYI: when running `scie-pants-linux-x86_64 fix lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fix` when running `lint` where possible.", + "help": "If true, skip running all fixers in check-only mode.\n\nFYI: when running `pants fix lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fix` when running `lint` where possible.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -61909,7 +61909,7 @@ "display_args": ["--[no-]mypy-skip"], "env_var": "PANTS_MYPY_SKIP", "fromfile": false, - "help": "If true, don't use MyPy when running `scie-pants-linux-x86_64 check`.", + "help": "If true, don't use MyPy when running `pants check`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--mypy-skip", "--no-mypy-skip"], @@ -62045,7 +62045,7 @@ "display_args": ["--mypy-lockfile="], "env_var": "PANTS_MYPY_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/typecheck/mypy/mypy.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=mypy`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/typecheck/mypy/mypy.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=mypy`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": "Custom tool versions are now installed from named resolves, as described at https://www.pantsbuild.org/v2.17/docs/python-lockfiles.\n\n1. If you have an existing resolve that includes the requirements for this tool,\n you can set `[mypy].install_from_resolve = \"\".\n This may be the case if the tool also provides a runtime library, and you want\n to specify the version in just one place.\n2. If not, you can set up a new resolve as described at the link above.\n\nEither way, the resolve you choose should provide the requirements currently set by the `version` and `extra-requirements` options for this tool, which you can see by running `pants help-advanced mypy`.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--mypy-lockfile"], @@ -62078,7 +62078,7 @@ "display_args": ["--[no-]mypy-export"], "env_var": "PANTS_MYPY_EXPORT", "fromfile": false, - "help": "If true, export a virtual environment with MyPy when running `scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with MyPy when running `pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": "Use the export goal's --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--mypy-export", "--no-mypy-export"], @@ -62146,7 +62146,7 @@ "display_args": ["--mypy-extra-type-stubs-lockfile="], "env_var": "PANTS_MYPY_EXTRA_TYPE_STUBS_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile for the option `[mypy].extra_type_stubs`.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this if you use `[mypy].extra_type_stubs`, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=mypy-extra-type-stubs`.", + "help": "Path to a lockfile for the option `[mypy].extra_type_stubs`.\n\nSet to the string `` to opt out of using a lockfile. We do not recommend this if you use `[mypy].extra_type_stubs`, though, as lockfiles are essential for reproducible builds and supply-chain security.\n\nTo use a lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=mypy-extra-type-stubs`.", "removal_hint": "Extra type stubs are now installed from a named resolve, as described at https://www.pantsbuild.org/v2.17/docs/python-lockfiles.", "removal_version": "2.18.0dev0", "scoped_cmd_line_args": ["--mypy-extra-type-stubs-lockfile"], @@ -62357,7 +62357,7 @@ "display_args": ["--mypy-protobuf-lockfile="], "env_var": "PANTS_MYPY_PROTOBUF_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/codegen/protobuf/python/mypy_protobuf.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=mypy-protobuf`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/codegen/protobuf/python/mypy_protobuf.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=mypy-protobuf`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": "Custom tool versions are now installed from named resolves, as described at https://www.pantsbuild.org/v2.17/docs/python-lockfiles.\n\n1. If you have an existing resolve that includes the requirements for this tool,\n you can set `[mypy-protobuf].install_from_resolve = \"\".\n This may be the case if the tool also provides a runtime library, and you want\n to specify the version in just one place.\n2. If not, you can set up a new resolve as described at the link above.\n\nEither way, the resolve you choose should provide the requirements currently set by the `version` and `extra-requirements` options for this tool, which you can see by running `pants help-advanced mypy-protobuf`.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--mypy-protobuf-lockfile"], @@ -62557,7 +62557,7 @@ ], "env_var": "PANTS_NODEJS_RESOLVES", "fromfile": false, - "help": "A mapping of names to lockfile paths used in your project.\n\nSpecifying a resolve name is optional. If unspecified, the default resolve name is calculated by taking the path from the source root to the directory containing the lockfile and replacing '/' with '.' in that path.\n\nExample: An npm lockfile located at `src/js/package/package-lock.json' will result in a resolve named `js.package`, assuming src/ is a source root.\n\nRun `scie-pants-linux-x86_64 generate-lockfiles` to generate the lockfile(s).", + "help": "A mapping of names to lockfile paths used in your project.\n\nSpecifying a resolve name is optional. If unspecified, the default resolve name is calculated by taking the path from the source root to the directory containing the lockfile and replacing '/' with '.' in that path.\n\nExample: An npm lockfile located at `src/js/package/package-lock.json' will result in a resolve named `js.package`, assuming src/ is a source root.\n\nRun `pants generate-lockfiles` to generate the lockfile(s).", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--nodejs-resolves"], @@ -63442,7 +63442,7 @@ "display_args": ["--[no-]preamble-skip"], "env_var": "PANTS_PREAMBLE_SKIP", "fromfile": false, - "help": "If true, don't use preamble when running `scie-pants-linux-x86_64 fmt`.", + "help": "If true, don't use preamble when running `pants fmt`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--preamble-skip", "--no-preamble-skip"], @@ -63598,7 +63598,7 @@ "display_args": ["--protobuf-java-grpc-lockfile="], "env_var": "PANTS_PROTOBUF_JAVA_GRPC_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/codegen/protobuf/java/grpc-java.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=protobuf-java-grpc`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/codegen/protobuf/java/grpc-java.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=protobuf-java-grpc`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--protobuf-java-grpc-lockfile"], @@ -64294,7 +64294,7 @@ "display_args": ["--[no-]pydocstyle-skip"], "env_var": "PANTS_PYDOCSTYLE_SKIP", "fromfile": false, - "help": "If true, don't use Pydocstyle when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Pydocstyle when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pydocstyle-skip", "--no-pydocstyle-skip"], @@ -64432,7 +64432,7 @@ "display_args": ["--pydocstyle-lockfile="], "env_var": "PANTS_PYDOCSTYLE_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/lint/pydocstyle/pydocstyle.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=pydocstyle`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/lint/pydocstyle/pydocstyle.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=pydocstyle`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": "Custom tool versions are now installed from named resolves, as described at https://www.pantsbuild.org/v2.17/docs/python-lockfiles.\n\n1. If you have an existing resolve that includes the requirements for this tool,\n you can set `[pydocstyle].install_from_resolve = \"\".\n This may be the case if the tool also provides a runtime library, and you want\n to specify the version in just one place.\n2. If not, you can set up a new resolve as described at the link above.\n\nEither way, the resolve you choose should provide the requirements currently set by the `version` and `extra-requirements` options for this tool, which you can see by running `pants help-advanced pydocstyle`.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--pydocstyle-lockfile"], @@ -64465,7 +64465,7 @@ "display_args": ["--[no-]pydocstyle-export"], "env_var": "PANTS_PYDOCSTYLE_EXPORT", "fromfile": false, - "help": "If true, export a virtual environment with Pydocstyle when running `scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with Pydocstyle when running `pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": "Use the export goal's --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": [ @@ -64736,7 +64736,7 @@ "display_args": ["--[no-]pylint-skip"], "env_var": "PANTS_PYLINT_SKIP", "fromfile": false, - "help": "If true, don't use Pylint when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Pylint when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pylint-skip", "--no-pylint-skip"], @@ -64872,7 +64872,7 @@ "display_args": ["--pylint-lockfile="], "env_var": "PANTS_PYLINT_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/lint/pylint/pylint.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=pylint`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/lint/pylint/pylint.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=pylint`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": "Custom tool versions are now installed from named resolves, as described at https://www.pantsbuild.org/v2.17/docs/python-lockfiles.\n\n1. If you have an existing resolve that includes the requirements for this tool,\n you can set `[pylint].install_from_resolve = \"\".\n This may be the case if the tool also provides a runtime library, and you want\n to specify the version in just one place.\n2. If not, you can set up a new resolve as described at the link above.\n\nEither way, the resolve you choose should provide the requirements currently set by the `version` and `extra-requirements` options for this tool, which you can see by running `pants help-advanced pylint`.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--pylint-lockfile"], @@ -64905,7 +64905,7 @@ "display_args": ["--[no-]pylint-export"], "env_var": "PANTS_PYLINT_EXPORT", "fromfile": false, - "help": "If true, export a virtual environment with Pylint when running `scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with Pylint when running `pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": "Use the export goal's --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--pylint-export", "--no-pylint-export"], @@ -65213,7 +65213,7 @@ "display_args": ["--pyoxidizer-lockfile="], "env_var": "PANTS_PYOXIDIZER_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/packaging/pyoxidizer/pyoxidizer.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=pyoxidizer`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/packaging/pyoxidizer/pyoxidizer.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=pyoxidizer`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": "Custom tool versions are now installed from named resolves, as described at https://www.pantsbuild.org/v2.17/docs/python-lockfiles.\n\n1. If you have an existing resolve that includes the requirements for this tool,\n you can set `[pyoxidizer].install_from_resolve = \"\".\n This may be the case if the tool also provides a runtime library, and you want\n to specify the version in just one place.\n2. If not, you can set up a new resolve as described at the link above.\n\nEither way, the resolve you choose should provide the requirements currently set by the `version` and `extra-requirements` options for this tool, which you can see by running `pants help-advanced pyoxidizer`.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--pyoxidizer-lockfile"], @@ -65579,7 +65579,7 @@ "display_args": ["--[no-]pytest-skip"], "env_var": "PANTS_PYTEST_SKIP", "fromfile": false, - "help": "If true, don't use Pytest when running `scie-pants-linux-x86_64 test`.", + "help": "If true, don't use Pytest when running `pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pytest-skip", "--no-pytest-skip"], @@ -65685,7 +65685,7 @@ "display_args": ["--pytest-lockfile="], "env_var": "PANTS_PYTEST_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/subsystems/pytest.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=pytest`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/subsystems/pytest.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=pytest`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": "Custom tool versions are now installed from named resolves, as described at https://www.pantsbuild.org/v2.17/docs/python-lockfiles.\n\n1. If you have an existing resolve that includes the requirements for this tool,\n you can set `[pytest].install_from_resolve = \"\".\n This may be the case if the tool also provides a runtime library, and you want\n to specify the version in just one place.\n2. If not, you can set up a new resolve as described at the link above.\n\nEither way, the resolve you choose should provide the requirements currently set by the `version` and `extra-requirements` options for this tool, which you can see by running `pants help-advanced pytest`.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--pytest-lockfile"], @@ -65718,7 +65718,7 @@ "display_args": ["--[no-]pytest-export"], "env_var": "PANTS_PYTEST_EXPORT", "fromfile": false, - "help": "If true, export a virtual environment with Pytest when running `scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with Pytest when running `pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": "Use the export goal's --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--pytest-export", "--no-pytest-export"], @@ -65893,7 +65893,7 @@ ], "env_var": "PANTS_PYTHON_RESOLVES", "fromfile": false, - "help": "A mapping of logical names to lockfile paths used in your project.\n\nMany organizations only need a single resolve for their whole project, which is a good default and often the simplest thing to do. However, you may need multiple resolves, such as if you use two conflicting versions of a requirement in your repository.\n\nIf you only need a single resolve, run `scie-pants-linux-x86_64 generate-lockfiles` to generate the lockfile.\n\nIf you need multiple resolves:\n\n 1. Via this option, define multiple resolve names and their lockfile paths. The names should be meaningful to your repository, such as `data-science` or `pants-plugins`.\n 2. Set the default with `[python].default_resolve`.\n 3. Update your `python_requirement` targets with the `resolve` field to declare which resolve they should be available in. They default to `[python].default_resolve`, so you only need to update targets that you want in non-default resolves. (Often you'll set this via the `python_requirements` or `poetry_requirements` target generators)\n 4. Run `scie-pants-linux-x86_64 generate-lockfiles` to generate the lockfiles. If the results aren't what you'd expect, adjust the prior step.\n 5. Update any targets like `python_source` / `python_sources`, `python_test` / `python_tests`, and `pex_binary` which need to set a non-default resolve with the `resolve` field.\n\nIf a target can work with multiple resolves, you can either use the `parametrize` mechanism or manually create a distinct target per resolve. See https://www.pantsbuild.org/v2.17/docs/targets for information about `parametrize`.\n\nFor example:\n\n python_sources(\n resolve=parametrize(\"data-science\", \"web-app\"),\n )\n\nYou can name the lockfile paths what you would like; Pants does not expect a certain file extension or location.\n\nOnly applies if `[python].enable_resolves` is true.", + "help": "A mapping of logical names to lockfile paths used in your project.\n\nMany organizations only need a single resolve for their whole project, which is a good default and often the simplest thing to do. However, you may need multiple resolves, such as if you use two conflicting versions of a requirement in your repository.\n\nIf you only need a single resolve, run `pants generate-lockfiles` to generate the lockfile.\n\nIf you need multiple resolves:\n\n 1. Via this option, define multiple resolve names and their lockfile paths. The names should be meaningful to your repository, such as `data-science` or `pants-plugins`.\n 2. Set the default with `[python].default_resolve`.\n 3. Update your `python_requirement` targets with the `resolve` field to declare which resolve they should be available in. They default to `[python].default_resolve`, so you only need to update targets that you want in non-default resolves. (Often you'll set this via the `python_requirements` or `poetry_requirements` target generators)\n 4. Run `pants generate-lockfiles` to generate the lockfiles. If the results aren't what you'd expect, adjust the prior step.\n 5. Update any targets like `python_source` / `python_sources`, `python_test` / `python_tests`, and `pex_binary` which need to set a non-default resolve with the `resolve` field.\n\nIf a target can work with multiple resolves, you can either use the `parametrize` mechanism or manually create a distinct target per resolve. See https://www.pantsbuild.org/v2.17/docs/targets for information about `parametrize`.\n\nFor example:\n\n python_sources(\n resolve=parametrize(\"data-science\", \"web-app\"),\n )\n\nYou can name the lockfile paths what you would like; Pants does not expect a certain file extension or location.\n\nOnly applies if `[python].enable_resolves` is true.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--python-resolves"], @@ -66646,7 +66646,7 @@ "env_var": "PANTS_PYTHON_REQUIREMENT_CONSTRAINTS", "fromfile": false, "help": "When resolving third-party requirements for your own code (vs. tools you run), use this constraints file to determine which versions to use.\n\nMutually exclusive with `[python].enable_resolves`, which we generally recommend as an improvement over constraints file.\n\nSee https://pip.pypa.io/en/stable/user_guide/#constraints-files for more information on the format of constraint files and how constraints are applied in Pex and pip.\n\nThis only applies when resolving user requirements, rather than tools you run like Black and Pytest. To constrain tools, set `[tool].lockfile`, e.g. `[black].lockfile`.", - "removal_hint": "We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.\n\nTo migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `scie-pants-linux-x86_64 generate-lockfiles`.", + "removal_hint": "We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.\n\nTo migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `pants generate-lockfiles`.", "removal_version": "3.0.0.dev0", "scoped_cmd_line_args": ["--python-requirement-constraints"], "target_field_name": null, @@ -66674,7 +66674,7 @@ "env_var": "PANTS_PYTHON_RESOLVE_ALL_CONSTRAINTS", "fromfile": false, "help": "(Only relevant when using `[python].requirement_constraints.`) If enabled, when resolving requirements, Pants will first resolve your entire constraints file as a single global resolve. Then, if the code uses a subset of your constraints file, Pants will extract the relevant requirements from that global resolve so that only what's actually needed gets used. If disabled, Pants will not use a global resolve and will resolve each subset of your requirements independently.\n\nUsually this option should be enabled because it can result in far fewer resolves.", - "removal_hint": "We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.\n\nTo migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `scie-pants-linux-x86_64 generate-lockfiles`.", + "removal_hint": "We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.\n\nTo migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `pants generate-lockfiles`.", "removal_version": "3.0.0.dev0", "scoped_cmd_line_args": [ "--python-resolve-all-constraints", @@ -67104,7 +67104,7 @@ "display_args": ["--python-infer-init-files="], "env_var": "PANTS_PYTHON_INFER_INIT_FILES", "fromfile": false, - "help": "Infer a target's dependencies on any `__init__.py` files in the packages it is located in (recursively upward in the directory structure).\n\nEven if this is set to `never` or `content_only`, Pants will still always include any ancestor `__init__.py` files in the sandbox. Only, they will not be \"proper\" dependencies, e.g. they will not show up in `scie-pants-linux-x86_64 dependencies` and their own dependencies will not be used.\n\nBy default, Pants only adds a \"proper\" dependency if there is content in the `__init__.py` file. This makes sure that dependencies are added when likely necessary to build, while also avoiding adding unnecessary dependencies. While accurate, those unnecessary dependencies can complicate setting metadata like the `interpreter_constraints` and `resolve` fields.", + "help": "Infer a target's dependencies on any `__init__.py` files in the packages it is located in (recursively upward in the directory structure).\n\nEven if this is set to `never` or `content_only`, Pants will still always include any ancestor `__init__.py` files in the sandbox. Only, they will not be \"proper\" dependencies, e.g. they will not show up in `pants dependencies` and their own dependencies will not be used.\n\nBy default, Pants only adds a \"proper\" dependency if there is content in the `__init__.py` file. This makes sure that dependencies are added when likely necessary to build, while also avoiding adding unnecessary dependencies. While accurate, those unnecessary dependencies can complicate setting metadata like the `interpreter_constraints` and `resolve` fields.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--python-infer-init-files"], @@ -67316,7 +67316,7 @@ "display_args": ["--[no-]python-infer-use-rust-parser"], "env_var": "PANTS_PYTHON_INFER_USE_RUST_PARSER", "fromfile": false, - "help": "Use the new Rust-based, multithreaded, in-process dependency parser.\n\nPants 2.17 introduced a new paradigm to dependency parsing for Python by leveraging a Rust-based parser that's called in the same process as Pants itself, instead of farming out to one-python-process-per-file.\n\nAs a result of the switch, cold-cache performance improved by a factor of about 12x, while hot-cache had no difference. Additionally, Pants can now infer dependencies from Python scripts with syntax errors.\n\nHowever, since this parser is completely different it has the potential of introducing differences in dependency inference. Although the Pants suite of tests only identified differences when using the `# pants: no-infer-dep` pragma, and string-based imports/assets, Out of an abundance of caution, this is behind a feature flag that will eventually be on-by-default then removed.\n\nIt is recommended that you run `scie-pants-linux-x86_64 peek :: > before.json` and then `scie-pants-linux-x86_64 --python-infer-use-rust-parser peek :: > after.json` and compare the two results. If all looks good, set `use_rust_parser` in `[python-infer]` in `pants.toml`. If you think there's a bug please file an issue: https://github.com/pantsbuild/pants/issues/new/choose.", + "help": "Use the new Rust-based, multithreaded, in-process dependency parser.\n\nPants 2.17 introduced a new paradigm to dependency parsing for Python by leveraging a Rust-based parser that's called in the same process as Pants itself, instead of farming out to one-python-process-per-file.\n\nAs a result of the switch, cold-cache performance improved by a factor of about 12x, while hot-cache had no difference. Additionally, Pants can now infer dependencies from Python scripts with syntax errors.\n\nHowever, since this parser is completely different it has the potential of introducing differences in dependency inference. Although the Pants suite of tests only identified differences when using the `# pants: no-infer-dep` pragma, and string-based imports/assets, Out of an abundance of caution, this is behind a feature flag that will eventually be on-by-default then removed.\n\nIt is recommended that you run `pants peek :: > before.json` and then `pants --python-infer-use-rust-parser peek :: > after.json` and compare the two results. If all looks good, set `use_rust_parser` in `[python-infer]` in `pants.toml`. If you think there's a bug please file an issue: https://github.com/pantsbuild/pants/issues/new/choose.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -67931,7 +67931,7 @@ "display_args": ["--[no-]pyupgrade-skip"], "env_var": "PANTS_PYUPGRADE_SKIP", "fromfile": false, - "help": "If true, don't use pyupgrade when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use pyupgrade when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pyupgrade-skip", "--no-pyupgrade-skip"], @@ -68069,7 +68069,7 @@ "display_args": ["--pyupgrade-lockfile="], "env_var": "PANTS_PYUPGRADE_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/lint/pyupgrade/pyupgrade.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=pyupgrade`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/lint/pyupgrade/pyupgrade.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=pyupgrade`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": "Custom tool versions are now installed from named resolves, as described at https://www.pantsbuild.org/v2.17/docs/python-lockfiles.\n\n1. If you have an existing resolve that includes the requirements for this tool,\n you can set `[pyupgrade].install_from_resolve = \"\".\n This may be the case if the tool also provides a runtime library, and you want\n to specify the version in just one place.\n2. If not, you can set up a new resolve as described at the link above.\n\nEither way, the resolve you choose should provide the requirements currently set by the `version` and `extra-requirements` options for this tool, which you can see by running `pants help-advanced pyupgrade`.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--pyupgrade-lockfile"], @@ -68102,7 +68102,7 @@ "display_args": ["--[no-]pyupgrade-export"], "env_var": "PANTS_PYUPGRADE_EXPORT", "fromfile": false, - "help": "If true, export a virtual environment with pyupgrade when running `scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with pyupgrade when running `pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": "Use the export goal's --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": [ @@ -68148,7 +68148,7 @@ "display_args": ["--[no-]regex-lint-skip"], "env_var": "PANTS_REGEX_LINT_SKIP", "fromfile": false, - "help": "If true, don't use regex-lint when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use regex-lint when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--regex-lint-skip", "--no-regex-lint-skip"], @@ -68632,7 +68632,7 @@ "display_args": ["--[no-]ruff-skip"], "env_var": "PANTS_RUFF_SKIP", "fromfile": false, - "help": "If true, don't use Ruff when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Ruff when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--ruff-skip", "--no-ruff-skip"], @@ -68768,7 +68768,7 @@ "display_args": ["--ruff-lockfile="], "env_var": "PANTS_RUFF_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/lint/ruff/ruff.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=ruff`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/lint/ruff/ruff.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=ruff`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": "Custom tool versions are now installed from named resolves, as described at https://www.pantsbuild.org/v2.17/docs/python-lockfiles.\n\n1. If you have an existing resolve that includes the requirements for this tool,\n you can set `[ruff].install_from_resolve = \"\".\n This may be the case if the tool also provides a runtime library, and you want\n to specify the version in just one place.\n2. If not, you can set up a new resolve as described at the link above.\n\nEither way, the resolve you choose should provide the requirements currently set by the `version` and `extra-requirements` options for this tool, which you can see by running `pants help-advanced ruff`.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--ruff-lockfile"], @@ -68801,7 +68801,7 @@ "display_args": ["--[no-]ruff-export"], "env_var": "PANTS_RUFF_EXPORT", "fromfile": false, - "help": "If true, export a virtual environment with Ruff when running `scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with Ruff when running `pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": "Use the export goal's --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--ruff-export", "--no-ruff-export"], @@ -69320,7 +69320,7 @@ "display_args": ["--scalafmt-lockfile="], "env_var": "PANTS_SCALAFMT_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/scala/lint/scalafmt/scalafmt.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalafmt`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/scala/lint/scalafmt/scalafmt.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=scalafmt`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalafmt-lockfile"], @@ -69390,7 +69390,7 @@ "display_args": ["--[no-]scalafmt-skip"], "env_var": "PANTS_SCALAFMT_SKIP", "fromfile": false, - "help": "If true, don't use scalafmt when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use scalafmt when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalafmt-skip", "--no-scalafmt-skip"], @@ -69499,7 +69499,7 @@ "display_args": ["--scalapb-lockfile="], "env_var": "PANTS_SCALAPB_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/codegen/protobuf/scala/scalapbc.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalapb`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/codegen/protobuf/scala/scalapbc.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=scalapb`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalapb-lockfile"], @@ -69676,7 +69676,7 @@ "display_args": ["--scalatest-lockfile="], "env_var": "PANTS_SCALATEST_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/scala/subsystems/scalatest.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalatest`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/scala/subsystems/scalatest.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=scalatest`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalatest-lockfile"], @@ -69782,7 +69782,7 @@ "display_args": ["--[no-]scalatest-skip"], "env_var": "PANTS_SCALATEST_SKIP", "fromfile": false, - "help": "If true, don't use Scalatest when running `scie-pants-linux-x86_64 test`.", + "help": "If true, don't use Scalatest when running `pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalatest-skip", "--no-scalatest-skip"], @@ -70283,7 +70283,7 @@ "display_args": ["--setuptools-lockfile="], "env_var": "PANTS_SETUPTOOLS_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/subsystems/setuptools.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=setuptools`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/subsystems/setuptools.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=setuptools`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": "Custom tool versions are now installed from named resolves, as described at https://www.pantsbuild.org/v2.17/docs/python-lockfiles.\n\n1. If you have an existing resolve that includes the requirements for this tool,\n you can set `[setuptools].install_from_resolve = \"\".\n This may be the case if the tool also provides a runtime library, and you want\n to specify the version in just one place.\n2. If not, you can set up a new resolve as described at the link above.\n\nEither way, the resolve you choose should provide the requirements currently set by the `version` and `extra-requirements` options for this tool, which you can see by running `pants help-advanced setuptools`.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--setuptools-lockfile"], @@ -70555,7 +70555,7 @@ "display_args": ["--setuptools-scm-lockfile="], "env_var": "PANTS_SETUPTOOLS_SCM_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/subsystems/setuptools_scm.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=setuptools-scm`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/subsystems/setuptools_scm.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=setuptools-scm`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": "Custom tool versions are now installed from named resolves, as described at https://www.pantsbuild.org/v2.17/docs/python-lockfiles.\n\n1. If you have an existing resolve that includes the requirements for this tool,\n you can set `[setuptools-scm].install_from_resolve = \"\".\n This may be the case if the tool also provides a runtime library, and you want\n to specify the version in just one place.\n2. If not, you can set up a new resolve as described at the link above.\n\nEither way, the resolve you choose should provide the requirements currently set by the `version` and `extra-requirements` options for this tool, which you can see by running `pants help-advanced setuptools-scm`.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--setuptools-scm-lockfile"], @@ -70719,7 +70719,7 @@ "display_args": ["--[no-]shell-test-skip"], "env_var": "PANTS_SHELL_TEST_SKIP", "fromfile": false, - "help": "If true, don't use Test with shell scripts when running `scie-pants-linux-x86_64 test`.", + "help": "If true, don't use Test with shell scripts when running `pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--shell-test-skip", "--no-shell-test-skip"], @@ -70994,7 +70994,7 @@ "display_args": ["--[no-]shellcheck-skip"], "env_var": "PANTS_SHELLCHECK_SKIP", "fromfile": false, - "help": "If true, don't use Shellcheck when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Shellcheck when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--shellcheck-skip", "--no-shellcheck-skip"], @@ -71312,7 +71312,7 @@ "display_args": ["--[no-]shfmt-skip"], "env_var": "PANTS_SHFMT_SKIP", "fromfile": false, - "help": "If true, don't use shfmt when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use shfmt when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--shfmt-skip", "--no-shfmt-skip"], @@ -71566,7 +71566,7 @@ "display_args": ["--[no-]shunit2-skip"], "env_var": "PANTS_SHUNIT2_SKIP", "fromfile": false, - "help": "If true, don't use shunit2 when running `scie-pants-linux-x86_64 test`.", + "help": "If true, don't use shunit2 when running `pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--shunit2-skip", "--no-shunit2-skip"], @@ -71745,7 +71745,7 @@ "display_args": ["--[no-]spectral-skip"], "env_var": "PANTS_SPECTRAL_SKIP", "fromfile": false, - "help": "If true, don't use Spectral when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Spectral when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--spectral-skip", "--no-spectral-skip"], @@ -72204,7 +72204,7 @@ "display_args": ["--[no-]terraform-fmt-skip"], "env_var": "PANTS_TERRAFORM_FMT_SKIP", "fromfile": false, - "help": "If true, don't use `terraform fmt` when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use `terraform fmt` when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -72427,7 +72427,7 @@ "display_args": ["--terraform-hcl2-parser-lockfile="], "env_var": "PANTS_TERRAFORM_HCL2_PARSER_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/terraform/hcl2.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=terraform-hcl2-parser`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/terraform/hcl2.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=terraform-hcl2-parser`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": "Custom tool versions are now installed from named resolves, as described at https://www.pantsbuild.org/v2.17/docs/python-lockfiles.\n\n1. If you have an existing resolve that includes the requirements for this tool,\n you can set `[terraform-hcl2-parser].install_from_resolve = \"\".\n This may be the case if the tool also provides a runtime library, and you want\n to specify the version in just one place.\n2. If not, you can set up a new resolve as described at the link above.\n\nEither way, the resolve you choose should provide the requirements currently set by the `version` and `extra-requirements` options for this tool, which you can see by running `pants help-advanced terraform-hcl2-parser`.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--terraform-hcl2-parser-lockfile"], @@ -72470,7 +72470,7 @@ "display_args": ["--[no-]terraform-validate-skip"], "env_var": "PANTS_TERRAFORM_VALIDATE_SKIP", "fromfile": false, - "help": "If true, don't use `terraform validate` when running `scie-pants-linux-x86_64 check`.", + "help": "If true, don't use `terraform validate` when running `pants check`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -73332,7 +73332,7 @@ "display_args": ["--[no-]twine-skip"], "env_var": "PANTS_TWINE_SKIP", "fromfile": false, - "help": "If true, don't use Twine when running `scie-pants-linux-x86_64 publish`.", + "help": "If true, don't use Twine when running `pants publish`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--twine-skip", "--no-twine-skip"], @@ -73468,7 +73468,7 @@ "display_args": ["--twine-lockfile="], "env_var": "PANTS_TWINE_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/subsystems/twine.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=twine`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/subsystems/twine.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=twine`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": "Custom tool versions are now installed from named resolves, as described at https://www.pantsbuild.org/v2.17/docs/python-lockfiles.\n\n1. If you have an existing resolve that includes the requirements for this tool,\n you can set `[twine].install_from_resolve = \"\".\n This may be the case if the tool also provides a runtime library, and you want\n to specify the version in just one place.\n2. If not, you can set up a new resolve as described at the link above.\n\nEither way, the resolve you choose should provide the requirements currently set by the `version` and `extra-requirements` options for this tool, which you can see by running `pants help-advanced twine`.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--twine-lockfile"], @@ -74050,7 +74050,7 @@ "display_args": ["--[no-]yamllint-skip"], "env_var": "PANTS_YAMLLINT_SKIP", "fromfile": false, - "help": "If true, don't use Yamllint when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Yamllint when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--yamllint-skip", "--no-yamllint-skip"], @@ -74153,7 +74153,7 @@ "display_args": ["--yamllint-lockfile="], "env_var": "PANTS_YAMLLINT_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/tools/yamllint/yamllint.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=yamllint`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/tools/yamllint/yamllint.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=yamllint`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": "Custom tool versions are now installed from named resolves, as described at https://www.pantsbuild.org/v2.17/docs/python-lockfiles.\n\n1. If you have an existing resolve that includes the requirements for this tool,\n you can set `[yamllint].install_from_resolve = \"\".\n This may be the case if the tool also provides a runtime library, and you want\n to specify the version in just one place.\n2. If not, you can set up a new resolve as described at the link above.\n\nEither way, the resolve you choose should provide the requirements currently set by the `version` and `extra-requirements` options for this tool, which you can see by running `pants help-advanced yamllint`.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--yamllint-lockfile"], @@ -74186,7 +74186,7 @@ "display_args": ["--[no-]yamllint-export"], "env_var": "PANTS_YAMLLINT_EXPORT", "fromfile": false, - "help": "If true, export a virtual environment with Yamllint when running `scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with Yamllint when running `pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": "Use the export goal's --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--yamllint-export", "--no-yamllint-export"], @@ -74454,7 +74454,7 @@ "display_args": ["--[no-]yapf-skip"], "env_var": "PANTS_YAPF_SKIP", "fromfile": false, - "help": "If true, don't use yapf when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use yapf when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--yapf-skip", "--no-yapf-skip"], @@ -74590,7 +74590,7 @@ "display_args": ["--yapf-lockfile="], "env_var": "PANTS_YAPF_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/lint/yapf/yapf.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=yapf`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/lint/yapf/yapf.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=yapf`.\n\nAlternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers.", "removal_hint": "Custom tool versions are now installed from named resolves, as described at https://www.pantsbuild.org/v2.17/docs/python-lockfiles.\n\n1. If you have an existing resolve that includes the requirements for this tool,\n you can set `[yapf].install_from_resolve = \"\".\n This may be the case if the tool also provides a runtime library, and you want\n to specify the version in just one place.\n2. If not, you can set up a new resolve as described at the link above.\n\nEither way, the resolve you choose should provide the requirements currently set by the `version` and `extra-requirements` options for this tool, which you can see by running `pants help-advanced yapf`.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--yapf-lockfile"], @@ -74623,7 +74623,7 @@ "display_args": ["--[no-]yapf-export"], "env_var": "PANTS_YAPF_EXPORT", "fromfile": false, - "help": "If true, export a virtual environment with yapf when running `scie-pants-linux-x86_64 export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", + "help": "If true, export a virtual environment with yapf when running `pants export`.\n\nThis can be useful, for example, with IDE integrations to point your editor to the tool's binary.", "removal_hint": "Use the export goal's --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.", "removal_version": "2.18.0.dev0", "scoped_cmd_line_args": ["--yapf-export", "--no-yapf-export"], diff --git a/versioned_docs/version-2.17/reference/subsystems/add-trailing-comma.mdx b/versioned_docs/version-2.17/reference/subsystems/add-trailing-comma.mdx index a37c8f7ab..90297f2d0 100644 --- a/versioned_docs/version-2.17/reference/subsystems/add-trailing-comma.mdx +++ b/versioned_docs/version-2.17/reference/subsystems/add-trailing-comma.mdx @@ -25,7 +25,7 @@ Config section: `[add-trailing-comma]` default_repr={`False`} > -If true, don't use add-trailing-comma when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use add-trailing-comma when running `pants fmt` and `pants lint`. @@ -161,7 +161,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/lint/add_trailing_comma/add_trailing_comma.lock for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=add-trailing-comma`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=add-trailing-comma`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. @@ -177,7 +177,7 @@ Alternatively, you can set this option to the path to a custom lockfile using pi removal_hint={'Use the export goal\'s --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.'} > -If true, export a virtual environment with add-trailing-comma when running `scie-pants-linux-x86_64 export`. +If true, export a virtual environment with add-trailing-comma when running `pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. diff --git a/versioned_docs/version-2.17/reference/subsystems/autoflake.mdx b/versioned_docs/version-2.17/reference/subsystems/autoflake.mdx index e9c7e5687..636aeb66f 100644 --- a/versioned_docs/version-2.17/reference/subsystems/autoflake.mdx +++ b/versioned_docs/version-2.17/reference/subsystems/autoflake.mdx @@ -25,7 +25,7 @@ Config section: `[autoflake]` default_repr={`False`} > -If true, don't use Autoflake when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use Autoflake when running `pants fmt` and `pants lint`. @@ -161,7 +161,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/lint/autoflake/autoflake.lock for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=autoflake`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=autoflake`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. @@ -177,7 +177,7 @@ Alternatively, you can set this option to the path to a custom lockfile using pi removal_hint={'Use the export goal\'s --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.'} > -If true, export a virtual environment with Autoflake when running `scie-pants-linux-x86_64 export`. +If true, export a virtual environment with Autoflake when running `pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. diff --git a/versioned_docs/version-2.17/reference/subsystems/bandit.mdx b/versioned_docs/version-2.17/reference/subsystems/bandit.mdx index d119ef28e..3ec546661 100644 --- a/versioned_docs/version-2.17/reference/subsystems/bandit.mdx +++ b/versioned_docs/version-2.17/reference/subsystems/bandit.mdx @@ -25,7 +25,7 @@ Config section: `[bandit]` default_repr={`False`} > -If true, don't use Bandit when running `scie-pants-linux-x86_64 lint`. +If true, don't use Bandit when running `pants lint`. @@ -161,7 +161,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/lint/bandit/bandit.lock for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=bandit`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=bandit`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. @@ -177,7 +177,7 @@ Alternatively, you can set this option to the path to a custom lockfile using pi removal_hint={'Use the export goal\'s --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.'} > -If true, export a virtual environment with Bandit when running `scie-pants-linux-x86_64 export`. +If true, export a virtual environment with Bandit when running `pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. diff --git a/versioned_docs/version-2.17/reference/subsystems/black.mdx b/versioned_docs/version-2.17/reference/subsystems/black.mdx index a641d60d1..cd7135c24 100644 --- a/versioned_docs/version-2.17/reference/subsystems/black.mdx +++ b/versioned_docs/version-2.17/reference/subsystems/black.mdx @@ -25,7 +25,7 @@ Config section: `[black]` default_repr={`False`} > -If true, don't use Black when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use Black when running `pants fmt` and `pants lint`. @@ -189,7 +189,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/lint/black/black.lock for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=black`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=black`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. @@ -205,7 +205,7 @@ Alternatively, you can set this option to the path to a custom lockfile using pi removal_hint={'Use the export goal\'s --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.'} > -If true, export a virtual environment with Black when running `scie-pants-linux-x86_64 export`. +If true, export a virtual environment with Black when running `pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. diff --git a/versioned_docs/version-2.17/reference/subsystems/buf.mdx b/versioned_docs/version-2.17/reference/subsystems/buf.mdx index 8189bdf18..2254c4dfa 100644 --- a/versioned_docs/version-2.17/reference/subsystems/buf.mdx +++ b/versioned_docs/version-2.17/reference/subsystems/buf.mdx @@ -25,7 +25,7 @@ Config section: `[buf]` default_repr={`False`} > -If true, don't use Buf when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use Buf when running `pants fmt` and `pants lint`. @@ -37,7 +37,7 @@ If true, don't use Buf when running `scie-pants-linux-x86_64 fmt` and `scie default_repr={`False`} > -If true, don't use Buf when running `scie-pants-linux-x86_64 lint`. +If true, don't use Buf when running `pants lint`. diff --git a/versioned_docs/version-2.17/reference/subsystems/build-deprecations-fixer.mdx b/versioned_docs/version-2.17/reference/subsystems/build-deprecations-fixer.mdx index b3a4e372b..8fa169ffe 100644 --- a/versioned_docs/version-2.17/reference/subsystems/build-deprecations-fixer.mdx +++ b/versioned_docs/version-2.17/reference/subsystems/build-deprecations-fixer.mdx @@ -27,7 +27,7 @@ Config section: `[build-deprecations-fixer]` -If true, don't use BUILD Deprecations Fixer when running `scie-pants-linux-x86_64 fix`. +If true, don't use BUILD Deprecations Fixer when running `pants fix`. diff --git a/versioned_docs/version-2.17/reference/subsystems/buildifier.mdx b/versioned_docs/version-2.17/reference/subsystems/buildifier.mdx index 22b9e9944..25508a035 100644 --- a/versioned_docs/version-2.17/reference/subsystems/buildifier.mdx +++ b/versioned_docs/version-2.17/reference/subsystems/buildifier.mdx @@ -32,7 +32,7 @@ Config section: `[buildifier]` default_repr={`False`} > -If true, don't use Buildifier when running `scie-pants-linux-x86_64 fmt`. +If true, don't use Buildifier when running `pants fmt`. diff --git a/versioned_docs/version-2.17/reference/subsystems/cli.mdx b/versioned_docs/version-2.17/reference/subsystems/cli.mdx index c73472624..e471cf70f 100644 --- a/versioned_docs/version-2.17/reference/subsystems/cli.mdx +++ b/versioned_docs/version-2.17/reference/subsystems/cli.mdx @@ -35,7 +35,7 @@ green = "fmt lint check" all-changed = "--changed-since=HEAD --changed-dependents=transitive" ``` -This would allow you to run `scie-pants-linux-x86_64 green all-changed`, which is shorthand for `scie-pants-linux-x86_64 fmt lint check --changed-since=HEAD --changed-dependents=transitive`. +This would allow you to run `pants green all-changed`, which is shorthand for `pants fmt lint check --changed-since=HEAD --changed-dependents=transitive`. Notice: this option must be placed in a config file (e.g. `pants.toml` or `pantsrc`) to have any effect. diff --git a/versioned_docs/version-2.17/reference/subsystems/coverage-py.mdx b/versioned_docs/version-2.17/reference/subsystems/coverage-py.mdx index e0e1a3d9e..746a22b18 100644 --- a/versioned_docs/version-2.17/reference/subsystems/coverage-py.mdx +++ b/versioned_docs/version-2.17/reference/subsystems/coverage-py.mdx @@ -238,7 +238,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/subsystems/coverage_py.lock for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=coverage-py`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=coverage-py`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.17/reference/subsystems/debugpy.mdx b/versioned_docs/version-2.17/reference/subsystems/debugpy.mdx index 06dc8121b..13aa2edb9 100644 --- a/versioned_docs/version-2.17/reference/subsystems/debugpy.mdx +++ b/versioned_docs/version-2.17/reference/subsystems/debugpy.mdx @@ -149,7 +149,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/subsystems/debugpy.lock for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=debugpy`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=debugpy`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.17/reference/subsystems/docformatter.mdx b/versioned_docs/version-2.17/reference/subsystems/docformatter.mdx index d7813f294..f4777a274 100644 --- a/versioned_docs/version-2.17/reference/subsystems/docformatter.mdx +++ b/versioned_docs/version-2.17/reference/subsystems/docformatter.mdx @@ -25,7 +25,7 @@ Config section: `[docformatter]` default_repr={`False`} > -If true, don't use docformatter when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use docformatter when running `pants fmt` and `pants lint`. @@ -161,7 +161,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/lint/docformatter/docformatter.lock for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=docformatter`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=docformatter`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. @@ -177,7 +177,7 @@ Alternatively, you can set this option to the path to a custom lockfile using pi removal_hint={'Use the export goal\'s --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.'} > -If true, export a virtual environment with docformatter when running `scie-pants-linux-x86_64 export`. +If true, export a virtual environment with docformatter when running `pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. diff --git a/versioned_docs/version-2.17/reference/subsystems/docker.mdx b/versioned_docs/version-2.17/reference/subsystems/docker.mdx index b1561d53d..497243eda 100644 --- a/versioned_docs/version-2.17/reference/subsystems/docker.mdx +++ b/versioned_docs/version-2.17/reference/subsystems/docker.mdx @@ -169,7 +169,7 @@ Additional arguments to use for `docker run` invocations. Example: ``` -$ scie-pants-linux-x86_64 run --docker-run-args="-p 127.0.0.1:80:8080/tcp --name demo" src/example:image -- [image entrypoint args] +$ pants run --docker-run-args="-p 127.0.0.1:80:8080/tcp --name demo" src/example:image -- [image entrypoint args] ``` To provide the top-level options to the `docker` client, use `[docker].env_vars` to configure the [Environment variables](https://docs.docker.com/engine/reference/commandline/cli/#environment-variables) as appropriate. diff --git a/versioned_docs/version-2.17/reference/subsystems/dockerfile-parser.mdx b/versioned_docs/version-2.17/reference/subsystems/dockerfile-parser.mdx index 6bdd6e51d..ff6d52f5a 100644 --- a/versioned_docs/version-2.17/reference/subsystems/dockerfile-parser.mdx +++ b/versioned_docs/version-2.17/reference/subsystems/dockerfile-parser.mdx @@ -115,7 +115,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/docker/subsystems/dockerfile.lock for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=dockerfile-parser`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=dockerfile-parser`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.17/reference/subsystems/flake8.mdx b/versioned_docs/version-2.17/reference/subsystems/flake8.mdx index fd13cadd2..0ed3f1c1a 100644 --- a/versioned_docs/version-2.17/reference/subsystems/flake8.mdx +++ b/versioned_docs/version-2.17/reference/subsystems/flake8.mdx @@ -25,7 +25,7 @@ Config section: `[flake8]` default_repr={`False`} > -If true, don't use Flake8 when running `scie-pants-linux-x86_64 lint`. +If true, don't use Flake8 when running `pants lint`. @@ -220,7 +220,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/lint/flake8/flake8.lock for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=flake8`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=flake8`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. @@ -236,7 +236,7 @@ Alternatively, you can set this option to the path to a custom lockfile using pi removal_hint={'Use the export goal\'s --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.'} > -If true, export a virtual environment with Flake8 when running `scie-pants-linux-x86_64 export`. +If true, export a virtual environment with Flake8 when running `pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. diff --git a/versioned_docs/version-2.17/reference/subsystems/go-test.mdx b/versioned_docs/version-2.17/reference/subsystems/go-test.mdx index ed16475ac..feb2073e9 100644 --- a/versioned_docs/version-2.17/reference/subsystems/go-test.mdx +++ b/versioned_docs/version-2.17/reference/subsystems/go-test.mdx @@ -90,7 +90,7 @@ This option is similar to the `go test -coverpkg` option, but without support cu default_repr={`False`} > -If true, don't use Go test binary when running `scie-pants-linux-x86_64 test`. +If true, don't use Go test binary when running `pants test`. diff --git a/versioned_docs/version-2.17/reference/subsystems/gofmt.mdx b/versioned_docs/version-2.17/reference/subsystems/gofmt.mdx index 0e737213e..b4fad02eb 100644 --- a/versioned_docs/version-2.17/reference/subsystems/gofmt.mdx +++ b/versioned_docs/version-2.17/reference/subsystems/gofmt.mdx @@ -25,7 +25,7 @@ Config section: `[gofmt]` default_repr={`False`} > -If true, don't use gofmt when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use gofmt when running `pants fmt` and `pants lint`. diff --git a/versioned_docs/version-2.17/reference/subsystems/google-java-format.mdx b/versioned_docs/version-2.17/reference/subsystems/google-java-format.mdx index 221e3d1ef..5c8c5347b 100644 --- a/versioned_docs/version-2.17/reference/subsystems/google-java-format.mdx +++ b/versioned_docs/version-2.17/reference/subsystems/google-java-format.mdx @@ -25,7 +25,7 @@ Config section: `[google-java-format]` default_repr={`False`} > -If true, don't use Google Java Format when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use Google Java Format when running `pants fmt` and `pants lint`. @@ -79,7 +79,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/java/lint/google_java_format/google_java_format.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=google-java-format`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=google-java-format`. diff --git a/versioned_docs/version-2.17/reference/subsystems/hadolint.mdx b/versioned_docs/version-2.17/reference/subsystems/hadolint.mdx index 66ec965bc..4d25b65be 100644 --- a/versioned_docs/version-2.17/reference/subsystems/hadolint.mdx +++ b/versioned_docs/version-2.17/reference/subsystems/hadolint.mdx @@ -25,7 +25,7 @@ Config section: `[hadolint]` default_repr={`False`} > -If true, don't use Hadolint when running `scie-pants-linux-x86_64 lint`. +If true, don't use Hadolint when running `pants lint`. diff --git a/versioned_docs/version-2.17/reference/subsystems/helm-k8s-parser.mdx b/versioned_docs/version-2.17/reference/subsystems/helm-k8s-parser.mdx index 10296fc90..27420fdab 100644 --- a/versioned_docs/version-2.17/reference/subsystems/helm-k8s-parser.mdx +++ b/versioned_docs/version-2.17/reference/subsystems/helm-k8s-parser.mdx @@ -115,7 +115,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/helm/subsystems/k8s_parser.lock for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=helm-k8s-parser`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=helm-k8s-parser`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.17/reference/subsystems/helm-post-renderer.mdx b/versioned_docs/version-2.17/reference/subsystems/helm-post-renderer.mdx index c3bcf1e1a..5a6e338e7 100644 --- a/versioned_docs/version-2.17/reference/subsystems/helm-post-renderer.mdx +++ b/versioned_docs/version-2.17/reference/subsystems/helm-post-renderer.mdx @@ -115,7 +115,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/helm/subsystems/post_renderer.lock for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=helm-post-renderer`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=helm-post-renderer`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.17/reference/subsystems/helm-unittest.mdx b/versioned_docs/version-2.17/reference/subsystems/helm-unittest.mdx index 59db7c73e..e46040795 100644 --- a/versioned_docs/version-2.17/reference/subsystems/helm-unittest.mdx +++ b/versioned_docs/version-2.17/reference/subsystems/helm-unittest.mdx @@ -50,7 +50,7 @@ Output type used for the test report. default_repr={`False`} > -If true, don't use helmunittestsubsystem when running `scie-pants-linux-x86_64 test`. +If true, don't use helmunittestsubsystem when running `pants test`. diff --git a/versioned_docs/version-2.17/reference/subsystems/ipython.mdx b/versioned_docs/version-2.17/reference/subsystems/ipython.mdx index bf48d8edb..f67cb49b3 100644 --- a/versioned_docs/version-2.17/reference/subsystems/ipython.mdx +++ b/versioned_docs/version-2.17/reference/subsystems/ipython.mdx @@ -143,7 +143,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/subsystems/ipython.lock for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=ipython`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=ipython`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.17/reference/subsystems/isort.mdx b/versioned_docs/version-2.17/reference/subsystems/isort.mdx index a3efaad37..2e8eae739 100644 --- a/versioned_docs/version-2.17/reference/subsystems/isort.mdx +++ b/versioned_docs/version-2.17/reference/subsystems/isort.mdx @@ -25,7 +25,7 @@ Config section: `[isort]` default_repr={`False`} > -If true, don't use isort when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use isort when running `pants fmt` and `pants lint`. @@ -191,7 +191,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/lint/isort/isort.lock for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=isort`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=isort`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. @@ -207,7 +207,7 @@ Alternatively, you can set this option to the path to a custom lockfile using pi removal_hint={'Use the export goal\'s --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.'} > -If true, export a virtual environment with isort when running `scie-pants-linux-x86_64 export`. +If true, export a virtual environment with isort when running `pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. diff --git a/versioned_docs/version-2.17/reference/subsystems/jarjar.mdx b/versioned_docs/version-2.17/reference/subsystems/jarjar.mdx index 22deef803..eda1c9327 100644 --- a/versioned_docs/version-2.17/reference/subsystems/jarjar.mdx +++ b/versioned_docs/version-2.17/reference/subsystems/jarjar.mdx @@ -80,7 +80,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/jvm/shading/jarjar.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=jarjar`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=jarjar`. diff --git a/versioned_docs/version-2.17/reference/subsystems/junit.mdx b/versioned_docs/version-2.17/reference/subsystems/junit.mdx index 1d3c6236c..751ed9776 100644 --- a/versioned_docs/version-2.17/reference/subsystems/junit.mdx +++ b/versioned_docs/version-2.17/reference/subsystems/junit.mdx @@ -37,7 +37,7 @@ Arguments to pass directly to JUnit, e.g. `--junit-args='--disable-ansi-colors'` default_repr={`False`} > -If true, don't use JUnit when running `scie-pants-linux-x86_64 test`. +If true, don't use JUnit when running `pants test`. @@ -79,7 +79,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/jvm/test/junit.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=junit`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=junit`. diff --git a/versioned_docs/version-2.17/reference/subsystems/ktlint.mdx b/versioned_docs/version-2.17/reference/subsystems/ktlint.mdx index cbc4a99ac..e5eee095b 100644 --- a/versioned_docs/version-2.17/reference/subsystems/ktlint.mdx +++ b/versioned_docs/version-2.17/reference/subsystems/ktlint.mdx @@ -25,7 +25,7 @@ Config section: `[ktlint]` default_repr={`False`} > -If true, don't use Ktlint when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use Ktlint when running `pants fmt` and `pants lint`. @@ -67,7 +67,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/kotlin/lint/ktlint/ktlint.lock for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=ktlint`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=ktlint`. diff --git a/versioned_docs/version-2.17/reference/subsystems/lambdex.mdx b/versioned_docs/version-2.17/reference/subsystems/lambdex.mdx index dc330ac38..400f8e942 100644 --- a/versioned_docs/version-2.17/reference/subsystems/lambdex.mdx +++ b/versioned_docs/version-2.17/reference/subsystems/lambdex.mdx @@ -150,7 +150,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/subsystems/lambdex.lock for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=lambdex`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=lambdex`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.17/reference/subsystems/mypy-protobuf.mdx b/versioned_docs/version-2.17/reference/subsystems/mypy-protobuf.mdx index 04fd826f2..1a364a5a1 100644 --- a/versioned_docs/version-2.17/reference/subsystems/mypy-protobuf.mdx +++ b/versioned_docs/version-2.17/reference/subsystems/mypy-protobuf.mdx @@ -115,7 +115,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/codegen/protobuf/python/mypy_protobuf.lock for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=mypy-protobuf`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=mypy-protobuf`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.17/reference/subsystems/mypy.mdx b/versioned_docs/version-2.17/reference/subsystems/mypy.mdx index c88f548a2..67a19e7c4 100644 --- a/versioned_docs/version-2.17/reference/subsystems/mypy.mdx +++ b/versioned_docs/version-2.17/reference/subsystems/mypy.mdx @@ -25,7 +25,7 @@ Config section: `[mypy]` default_repr={`False`} > -If true, don't use MyPy when running `scie-pants-linux-x86_64 check`. +If true, don't use MyPy when running `pants check`. @@ -205,7 +205,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/typecheck/mypy/mypy.lock for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=mypy`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=mypy`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. @@ -221,7 +221,7 @@ Alternatively, you can set this option to the path to a custom lockfile using pi removal_hint={'Use the export goal\'s --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.'} > -If true, export a virtual environment with MyPy when running `scie-pants-linux-x86_64 export`. +If true, export a virtual environment with MyPy when running `pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. @@ -263,7 +263,7 @@ Path to a lockfile for the option `[mypy].extra_type_stubs`. Set to the string `` to opt out of using a lockfile. We do not recommend this if you use `[mypy].extra_type_stubs`, though, as lockfiles are essential for reproducible builds and supply-chain security. -To use a lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=mypy-extra-type-stubs`. +To use a lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=mypy-extra-type-stubs`. diff --git a/versioned_docs/version-2.17/reference/subsystems/nodejs.mdx b/versioned_docs/version-2.17/reference/subsystems/nodejs.mdx index d32c6fee5..b67033710 100644 --- a/versioned_docs/version-2.17/reference/subsystems/nodejs.mdx +++ b/versioned_docs/version-2.17/reference/subsystems/nodejs.mdx @@ -134,7 +134,7 @@ Specifying a resolve name is optional. If unspecified, the default resolve name Example: An npm lockfile located at `src/js/package/package-lock.json' will result in a resolve named `js.package`, assuming src/ is a source root. -Run `scie-pants-linux-x86_64 generate-lockfiles` to generate the lockfile(s). +Run `pants generate-lockfiles` to generate the lockfile(s). diff --git a/versioned_docs/version-2.17/reference/subsystems/preamble.mdx b/versioned_docs/version-2.17/reference/subsystems/preamble.mdx index 8a4007fbf..2a12e42f3 100644 --- a/versioned_docs/version-2.17/reference/subsystems/preamble.mdx +++ b/versioned_docs/version-2.17/reference/subsystems/preamble.mdx @@ -29,7 +29,7 @@ Config section: `[preamble]` default_repr={`False`} > -If true, don't use preamble when running `scie-pants-linux-x86_64 fmt`. +If true, don't use preamble when running `pants fmt`. diff --git a/versioned_docs/version-2.17/reference/subsystems/protobuf-java-grpc.mdx b/versioned_docs/version-2.17/reference/subsystems/protobuf-java-grpc.mdx index 6562a0378..65c6dec67 100644 --- a/versioned_docs/version-2.17/reference/subsystems/protobuf-java-grpc.mdx +++ b/versioned_docs/version-2.17/reference/subsystems/protobuf-java-grpc.mdx @@ -57,7 +57,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/codegen/protobuf/java/grpc-java.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=protobuf-java-grpc`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=protobuf-java-grpc`. diff --git a/versioned_docs/version-2.17/reference/subsystems/pydocstyle.mdx b/versioned_docs/version-2.17/reference/subsystems/pydocstyle.mdx index 6ba0d0fdb..2d94e3b55 100644 --- a/versioned_docs/version-2.17/reference/subsystems/pydocstyle.mdx +++ b/versioned_docs/version-2.17/reference/subsystems/pydocstyle.mdx @@ -25,7 +25,7 @@ Config section: `[pydocstyle]` default_repr={`False`} > -If true, don't use Pydocstyle when running `scie-pants-linux-x86_64 lint`. +If true, don't use Pydocstyle when running `pants lint`. @@ -189,7 +189,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/lint/pydocstyle/pydocstyle.lock for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=pydocstyle`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=pydocstyle`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. @@ -205,7 +205,7 @@ Alternatively, you can set this option to the path to a custom lockfile using pi removal_hint={'Use the export goal\'s --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.'} > -If true, export a virtual environment with Pydocstyle when running `scie-pants-linux-x86_64 export`. +If true, export a virtual environment with Pydocstyle when running `pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. diff --git a/versioned_docs/version-2.17/reference/subsystems/pylint.mdx b/versioned_docs/version-2.17/reference/subsystems/pylint.mdx index dcb35b553..4075fee71 100644 --- a/versioned_docs/version-2.17/reference/subsystems/pylint.mdx +++ b/versioned_docs/version-2.17/reference/subsystems/pylint.mdx @@ -25,7 +25,7 @@ Config section: `[pylint]` default_repr={`False`} > -If true, don't use Pylint when running `scie-pants-linux-x86_64 lint`. +If true, don't use Pylint when running `pants lint`. @@ -199,7 +199,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/lint/pylint/pylint.lock for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=pylint`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=pylint`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. @@ -215,7 +215,7 @@ Alternatively, you can set this option to the path to a custom lockfile using pi removal_hint={'Use the export goal\'s --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.'} > -If true, export a virtual environment with Pylint when running `scie-pants-linux-x86_64 export`. +If true, export a virtual environment with Pylint when running `pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. diff --git a/versioned_docs/version-2.17/reference/subsystems/pyoxidizer.mdx b/versioned_docs/version-2.17/reference/subsystems/pyoxidizer.mdx index 706db047e..4470d7e56 100644 --- a/versioned_docs/version-2.17/reference/subsystems/pyoxidizer.mdx +++ b/versioned_docs/version-2.17/reference/subsystems/pyoxidizer.mdx @@ -151,7 +151,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/packaging/pyoxidizer/pyoxidizer.lock for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=pyoxidizer`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=pyoxidizer`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.17/reference/subsystems/pytest.mdx b/versioned_docs/version-2.17/reference/subsystems/pytest.mdx index 5a4a76e30..8cf653cdc 100644 --- a/versioned_docs/version-2.17/reference/subsystems/pytest.mdx +++ b/versioned_docs/version-2.17/reference/subsystems/pytest.mdx @@ -51,7 +51,7 @@ NOTE: Enabling `pytest-xdist` can cause high-level scoped fixtures (for example default_repr={`False`} > -If true, don't use Pytest when running `scie-pants-linux-x86_64 test`. +If true, don't use Pytest when running `pants test`. @@ -213,7 +213,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/subsystems/pytest.lock for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=pytest`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=pytest`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. @@ -229,7 +229,7 @@ Alternatively, you can set this option to the path to a custom lockfile using pi removal_hint={'Use the export goal\'s --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.'} > -If true, export a virtual environment with Pytest when running `scie-pants-linux-x86_64 export`. +If true, export a virtual environment with Pytest when running `pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. diff --git a/versioned_docs/version-2.17/reference/subsystems/python-infer.mdx b/versioned_docs/version-2.17/reference/subsystems/python-infer.mdx index a4a60fb38..177804134 100644 --- a/versioned_docs/version-2.17/reference/subsystems/python-infer.mdx +++ b/versioned_docs/version-2.17/reference/subsystems/python-infer.mdx @@ -94,7 +94,7 @@ If --assets is True, treat valid-looking strings with at least this many forward Infer a target's dependencies on any `__init__.py` files in the packages it is located in (recursively upward in the directory structure). -Even if this is set to `never` or `content_only`, Pants will still always include any ancestor `__init__.py` files in the sandbox. Only, they will not be "proper" dependencies, e.g. they will not show up in `scie-pants-linux-x86_64 dependencies` and their own dependencies will not be used. +Even if this is set to `never` or `content_only`, Pants will still always include any ancestor `__init__.py` files in the sandbox. Only, they will not be "proper" dependencies, e.g. they will not show up in `pants dependencies` and their own dependencies will not be used. By default, Pants only adds a "proper" dependency if there is content in the `__init__.py` file. This makes sure that dependencies are added when likely necessary to build, while also avoiding adding unnecessary dependencies. While accurate, those unnecessary dependencies can complicate setting metadata like the `interpreter_constraints` and `resolve` fields. @@ -204,7 +204,7 @@ As a result of the switch, cold-cache performance improved by a factor of about However, since this parser is completely different it has the potential of introducing differences in dependency inference. Although the Pants suite of tests only identified differences when using the `# pants: no-infer-dep` pragma, and string-based imports/assets, Out of an abundance of caution, this is behind a feature flag that will eventually be on-by-default then removed. -It is recommended that you run `scie-pants-linux-x86_64 peek :: > before.json` and then `scie-pants-linux-x86_64 --python-infer-use-rust-parser peek :: > after.json` and compare the two results. If all looks good, set `use_rust_parser` in `[python-infer]` in `pants.toml`. If you think there's a bug please file an issue: https://github.com/pantsbuild/pants/issues/new/choose. +It is recommended that you run `pants peek :: > before.json` and then `pants --python-infer-use-rust-parser peek :: > after.json` and compare the two results. If all looks good, set `use_rust_parser` in `[python-infer]` in `pants.toml`. If you think there's a bug please file an issue: https://github.com/pantsbuild/pants/issues/new/choose. diff --git a/versioned_docs/version-2.17/reference/subsystems/python.mdx b/versioned_docs/version-2.17/reference/subsystems/python.mdx index a500c0aaf..c70645295 100644 --- a/versioned_docs/version-2.17/reference/subsystems/python.mdx +++ b/versioned_docs/version-2.17/reference/subsystems/python.mdx @@ -107,14 +107,14 @@ A mapping of logical names to lockfile paths used in your project. Many organizations only need a single resolve for their whole project, which is a good default and often the simplest thing to do. However, you may need multiple resolves, such as if you use two conflicting versions of a requirement in your repository. -If you only need a single resolve, run `scie-pants-linux-x86_64 generate-lockfiles` to generate the lockfile. +If you only need a single resolve, run `pants generate-lockfiles` to generate the lockfile. If you need multiple resolves: 1. Via this option, define multiple resolve names and their lockfile paths. The names should be meaningful to your repository, such as `data-science` or `pants-plugins`. 2. Set the default with `[python].default_resolve`. 3. Update your `python_requirement` targets with the `resolve` field to declare which resolve they should be available in. They default to `[python].default_resolve`, so you only need to update targets that you want in non-default resolves. (Often you'll set this via the `python_requirements` or `poetry_requirements` target generators) -4. Run `scie-pants-linux-x86_64 generate-lockfiles` to generate the lockfiles. If the results aren't what you'd expect, adjust the prior step. +4. Run `pants generate-lockfiles` to generate the lockfiles. If the results aren't what you'd expect, adjust the prior step. 5. Update any targets like `python_source` / `python_sources`, `python_test` / `python_tests`, and `pex_binary` which need to set a non-default resolve with the `resolve` field. If a target can work with multiple resolves, you can either use the `parametrize` mechanism or manually create a distinct target per resolve. See https://www.pantsbuild.org/v2.17/docs/targets for information about `parametrize`. @@ -416,7 +416,7 @@ If another targets address is in conflict with the created lockfile target, it w env_repr='PANTS_PYTHON_REQUIREMENT_CONSTRAINTS' default_repr={`None`} removal_version='3.0.0.dev0' - removal_hint={'We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.

To migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `scie-pants-linux-x86_64 generate-lockfiles`.'} + removal_hint={'We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.

To migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `pants generate-lockfiles`.'} > When resolving third-party requirements for your own code (vs. tools you run), use this constraints file to determine which versions to use. @@ -436,7 +436,7 @@ This only applies when resolving user requirements, rather than tools you run li env_repr='PANTS_PYTHON_RESOLVE_ALL_CONSTRAINTS' default_repr={`True`} removal_version='3.0.0.dev0' - removal_hint={'We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.

To migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `scie-pants-linux-x86_64 generate-lockfiles`.'} + removal_hint={'We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.

To migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `pants generate-lockfiles`.'} > (Only relevant when using `[python].requirement_constraints.`) If enabled, when resolving requirements, Pants will first resolve your entire constraints file as a single global resolve. Then, if the code uses a subset of your constraints file, Pants will extract the relevant requirements from that global resolve so that only what's actually needed gets used. If disabled, Pants will not use a global resolve and will resolve each subset of your requirements independently. diff --git a/versioned_docs/version-2.17/reference/subsystems/pyupgrade.mdx b/versioned_docs/version-2.17/reference/subsystems/pyupgrade.mdx index ad4e18401..b129cccc5 100644 --- a/versioned_docs/version-2.17/reference/subsystems/pyupgrade.mdx +++ b/versioned_docs/version-2.17/reference/subsystems/pyupgrade.mdx @@ -25,7 +25,7 @@ Config section: `[pyupgrade]` default_repr={`False`} > -If true, don't use pyupgrade when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use pyupgrade when running `pants fmt` and `pants lint`. @@ -161,7 +161,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/lint/pyupgrade/pyupgrade.lock for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=pyupgrade`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=pyupgrade`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. @@ -177,7 +177,7 @@ Alternatively, you can set this option to the path to a custom lockfile using pi removal_hint={'Use the export goal\'s --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.'} > -If true, export a virtual environment with pyupgrade when running `scie-pants-linux-x86_64 export`. +If true, export a virtual environment with pyupgrade when running `pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. diff --git a/versioned_docs/version-2.17/reference/subsystems/regex-lint.mdx b/versioned_docs/version-2.17/reference/subsystems/regex-lint.mdx index a919e6ff4..20d8d1542 100644 --- a/versioned_docs/version-2.17/reference/subsystems/regex-lint.mdx +++ b/versioned_docs/version-2.17/reference/subsystems/regex-lint.mdx @@ -29,7 +29,7 @@ Config section: `[regex-lint]` default_repr={`False`} > -If true, don't use regex-lint when running `scie-pants-linux-x86_64 lint`. +If true, don't use regex-lint when running `pants lint`. diff --git a/versioned_docs/version-2.17/reference/subsystems/ruff.mdx b/versioned_docs/version-2.17/reference/subsystems/ruff.mdx index 95b9282bf..65e1286de 100644 --- a/versioned_docs/version-2.17/reference/subsystems/ruff.mdx +++ b/versioned_docs/version-2.17/reference/subsystems/ruff.mdx @@ -25,7 +25,7 @@ Config section: `[ruff]` default_repr={`False`} > -If true, don't use Ruff when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use Ruff when running `pants fmt` and `pants lint`. @@ -189,7 +189,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/lint/ruff/ruff.lock for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=ruff`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=ruff`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. @@ -205,7 +205,7 @@ Alternatively, you can set this option to the path to a custom lockfile using pi removal_hint={'Use the export goal\'s --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.'} > -If true, export a virtual environment with Ruff when running `scie-pants-linux-x86_64 export`. +If true, export a virtual environment with Ruff when running `pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. diff --git a/versioned_docs/version-2.17/reference/subsystems/scalafmt.mdx b/versioned_docs/version-2.17/reference/subsystems/scalafmt.mdx index ff729016b..f6ca16770 100644 --- a/versioned_docs/version-2.17/reference/subsystems/scalafmt.mdx +++ b/versioned_docs/version-2.17/reference/subsystems/scalafmt.mdx @@ -25,7 +25,7 @@ Config section: `[scalafmt]` default_repr={`False`} > -If true, don't use scalafmt when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use scalafmt when running `pants fmt` and `pants lint`. @@ -67,7 +67,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/scala/lint/scalafmt/scalafmt.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalafmt`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=scalafmt`. diff --git a/versioned_docs/version-2.17/reference/subsystems/scalapb.mdx b/versioned_docs/version-2.17/reference/subsystems/scalapb.mdx index 6893f7f54..db89be6d3 100644 --- a/versioned_docs/version-2.17/reference/subsystems/scalapb.mdx +++ b/versioned_docs/version-2.17/reference/subsystems/scalapb.mdx @@ -69,7 +69,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/codegen/protobuf/scala/scalapbc.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalapb`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=scalapb`. diff --git a/versioned_docs/version-2.17/reference/subsystems/scalatest.mdx b/versioned_docs/version-2.17/reference/subsystems/scalatest.mdx index 405aa4081..29bafcf4a 100644 --- a/versioned_docs/version-2.17/reference/subsystems/scalatest.mdx +++ b/versioned_docs/version-2.17/reference/subsystems/scalatest.mdx @@ -39,7 +39,7 @@ See https://www.scalatest.org/user_guide/using_the_runner for supported argument default_repr={`False`} > -If true, don't use Scalatest when running `scie-pants-linux-x86_64 test`. +If true, don't use Scalatest when running `pants test`. @@ -81,7 +81,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/scala/subsystems/scalatest.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalatest`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=scalatest`. diff --git a/versioned_docs/version-2.17/reference/subsystems/setuptools-scm.mdx b/versioned_docs/version-2.17/reference/subsystems/setuptools-scm.mdx index 404650665..6d21ef376 100644 --- a/versioned_docs/version-2.17/reference/subsystems/setuptools-scm.mdx +++ b/versioned_docs/version-2.17/reference/subsystems/setuptools-scm.mdx @@ -139,7 +139,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/subsystems/setuptools_scm.lock for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=setuptools-scm`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=setuptools-scm`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.17/reference/subsystems/setuptools.mdx b/versioned_docs/version-2.17/reference/subsystems/setuptools.mdx index a3aff65a1..76d092ffc 100644 --- a/versioned_docs/version-2.17/reference/subsystems/setuptools.mdx +++ b/versioned_docs/version-2.17/reference/subsystems/setuptools.mdx @@ -103,7 +103,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/subsystems/setuptools.lock for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=setuptools`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=setuptools`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.17/reference/subsystems/shell-test.mdx b/versioned_docs/version-2.17/reference/subsystems/shell-test.mdx index 3c748d702..1a371c907 100644 --- a/versioned_docs/version-2.17/reference/subsystems/shell-test.mdx +++ b/versioned_docs/version-2.17/reference/subsystems/shell-test.mdx @@ -25,7 +25,7 @@ Config section: `[shell-test]` default_repr={`False`} > -If true, don't use Test with shell scripts when running `scie-pants-linux-x86_64 test`. +If true, don't use Test with shell scripts when running `pants test`. diff --git a/versioned_docs/version-2.17/reference/subsystems/shellcheck.mdx b/versioned_docs/version-2.17/reference/subsystems/shellcheck.mdx index 0806a26fb..648bbd985 100644 --- a/versioned_docs/version-2.17/reference/subsystems/shellcheck.mdx +++ b/versioned_docs/version-2.17/reference/subsystems/shellcheck.mdx @@ -25,7 +25,7 @@ Config section: `[shellcheck]` default_repr={`False`} > -If true, don't use Shellcheck when running `scie-pants-linux-x86_64 lint`. +If true, don't use Shellcheck when running `pants lint`. diff --git a/versioned_docs/version-2.17/reference/subsystems/shfmt.mdx b/versioned_docs/version-2.17/reference/subsystems/shfmt.mdx index e1836db38..55eff876b 100644 --- a/versioned_docs/version-2.17/reference/subsystems/shfmt.mdx +++ b/versioned_docs/version-2.17/reference/subsystems/shfmt.mdx @@ -25,7 +25,7 @@ Config section: `[shfmt]` default_repr={`False`} > -If true, don't use shfmt when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use shfmt when running `pants fmt` and `pants lint`. diff --git a/versioned_docs/version-2.17/reference/subsystems/shunit2.mdx b/versioned_docs/version-2.17/reference/subsystems/shunit2.mdx index fe1308b37..93f981d77 100644 --- a/versioned_docs/version-2.17/reference/subsystems/shunit2.mdx +++ b/versioned_docs/version-2.17/reference/subsystems/shunit2.mdx @@ -25,7 +25,7 @@ Config section: `[shunit2]` default_repr={`False`} > -If true, don't use shunit2 when running `scie-pants-linux-x86_64 test`. +If true, don't use shunit2 when running `pants test`. diff --git a/versioned_docs/version-2.17/reference/subsystems/spectral.mdx b/versioned_docs/version-2.17/reference/subsystems/spectral.mdx index 61540d8b9..040a2646c 100644 --- a/versioned_docs/version-2.17/reference/subsystems/spectral.mdx +++ b/versioned_docs/version-2.17/reference/subsystems/spectral.mdx @@ -25,7 +25,7 @@ Config section: `[spectral]` default_repr={`False`} > -If true, don't use Spectral when running `scie-pants-linux-x86_64 lint`. +If true, don't use Spectral when running `pants lint`. diff --git a/versioned_docs/version-2.17/reference/subsystems/terraform-fmt.mdx b/versioned_docs/version-2.17/reference/subsystems/terraform-fmt.mdx index 968e542ad..c675ed16b 100644 --- a/versioned_docs/version-2.17/reference/subsystems/terraform-fmt.mdx +++ b/versioned_docs/version-2.17/reference/subsystems/terraform-fmt.mdx @@ -25,7 +25,7 @@ Config section: `[terraform-fmt]` default_repr={`False`} > -If true, don't use `terraform fmt` when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use `terraform fmt` when running `pants fmt` and `pants lint`. diff --git a/versioned_docs/version-2.17/reference/subsystems/terraform-hcl2-parser.mdx b/versioned_docs/version-2.17/reference/subsystems/terraform-hcl2-parser.mdx index ab546a7b6..ffa874a7a 100644 --- a/versioned_docs/version-2.17/reference/subsystems/terraform-hcl2-parser.mdx +++ b/versioned_docs/version-2.17/reference/subsystems/terraform-hcl2-parser.mdx @@ -115,7 +115,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/terraform/hcl2.lock for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=terraform-hcl2-parser`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=terraform-hcl2-parser`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.17/reference/subsystems/terraform-validate.mdx b/versioned_docs/version-2.17/reference/subsystems/terraform-validate.mdx index a84bf5b6c..e7686bc2f 100644 --- a/versioned_docs/version-2.17/reference/subsystems/terraform-validate.mdx +++ b/versioned_docs/version-2.17/reference/subsystems/terraform-validate.mdx @@ -25,7 +25,7 @@ Config section: `[terraform-validate]` default_repr={`False`} > -If true, don't use `terraform validate` when running `scie-pants-linux-x86_64 check`. +If true, don't use `terraform validate` when running `pants check`. diff --git a/versioned_docs/version-2.17/reference/subsystems/twine.mdx b/versioned_docs/version-2.17/reference/subsystems/twine.mdx index f18603a57..725e8f135 100644 --- a/versioned_docs/version-2.17/reference/subsystems/twine.mdx +++ b/versioned_docs/version-2.17/reference/subsystems/twine.mdx @@ -25,7 +25,7 @@ Config section: `[twine]` default_repr={`False`} > -If true, don't use Twine when running `scie-pants-linux-x86_64 publish`. +If true, don't use Twine when running `pants publish`. @@ -207,7 +207,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/subsystems/twine.lock for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=twine`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=twine`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. diff --git a/versioned_docs/version-2.17/reference/subsystems/yamllint.mdx b/versioned_docs/version-2.17/reference/subsystems/yamllint.mdx index 6debc4b5d..b4067428b 100644 --- a/versioned_docs/version-2.17/reference/subsystems/yamllint.mdx +++ b/versioned_docs/version-2.17/reference/subsystems/yamllint.mdx @@ -61,7 +61,7 @@ Arguments to pass directly to Yamllint, e.g. `--yamllint-args='-d relaxed'`. default_repr={`False`} > -If true, don't use Yamllint when running `scie-pants-linux-x86_64 lint`. +If true, don't use Yamllint when running `pants lint`. @@ -197,7 +197,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/tools/yamllint/yamllint.lock for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=yamllint`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=yamllint`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. @@ -213,7 +213,7 @@ Alternatively, you can set this option to the path to a custom lockfile using pi removal_hint={'Use the export goal\'s --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.'} > -If true, export a virtual environment with Yamllint when running `scie-pants-linux-x86_64 export`. +If true, export a virtual environment with Yamllint when running `pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. diff --git a/versioned_docs/version-2.17/reference/subsystems/yapf.mdx b/versioned_docs/version-2.17/reference/subsystems/yapf.mdx index 03fb5cbd6..b1e88add3 100644 --- a/versioned_docs/version-2.17/reference/subsystems/yapf.mdx +++ b/versioned_docs/version-2.17/reference/subsystems/yapf.mdx @@ -25,7 +25,7 @@ Config section: `[yapf]` default_repr={`False`} > -If true, don't use yapf when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use yapf when running `pants fmt` and `pants lint`. @@ -191,7 +191,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` and `--extra-requirements` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior`). See https://github.com/pantsbuild/pants/blob/release_2.17.1rc3/src/python/pants/backend/python/lint/yapf/yapf.lock for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 generate-lockfiles --resolve=yapf`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants generate-lockfiles --resolve=yapf`. Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with `--hash`. Set `[python].invalid_lockfile_behavior = 'ignore'` so that Pants does not complain about missing lockfile headers. @@ -207,7 +207,7 @@ Alternatively, you can set this option to the path to a custom lockfile using pi removal_hint={'Use the export goal\'s --resolve option to select tools to export, instead of using this option to exempt a tool from export-by-default.'} > -If true, export a virtual environment with yapf when running `scie-pants-linux-x86_64 export`. +If true, export a virtual environment with yapf when running `pants export`. This can be useful, for example, with IDE integrations to point your editor to the tool's binary. diff --git a/versioned_docs/version-2.17/reference/targets/adhoc_tool.mdx b/versioned_docs/version-2.17/reference/targets/adhoc_tool.mdx index 4378a4583..985e36caa 100644 --- a/versioned_docs/version-2.17/reference/targets/adhoc_tool.mdx +++ b/versioned_docs/version-2.17/reference/targets/adhoc_tool.mdx @@ -38,7 +38,7 @@ Backend: `pants.backend.experimental.adhoc` @@ -51,7 +51,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.17/reference/targets/archive.mdx b/versioned_docs/version-2.17/reference/targets/archive.mdx index c0c9b9ef7..b3f69629d 100644 --- a/versioned_docs/version-2.17/reference/targets/archive.mdx +++ b/versioned_docs/version-2.17/reference/targets/archive.mdx @@ -24,7 +24,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -52,7 +52,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. @@ -65,11 +65,11 @@ Warning: setting this value risks naming collisions with other package targets y default_repr={`None`} > -Addresses to any targets that can be built with `scie-pants-linux-x86_64 package`, e.g. `["project:app"]`. +Addresses to any targets that can be built with `pants package`, e.g. `["project:app"]`. -Pants will build the assets as if you had run `scie-pants-linux-x86_64 package`. It will include the results in your archive using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). +Pants will build the assets as if you had run `pants package`. It will include the results in your archive using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). -You can include anything that can be built by `scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or even another `archive`. +You can include anything that can be built by `pants package`, e.g. a `pex_binary`, `python_awslambda`, or even another `archive`. diff --git a/versioned_docs/version-2.17/reference/targets/deploy_jar.mdx b/versioned_docs/version-2.17/reference/targets/deploy_jar.mdx index e80e03f20..21e983cb7 100644 --- a/versioned_docs/version-2.17/reference/targets/deploy_jar.mdx +++ b/versioned_docs/version-2.17/reference/targets/deploy_jar.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.experimental.java` @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -65,7 +65,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. @@ -80,9 +80,9 @@ Warning: setting this value risks naming collisions with other package targets y Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.17/reference/targets/docker_environment.mdx b/versioned_docs/version-2.17/reference/targets/docker_environment.mdx index 56407a875..933d8dd92 100644 --- a/versioned_docs/version-2.17/reference/targets/docker_environment.mdx +++ b/versioned_docs/version-2.17/reference/targets/docker_environment.mdx @@ -30,7 +30,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.17/reference/targets/docker_image.mdx b/versioned_docs/version-2.17/reference/targets/docker_image.mdx index 3945b42d5..67314981d 100644 --- a/versioned_docs/version-2.17/reference/targets/docker_image.mdx +++ b/versioned_docs/version-2.17/reference/targets/docker_image.mdx @@ -39,7 +39,7 @@ Backend: `pants.backend.docker` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -52,7 +52,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -78,9 +78,9 @@ Use `[docker].build_args` to set default build args for all images. Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -277,7 +277,7 @@ See [Docker documentation](https://docs.docker.com/develop/develop-images/build_ default_repr={`False`} > -If true, do not push this image to registries when running `scie-pants-linux-x86_64 publish`. +If true, do not push this image to registries when running `pants publish`. @@ -333,7 +333,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. diff --git a/versioned_docs/version-2.17/reference/targets/experimental_test_shell_command.mdx b/versioned_docs/version-2.17/reference/targets/experimental_test_shell_command.mdx index d9cbf0eed..58eccc73a 100644 --- a/versioned_docs/version-2.17/reference/targets/experimental_test_shell_command.mdx +++ b/versioned_docs/version-2.17/reference/targets/experimental_test_shell_command.mdx @@ -39,7 +39,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -52,7 +52,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.17/reference/targets/experimental_wrap_as_go_package_sources.mdx b/versioned_docs/version-2.17/reference/targets/experimental_wrap_as_go_package_sources.mdx index 76db3f1ba..0630639a4 100644 --- a/versioned_docs/version-2.17/reference/targets/experimental_wrap_as_go_package_sources.mdx +++ b/versioned_docs/version-2.17/reference/targets/experimental_wrap_as_go_package_sources.mdx @@ -30,7 +30,7 @@ Backend: `pants.backend.experimental.go` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.17/reference/targets/experimental_wrap_as_java_sources.mdx b/versioned_docs/version-2.17/reference/targets/experimental_wrap_as_java_sources.mdx index 940029f9b..ff3e04681 100644 --- a/versioned_docs/version-2.17/reference/targets/experimental_wrap_as_java_sources.mdx +++ b/versioned_docs/version-2.17/reference/targets/experimental_wrap_as_java_sources.mdx @@ -30,7 +30,7 @@ Backend: `pants.backend.experimental.java` @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.17/reference/targets/experimental_wrap_as_kotlin_sources.mdx b/versioned_docs/version-2.17/reference/targets/experimental_wrap_as_kotlin_sources.mdx index 003b6ad9a..bae3428a7 100644 --- a/versioned_docs/version-2.17/reference/targets/experimental_wrap_as_kotlin_sources.mdx +++ b/versioned_docs/version-2.17/reference/targets/experimental_wrap_as_kotlin_sources.mdx @@ -30,7 +30,7 @@ Backend: `pants.backend.experimental.kotlin` @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.17/reference/targets/experimental_wrap_as_python_sources.mdx b/versioned_docs/version-2.17/reference/targets/experimental_wrap_as_python_sources.mdx index a341b498b..5751ec09f 100644 --- a/versioned_docs/version-2.17/reference/targets/experimental_wrap_as_python_sources.mdx +++ b/versioned_docs/version-2.17/reference/targets/experimental_wrap_as_python_sources.mdx @@ -30,7 +30,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.17/reference/targets/experimental_wrap_as_resources.mdx b/versioned_docs/version-2.17/reference/targets/experimental_wrap_as_resources.mdx index bdb4704b5..7f60252a5 100644 --- a/versioned_docs/version-2.17/reference/targets/experimental_wrap_as_resources.mdx +++ b/versioned_docs/version-2.17/reference/targets/experimental_wrap_as_resources.mdx @@ -30,7 +30,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.17/reference/targets/experimental_wrap_as_scala_sources.mdx b/versioned_docs/version-2.17/reference/targets/experimental_wrap_as_scala_sources.mdx index df94d3733..5548c481b 100644 --- a/versioned_docs/version-2.17/reference/targets/experimental_wrap_as_scala_sources.mdx +++ b/versioned_docs/version-2.17/reference/targets/experimental_wrap_as_scala_sources.mdx @@ -30,7 +30,7 @@ Backend: `pants.backend.experimental.scala` @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.17/reference/targets/file.mdx b/versioned_docs/version-2.17/reference/targets/file.mdx index 44d4b985d..157214412 100644 --- a/versioned_docs/version-2.17/reference/targets/file.mdx +++ b/versioned_docs/version-2.17/reference/targets/file.mdx @@ -26,7 +26,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -52,9 +52,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.17/reference/targets/files.mdx b/versioned_docs/version-2.17/reference/targets/files.mdx index 6536f0f0b..396266b7d 100644 --- a/versioned_docs/version-2.17/reference/targets/files.mdx +++ b/versioned_docs/version-2.17/reference/targets/files.mdx @@ -24,7 +24,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -94,9 +94,9 @@ You can specify the same file name in multiple keys, so long as you don't o Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.17/reference/targets/go_binary.mdx b/versioned_docs/version-2.17/reference/targets/go_binary.mdx index 55a27e2dd..e1a85a7a6 100644 --- a/versioned_docs/version-2.17/reference/targets/go_binary.mdx +++ b/versioned_docs/version-2.17/reference/targets/go_binary.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.go` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -52,7 +52,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. diff --git a/versioned_docs/version-2.17/reference/targets/go_mod.mdx b/versioned_docs/version-2.17/reference/targets/go_mod.mdx index ea3d4e8ad..a0cfd6173 100644 --- a/versioned_docs/version-2.17/reference/targets/go_mod.mdx +++ b/versioned_docs/version-2.17/reference/targets/go_mod.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.go` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.17/reference/targets/go_package.mdx b/versioned_docs/version-2.17/reference/targets/go_package.mdx index 402df14e0..0713e4102 100644 --- a/versioned_docs/version-2.17/reference/targets/go_package.mdx +++ b/versioned_docs/version-2.17/reference/targets/go_package.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.experimental.go` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -52,9 +52,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.17/reference/targets/go_third_party_package.mdx b/versioned_docs/version-2.17/reference/targets/go_third_party_package.mdx index 518a5db7f..909c2507f 100644 --- a/versioned_docs/version-2.17/reference/targets/go_third_party_package.mdx +++ b/versioned_docs/version-2.17/reference/targets/go_third_party_package.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.go` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -54,9 +54,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.17/reference/targets/helm_artifact.mdx b/versioned_docs/version-2.17/reference/targets/helm_artifact.mdx index 0c94682be..df2c66974 100644 --- a/versioned_docs/version-2.17/reference/targets/helm_artifact.mdx +++ b/versioned_docs/version-2.17/reference/targets/helm_artifact.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.helm` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.17/reference/targets/helm_chart.mdx b/versioned_docs/version-2.17/reference/targets/helm_chart.mdx index fe473a9ec..284c9d0ad 100644 --- a/versioned_docs/version-2.17/reference/targets/helm_chart.mdx +++ b/versioned_docs/version-2.17/reference/targets/helm_chart.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.helm` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -76,9 +76,9 @@ Example: `sources=['values.yaml', 'templates/*.yaml', '!values_ignore.yaml']` Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -99,7 +99,7 @@ If undefined, this will use the path to the BUILD file, For example, `src/charts Regardless of whether you use the default or set this field, the path will end with Helms's file format of `-.tgz`, where `chart_name` and `chart_version` are the values extracted from the Chart.yaml file. So, using the default for this field, the target `src/charts/mychart:tgt_name` might have a final path like `src.charts.mychart/tgt_name/mychart-0.1.0.tgz`. -When running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. @@ -170,7 +170,7 @@ The above example shows two valid `registry` options: using an alias to a config default_repr={`False`} > -If set to true, do not push this Helm chart to registries when running `scie-pants-linux-x86_64 publish`. +If set to true, do not push this Helm chart to registries when running `pants publish`. @@ -181,7 +181,7 @@ If set to true, do not push this Helm chart to registries when running `scie-pan default_repr={`False`} > -If set to true, do not run any linting in this Helm chart when running `scie-pants-linux-x86_64 lint`. +If set to true, do not run any linting in this Helm chart when running `pants lint`. diff --git a/versioned_docs/version-2.17/reference/targets/helm_deployment.mdx b/versioned_docs/version-2.17/reference/targets/helm_deployment.mdx index 2e98ef903..df5081697 100644 --- a/versioned_docs/version-2.17/reference/targets/helm_deployment.mdx +++ b/versioned_docs/version-2.17/reference/targets/helm_deployment.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.helm` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -61,9 +61,9 @@ Name of the release used in the deployment. If not set, the target name will be Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.17/reference/targets/helm_unittest_test.mdx b/versioned_docs/version-2.17/reference/targets/helm_unittest_test.mdx index e8fb9e87e..97331affa 100644 --- a/versioned_docs/version-2.17/reference/targets/helm_unittest_test.mdx +++ b/versioned_docs/version-2.17/reference/targets/helm_unittest_test.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.helm` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -63,9 +63,9 @@ Path is relative to the BUILD file's directory, e.g. `source='example.ext'` Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.17/reference/targets/helm_unittest_tests.mdx b/versioned_docs/version-2.17/reference/targets/helm_unittest_tests.mdx index 37652ce53..a18e10877 100644 --- a/versioned_docs/version-2.17/reference/targets/helm_unittest_tests.mdx +++ b/versioned_docs/version-2.17/reference/targets/helm_unittest_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.helm` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -65,9 +65,9 @@ Example: `sources=['*_test.yaml', '!ignore_test.yaml']` Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.17/reference/targets/java_source.mdx b/versioned_docs/version-2.17/reference/targets/java_source.mdx index 4e0f593a1..ba236709e 100644 --- a/versioned_docs/version-2.17/reference/targets/java_source.mdx +++ b/versioned_docs/version-2.17/reference/targets/java_source.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.java` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.17/reference/targets/java_sources.mdx b/versioned_docs/version-2.17/reference/targets/java_sources.mdx index 1d8532985..bea400570 100644 --- a/versioned_docs/version-2.17/reference/targets/java_sources.mdx +++ b/versioned_docs/version-2.17/reference/targets/java_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.java` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -77,9 +77,9 @@ If true, don't run Google Java Format on this target's code. Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.17/reference/targets/junit_test.mdx b/versioned_docs/version-2.17/reference/targets/junit_test.mdx index 404308916..0c23c5786 100644 --- a/versioned_docs/version-2.17/reference/targets/junit_test.mdx +++ b/versioned_docs/version-2.17/reference/targets/junit_test.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.java` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -91,9 +91,9 @@ This will be merged with and override values from `[test].extra_env_vars`. Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.17/reference/targets/junit_tests.mdx b/versioned_docs/version-2.17/reference/targets/junit_tests.mdx index 0be6e7736..900655a97 100644 --- a/versioned_docs/version-2.17/reference/targets/junit_tests.mdx +++ b/versioned_docs/version-2.17/reference/targets/junit_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.java` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -93,9 +93,9 @@ This will be merged with and override values from `[test].extra_env_vars`. Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.17/reference/targets/jvm_artifact.mdx b/versioned_docs/version-2.17/reference/targets/jvm_artifact.mdx index 25cdbf995..cc35d00e5 100644 --- a/versioned_docs/version-2.17/reference/targets/jvm_artifact.mdx +++ b/versioned_docs/version-2.17/reference/targets/jvm_artifact.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.java` @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.17/reference/targets/jvm_war.mdx b/versioned_docs/version-2.17/reference/targets/jvm_war.mdx index d6c5ff4e1..4eb8d48f7 100644 --- a/versioned_docs/version-2.17/reference/targets/jvm_war.mdx +++ b/versioned_docs/version-2.17/reference/targets/jvm_war.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.java` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -74,9 +74,9 @@ A list of addresses to `resources` and `files` targets with content to place in Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -126,7 +126,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. diff --git a/versioned_docs/version-2.17/reference/targets/kotlin_junit_test.mdx b/versioned_docs/version-2.17/reference/targets/kotlin_junit_test.mdx index ac914dd99..4ea2bbc0f 100644 --- a/versioned_docs/version-2.17/reference/targets/kotlin_junit_test.mdx +++ b/versioned_docs/version-2.17/reference/targets/kotlin_junit_test.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.kotlin` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.17/reference/targets/kotlin_junit_tests.mdx b/versioned_docs/version-2.17/reference/targets/kotlin_junit_tests.mdx index f79948a00..eb05e9e9f 100644 --- a/versioned_docs/version-2.17/reference/targets/kotlin_junit_tests.mdx +++ b/versioned_docs/version-2.17/reference/targets/kotlin_junit_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.kotlin` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -65,9 +65,9 @@ Example: `sources=['*Test.kt', '!TestIgnore.kt']` Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.17/reference/targets/kotlin_source.mdx b/versioned_docs/version-2.17/reference/targets/kotlin_source.mdx index d780f844f..dd0113246 100644 --- a/versioned_docs/version-2.17/reference/targets/kotlin_source.mdx +++ b/versioned_docs/version-2.17/reference/targets/kotlin_source.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.kotlin` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.17/reference/targets/kotlin_sources.mdx b/versioned_docs/version-2.17/reference/targets/kotlin_sources.mdx index 8cc4d2f83..7ad97ac88 100644 --- a/versioned_docs/version-2.17/reference/targets/kotlin_sources.mdx +++ b/versioned_docs/version-2.17/reference/targets/kotlin_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.kotlin` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -77,9 +77,9 @@ If true, don't run Ktlint on this target's code. Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.17/reference/targets/kotlinc_plugin.mdx b/versioned_docs/version-2.17/reference/targets/kotlinc_plugin.mdx index c8ad9eb36..828754fa0 100644 --- a/versioned_docs/version-2.17/reference/targets/kotlinc_plugin.mdx +++ b/versioned_docs/version-2.17/reference/targets/kotlinc_plugin.mdx @@ -34,7 +34,7 @@ Backend: `pants.backend.experimental.kotlin` @@ -47,7 +47,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.17/reference/targets/local_environment.mdx b/versioned_docs/version-2.17/reference/targets/local_environment.mdx index 5dd6b4ebd..1867767ac 100644 --- a/versioned_docs/version-2.17/reference/targets/local_environment.mdx +++ b/versioned_docs/version-2.17/reference/targets/local_environment.mdx @@ -30,7 +30,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.17/reference/targets/openapi_document.mdx b/versioned_docs/version-2.17/reference/targets/openapi_document.mdx index 241ef2913..7b52b0275 100644 --- a/versioned_docs/version-2.17/reference/targets/openapi_document.mdx +++ b/versioned_docs/version-2.17/reference/targets/openapi_document.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.openapi` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.17/reference/targets/openapi_documents.mdx b/versioned_docs/version-2.17/reference/targets/openapi_documents.mdx index 8d7dfa39a..58827613f 100644 --- a/versioned_docs/version-2.17/reference/targets/openapi_documents.mdx +++ b/versioned_docs/version-2.17/reference/targets/openapi_documents.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.openapi` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -77,9 +77,9 @@ If true, don't run `spectral lint` on this target's code. Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.17/reference/targets/openapi_source.mdx b/versioned_docs/version-2.17/reference/targets/openapi_source.mdx index 0622a2f8f..e9ba3532e 100644 --- a/versioned_docs/version-2.17/reference/targets/openapi_source.mdx +++ b/versioned_docs/version-2.17/reference/targets/openapi_source.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.openapi` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.17/reference/targets/openapi_sources.mdx b/versioned_docs/version-2.17/reference/targets/openapi_sources.mdx index a1ee7ca6f..1bd105968 100644 --- a/versioned_docs/version-2.17/reference/targets/openapi_sources.mdx +++ b/versioned_docs/version-2.17/reference/targets/openapi_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.openapi` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -65,9 +65,9 @@ Example: `sources=['*.json']` Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.17/reference/targets/pants_requirements.mdx b/versioned_docs/version-2.17/reference/targets/pants_requirements.mdx index 989bdcbf8..c31b71e88 100644 --- a/versioned_docs/version-2.17/reference/targets/pants_requirements.mdx +++ b/versioned_docs/version-2.17/reference/targets/pants_requirements.mdx @@ -30,7 +30,7 @@ Backend: `pants.backend.plugin_development` @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.17/reference/targets/pex_binaries.mdx b/versioned_docs/version-2.17/reference/targets/pex_binaries.mdx index 765470e3f..d12778caa 100644 --- a/versioned_docs/version-2.17/reference/targets/pex_binaries.mdx +++ b/versioned_docs/version-2.17/reference/targets/pex_binaries.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -147,9 +147,9 @@ All dependencies must share the same value for their `resolve` field. Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.17/reference/targets/pex_binary.mdx b/versioned_docs/version-2.17/reference/targets/pex_binary.mdx index 6970ec44a..a1a06b3b4 100644 --- a/versioned_docs/version-2.17/reference/targets/pex_binary.mdx +++ b/versioned_docs/version-2.17/reference/targets/pex_binary.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -101,9 +101,9 @@ All dependencies must share the same value for their `resolve` field. Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -400,7 +400,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. diff --git a/versioned_docs/version-2.17/reference/targets/pipenv_requirements.mdx b/versioned_docs/version-2.17/reference/targets/pipenv_requirements.mdx index e06585179..f67f613c7 100644 --- a/versioned_docs/version-2.17/reference/targets/pipenv_requirements.mdx +++ b/versioned_docs/version-2.17/reference/targets/pipenv_requirements.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.17/reference/targets/poetry_requirements.mdx b/versioned_docs/version-2.17/reference/targets/poetry_requirements.mdx index 82136c634..6edf88e02 100644 --- a/versioned_docs/version-2.17/reference/targets/poetry_requirements.mdx +++ b/versioned_docs/version-2.17/reference/targets/poetry_requirements.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.17/reference/targets/protobuf_source.mdx b/versioned_docs/version-2.17/reference/targets/protobuf_source.mdx index ffdf58a54..7684d6752 100644 --- a/versioned_docs/version-2.17/reference/targets/protobuf_source.mdx +++ b/versioned_docs/version-2.17/reference/targets/protobuf_source.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.codegen.protobuf.python Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -54,9 +54,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.17/reference/targets/protobuf_sources.mdx b/versioned_docs/version-2.17/reference/targets/protobuf_sources.mdx index c72ff4fec..dbac4775e 100644 --- a/versioned_docs/version-2.17/reference/targets/protobuf_sources.mdx +++ b/versioned_docs/version-2.17/reference/targets/protobuf_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.codegen.protobuf.python Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -221,9 +221,9 @@ Whether to generate gRPC code or not. Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.17/reference/targets/pyoxidizer_binary.mdx b/versioned_docs/version-2.17/reference/targets/pyoxidizer_binary.mdx index e3765367e..47a996a4f 100644 --- a/versioned_docs/version-2.17/reference/targets/pyoxidizer_binary.mdx +++ b/versioned_docs/version-2.17/reference/targets/pyoxidizer_binary.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.python.pac Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -58,7 +58,7 @@ If undefined, this will use the path to the BUILD file, followed by the target n Regardless of whether you use the default or set this field, the path will end with PyOxidizer's file format of `/{debug,release}/install/`, where `platform` is a Rust platform triplet like `aarch-64-apple-darwin` and `binary_name` is the value of the `binary_name` field. So, using the default for this field, the target `src/python/project:bin` might have a final path like `src.python.project/bin/aarch-64-apple-darwin/release/bin`. -When running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. diff --git a/versioned_docs/version-2.17/reference/targets/python_awslambda.mdx b/versioned_docs/version-2.17/reference/targets/python_awslambda.mdx index faeaeaab6..4ddb05808 100644 --- a/versioned_docs/version-2.17/reference/targets/python_awslambda.mdx +++ b/versioned_docs/version-2.17/reference/targets/python_awslambda.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.awslambda.python` @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -54,7 +54,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. @@ -69,9 +69,9 @@ Warning: setting this value risks naming collisions with other package targets y Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.17/reference/targets/python_distribution.mdx b/versioned_docs/version-2.17/reference/targets/python_distribution.mdx index 7d56e6157..ea4611d04 100644 --- a/versioned_docs/version-2.17/reference/targets/python_distribution.mdx +++ b/versioned_docs/version-2.17/reference/targets/python_distribution.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -71,9 +71,9 @@ See https://www.pantsbuild.org/v2.17/docs/python-interpreter-compatibility for h Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -108,7 +108,7 @@ Note that Pants will assume that any value that either starts with `:` or has `/ Pants will attempt to infer dependencies, which you can confirm by running: ``` -scie-pants-linux-x86_64 dependencies +pants dependencies ``` diff --git a/versioned_docs/version-2.17/reference/targets/python_google_cloud_function.mdx b/versioned_docs/version-2.17/reference/targets/python_google_cloud_function.mdx index 9035e5694..0c81f50a4 100644 --- a/versioned_docs/version-2.17/reference/targets/python_google_cloud_function.mdx +++ b/versioned_docs/version-2.17/reference/targets/python_google_cloud_function.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.google_cloud_function.p Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -54,7 +54,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. @@ -69,9 +69,9 @@ Warning: setting this value risks naming collisions with other package targets y Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.17/reference/targets/python_requirement.mdx b/versioned_docs/version-2.17/reference/targets/python_requirement.mdx index e00d4a37d..a875cc367 100644 --- a/versioned_docs/version-2.17/reference/targets/python_requirement.mdx +++ b/versioned_docs/version-2.17/reference/targets/python_requirement.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -69,9 +69,9 @@ If the requirement depends on some other requirement to work, such as needing `s Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.17/reference/targets/python_requirements.mdx b/versioned_docs/version-2.17/reference/targets/python_requirements.mdx index 621be0c31..b4078a301 100644 --- a/versioned_docs/version-2.17/reference/targets/python_requirements.mdx +++ b/versioned_docs/version-2.17/reference/targets/python_requirements.mdx @@ -30,7 +30,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.17/reference/targets/python_source.mdx b/versioned_docs/version-2.17/reference/targets/python_source.mdx index 0766503dd..af7d80f24 100644 --- a/versioned_docs/version-2.17/reference/targets/python_source.mdx +++ b/versioned_docs/version-2.17/reference/targets/python_source.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -69,9 +69,9 @@ See https://www.pantsbuild.org/v2.17/docs/python-interpreter-compatibility for h Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.17/reference/targets/python_sources.mdx b/versioned_docs/version-2.17/reference/targets/python_sources.mdx index df6aec7a3..cf48c4fd5 100644 --- a/versioned_docs/version-2.17/reference/targets/python_sources.mdx +++ b/versioned_docs/version-2.17/reference/targets/python_sources.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -286,9 +286,9 @@ The latter mode is similar to creating, activating, and using a virtual environm Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.17/reference/targets/python_test.mdx b/versioned_docs/version-2.17/reference/targets/python_test.mdx index e040f391b..80e1f197c 100644 --- a/versioned_docs/version-2.17/reference/targets/python_test.mdx +++ b/versioned_docs/version-2.17/reference/targets/python_test.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -54,9 +54,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -159,11 +159,11 @@ When tests with the same `batch_compatibility_tag` have incompatibilities in som default_repr={`None`} > -Addresses to targets that can be built with the `scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run. +Addresses to targets that can be built with the `pants package` goal and whose resulting artifacts should be included in the test run. -Pants will build the artifacts as if you had run `scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). +Pants will build the artifacts as if you had run `pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). -You can include anything that can be built by `scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`. +You can include anything that can be built by `pants package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`. diff --git a/versioned_docs/version-2.17/reference/targets/python_test_utils.mdx b/versioned_docs/version-2.17/reference/targets/python_test_utils.mdx index 1474687d7..ac21edd4d 100644 --- a/versioned_docs/version-2.17/reference/targets/python_test_utils.mdx +++ b/versioned_docs/version-2.17/reference/targets/python_test_utils.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -286,9 +286,9 @@ The latter mode is similar to creating, activating, and using a virtual environm Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.17/reference/targets/python_tests.mdx b/versioned_docs/version-2.17/reference/targets/python_tests.mdx index 07f477808..5954c1084 100644 --- a/versioned_docs/version-2.17/reference/targets/python_tests.mdx +++ b/versioned_docs/version-2.17/reference/targets/python_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -270,9 +270,9 @@ If true, don't run Black on this target's code. Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -375,11 +375,11 @@ When tests with the same `batch_compatibility_tag` have incompatibilities in som default_repr={`None`} > -Addresses to targets that can be built with the `scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run. +Addresses to targets that can be built with the `pants package` goal and whose resulting artifacts should be included in the test run. -Pants will build the artifacts as if you had run `scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). +Pants will build the artifacts as if you had run `pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). -You can include anything that can be built by `scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`. +You can include anything that can be built by `pants package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`. diff --git a/versioned_docs/version-2.17/reference/targets/relocated_files.mdx b/versioned_docs/version-2.17/reference/targets/relocated_files.mdx index 62f3ec4e4..346339e69 100644 --- a/versioned_docs/version-2.17/reference/targets/relocated_files.mdx +++ b/versioned_docs/version-2.17/reference/targets/relocated_files.mdx @@ -61,7 +61,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -74,7 +74,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.17/reference/targets/remote_environment.mdx b/versioned_docs/version-2.17/reference/targets/remote_environment.mdx index e7ec0bea0..30f4785b7 100644 --- a/versioned_docs/version-2.17/reference/targets/remote_environment.mdx +++ b/versioned_docs/version-2.17/reference/targets/remote_environment.mdx @@ -32,7 +32,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -45,7 +45,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.17/reference/targets/resource.mdx b/versioned_docs/version-2.17/reference/targets/resource.mdx index 20ad5c110..d949720b9 100644 --- a/versioned_docs/version-2.17/reference/targets/resource.mdx +++ b/versioned_docs/version-2.17/reference/targets/resource.mdx @@ -26,7 +26,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -52,9 +52,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.17/reference/targets/resources.mdx b/versioned_docs/version-2.17/reference/targets/resources.mdx index 030e41877..27bbd3dbf 100644 --- a/versioned_docs/version-2.17/reference/targets/resources.mdx +++ b/versioned_docs/version-2.17/reference/targets/resources.mdx @@ -24,7 +24,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -94,9 +94,9 @@ You can specify the same file name in multiple keys, so long as you don't o Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.17/reference/targets/run_shell_command.mdx b/versioned_docs/version-2.17/reference/targets/run_shell_command.mdx index 96824cfac..bf8dfe79c 100644 --- a/versioned_docs/version-2.17/reference/targets/run_shell_command.mdx +++ b/versioned_docs/version-2.17/reference/targets/run_shell_command.mdx @@ -37,7 +37,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -50,7 +50,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.17/reference/targets/scala_junit_test.mdx b/versioned_docs/version-2.17/reference/targets/scala_junit_test.mdx index f439e428c..9dea5e3ce 100644 --- a/versioned_docs/version-2.17/reference/targets/scala_junit_test.mdx +++ b/versioned_docs/version-2.17/reference/targets/scala_junit_test.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.scala` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.17/reference/targets/scala_junit_tests.mdx b/versioned_docs/version-2.17/reference/targets/scala_junit_tests.mdx index b8eb058cb..c5f8293f1 100644 --- a/versioned_docs/version-2.17/reference/targets/scala_junit_tests.mdx +++ b/versioned_docs/version-2.17/reference/targets/scala_junit_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.scala` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -107,9 +107,9 @@ If unset, will default to `[test].timeout_default`; if that option is also unset Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.17/reference/targets/scala_source.mdx b/versioned_docs/version-2.17/reference/targets/scala_source.mdx index 064af7743..c793d55b1 100644 --- a/versioned_docs/version-2.17/reference/targets/scala_source.mdx +++ b/versioned_docs/version-2.17/reference/targets/scala_source.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.scala` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.17/reference/targets/scala_sources.mdx b/versioned_docs/version-2.17/reference/targets/scala_sources.mdx index ea659ce1a..d6c6f22c2 100644 --- a/versioned_docs/version-2.17/reference/targets/scala_sources.mdx +++ b/versioned_docs/version-2.17/reference/targets/scala_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.scala` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -106,9 +106,9 @@ If true, don't run `scalafmt` on this target's code. Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.17/reference/targets/scalac_plugin.mdx b/versioned_docs/version-2.17/reference/targets/scalac_plugin.mdx index 8ac0fa920..b67cbac68 100644 --- a/versioned_docs/version-2.17/reference/targets/scalac_plugin.mdx +++ b/versioned_docs/version-2.17/reference/targets/scalac_plugin.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.scala` @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.17/reference/targets/scalatest_test.mdx b/versioned_docs/version-2.17/reference/targets/scalatest_test.mdx index 9ecc3b752..3818e7eae 100644 --- a/versioned_docs/version-2.17/reference/targets/scalatest_test.mdx +++ b/versioned_docs/version-2.17/reference/targets/scalatest_test.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.scala` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.17/reference/targets/scalatest_tests.mdx b/versioned_docs/version-2.17/reference/targets/scalatest_tests.mdx index 425bed13f..5a528cdf5 100644 --- a/versioned_docs/version-2.17/reference/targets/scalatest_tests.mdx +++ b/versioned_docs/version-2.17/reference/targets/scalatest_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.scala` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -94,9 +94,9 @@ You can specify the same file name in multiple keys, so long as you don't o Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.17/reference/targets/shell_command.mdx b/versioned_docs/version-2.17/reference/targets/shell_command.mdx index f7dc848c2..507f27c3c 100644 --- a/versioned_docs/version-2.17/reference/targets/shell_command.mdx +++ b/versioned_docs/version-2.17/reference/targets/shell_command.mdx @@ -42,7 +42,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -55,7 +55,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.17/reference/targets/shell_source.mdx b/versioned_docs/version-2.17/reference/targets/shell_source.mdx index b9f175a73..adad94090 100644 --- a/versioned_docs/version-2.17/reference/targets/shell_source.mdx +++ b/versioned_docs/version-2.17/reference/targets/shell_source.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.17/reference/targets/shell_sources.mdx b/versioned_docs/version-2.17/reference/targets/shell_sources.mdx index b25b6f36e..512ca2d97 100644 --- a/versioned_docs/version-2.17/reference/targets/shell_sources.mdx +++ b/versioned_docs/version-2.17/reference/targets/shell_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -118,9 +118,9 @@ If true, don't run shfmt on this target's code. Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.17/reference/targets/shunit2_test.mdx b/versioned_docs/version-2.17/reference/targets/shunit2_test.mdx index e1053bf92..3a9c1c39c 100644 --- a/versioned_docs/version-2.17/reference/targets/shunit2_test.mdx +++ b/versioned_docs/version-2.17/reference/targets/shunit2_test.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -67,9 +67,9 @@ Path is relative to the BUILD file's directory, e.g. `source='example.ext'` Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -119,11 +119,11 @@ Which shell to run the tests with. If unspecified, Pants will look for a shebang default_repr={`None`} > -Addresses to targets that can be built with the `scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run. +Addresses to targets that can be built with the `pants package` goal and whose resulting artifacts should be included in the test run. -Pants will build the artifacts as if you had run `scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). +Pants will build the artifacts as if you had run `pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). -You can include anything that can be built by `scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`. +You can include anything that can be built by `pants package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`. diff --git a/versioned_docs/version-2.17/reference/targets/shunit2_tests.mdx b/versioned_docs/version-2.17/reference/targets/shunit2_tests.mdx index ac2f1cce0..c813e72cc 100644 --- a/versioned_docs/version-2.17/reference/targets/shunit2_tests.mdx +++ b/versioned_docs/version-2.17/reference/targets/shunit2_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -118,9 +118,9 @@ If true, don't run shfmt on this target's code. Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -170,11 +170,11 @@ Which shell to run the tests with. If unspecified, Pants will look for a shebang default_repr={`None`} > -Addresses to targets that can be built with the `scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run. +Addresses to targets that can be built with the `pants package` goal and whose resulting artifacts should be included in the test run. -Pants will build the artifacts as if you had run `scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). +Pants will build the artifacts as if you had run `pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). -You can include anything that can be built by `scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`. +You can include anything that can be built by `pants package`, e.g. a `pex_binary`, `python_awslambda`, or an `archive`. diff --git a/versioned_docs/version-2.17/reference/targets/system_binary.mdx b/versioned_docs/version-2.17/reference/targets/system_binary.mdx index 9920f16b2..d7bd775a0 100644 --- a/versioned_docs/version-2.17/reference/targets/system_binary.mdx +++ b/versioned_docs/version-2.17/reference/targets/system_binary.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.adhoc` @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.17/reference/targets/target.mdx b/versioned_docs/version-2.17/reference/targets/target.mdx index 5c137b750..c31ddeaed 100644 --- a/versioned_docs/version-2.17/reference/targets/target.mdx +++ b/versioned_docs/version-2.17/reference/targets/target.mdx @@ -26,7 +26,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -52,9 +52,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.17/reference/targets/terraform_module.mdx b/versioned_docs/version-2.17/reference/targets/terraform_module.mdx index 7c775e535..0f2ad9974 100644 --- a/versioned_docs/version-2.17/reference/targets/terraform_module.mdx +++ b/versioned_docs/version-2.17/reference/targets/terraform_module.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.terraform` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -54,9 +54,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.17/reference/targets/thrift_source.mdx b/versioned_docs/version-2.17/reference/targets/thrift_source.mdx index 0538c8a28..15a655891 100644 --- a/versioned_docs/version-2.17/reference/targets/thrift_source.mdx +++ b/versioned_docs/version-2.17/reference/targets/thrift_source.mdx @@ -27,7 +27,7 @@ Backend: `pants.backend.codegen.thrift.apache.p Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -40,7 +40,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -53,9 +53,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.17/reference/targets/thrift_sources.mdx b/versioned_docs/version-2.17/reference/targets/thrift_sources.mdx index d7ec2b55e..09d086a63 100644 --- a/versioned_docs/version-2.17/reference/targets/thrift_sources.mdx +++ b/versioned_docs/version-2.17/reference/targets/thrift_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.codegen.thrift.apache.p Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -109,9 +109,9 @@ All dependencies must share the same value for their `resolve` field. Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.17/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.17/reference/targets/vcs_version.mdx b/versioned_docs/version-2.17/reference/targets/vcs_version.mdx index ce5e65090..47b639217 100644 --- a/versioned_docs/version-2.17/reference/targets/vcs_version.mdx +++ b/versioned_docs/version-2.17/reference/targets/vcs_version.mdx @@ -30,7 +30,7 @@ Backend: `pants.backend.experimental.python` @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.18/reference/global-options.mdx b/versioned_docs/version-2.18/reference/global-options.mdx index 5d3ac712d..79ca384b6 100644 --- a/versioned_docs/version-2.18/reference/global-options.mdx +++ b/versioned_docs/version-2.18/reference/global-options.mdx @@ -317,9 +317,9 @@ ignore_warnings = [ Use this Pants version. Note that Pants only uses this to verify that you are using the requested version, as Pants cannot dynamically change the version it is using once the program is already running. -If you use the `scie-pants-linux-x86_64` script from https://www.pantsbuild.org/v2.18/docs/installation, however, changing the value in your `pants.toml` will cause the new version to be installed and run automatically. +If you use the `pants` script from https://www.pantsbuild.org/v2.18/docs/installation, however, changing the value in your `pants.toml` will cause the new version to be installed and run automatically. -Run `scie-pants-linux-x86_64 --version` to check what is being used. +Run `pants --version` to check what is being used. @@ -832,7 +832,7 @@ Whether or not to use nailgun to run JVM requests that are marked as supporting default_repr={`3`} > -The time in seconds to wait when gracefully shutting down an interactive process (such as one opened using `scie-pants-linux-x86_64 run`) before killing it. +The time in seconds to wait when gracefully shutting down an interactive process (such as one opened using `pants run`) before killing it. diff --git a/versioned_docs/version-2.18/reference/goals/experimental-bsp.mdx b/versioned_docs/version-2.18/reference/goals/experimental-bsp.mdx index 5362d9e2f..501fe81ee 100644 --- a/versioned_docs/version-2.18/reference/goals/experimental-bsp.mdx +++ b/versioned_docs/version-2.18/reference/goals/experimental-bsp.mdx @@ -79,7 +79,7 @@ Run the Build Server Protocol server. Pants will receive BSP RPC requests via th Environment variables to set in the BSP runner script when setting up BSP in a repository. Entries are either strings in the form `ENV_VAR=value` to set an explicit value; or just `ENV_VAR` to copy the value from Pants' own environment when the experimental-bsp goal was run. -This option only takes effect when the BSP runner script is written. If the option changes, you must run `scie-pants-linux-x86_64 experimental-bsp` again to write a new copy of the BSP runner script. +This option only takes effect when the BSP runner script is written. If the option changes, you must run `pants experimental-bsp` again to write a new copy of the BSP runner script. Note: The environment variables passed to the Pants BSP server will be those set for your IDE and not your shell. For example, on macOS, the IDE is generally launched by `launchd` after clicking on a Dock icon, and not from the shell. Thus, any environment variables set for your shell will likely not be seen by the Pants BSP server. At the very least, on macOS consider writing an explicit PATH into the BSP runner script via this option. diff --git a/versioned_docs/version-2.18/reference/goals/fix.mdx b/versioned_docs/version-2.18/reference/goals/fix.mdx index 1f996ab0d..7c7407fae 100644 --- a/versioned_docs/version-2.18/reference/goals/fix.mdx +++ b/versioned_docs/version-2.18/reference/goals/fix.mdx @@ -47,7 +47,7 @@ You can repeat this option, e.g. `fix --only=autoflake --only=pyupgrade` or `fix If true, skip running all formatters. -FYI: when running `scie-pants-linux-x86_64 fix fmt ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `fix` where possible. +FYI: when running `pants fix fmt ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `fix` where possible. diff --git a/versioned_docs/version-2.18/reference/goals/generate-lockfiles.mdx b/versioned_docs/version-2.18/reference/goals/generate-lockfiles.mdx index 4b1f0a8cb..022833e0f 100644 --- a/versioned_docs/version-2.18/reference/goals/generate-lockfiles.mdx +++ b/versioned_docs/version-2.18/reference/goals/generate-lockfiles.mdx @@ -33,7 +33,7 @@ Only generate lockfiles for the specified resolve(s). Resolves are the logical names for the different lockfiles used in your project. For your own code's dependencies, these come from backend-specific configuration such as `[python].resolves`. For tool lockfiles, resolve names are the options scope for that tool such as `black`, `pytest`, and `mypy-protobuf`. -For example, you can run `scie-pants-linux-x86_64 generate-lockfiles --resolve=black --resolve=pytest --resolve=data-science` to only generate lockfiles for those two tools and your resolve named `data-science`. +For example, you can run `pants generate-lockfiles --resolve=black --resolve=pytest --resolve=data-science` to only generate lockfiles for those two tools and your resolve named `data-science`. If you specify an invalid resolve name, like 'fake', Pants will output all possible values. @@ -75,7 +75,7 @@ Include unchanged distributions in the diff summary output. Implies `diff=true`. default_repr={`None`} > -If set, lockfile headers will say to run this command to regenerate the lockfile, rather than running `scie-pants-linux-x86_64 generate-lockfiles --resolve=` like normal. +If set, lockfile headers will say to run this command to regenerate the lockfile, rather than running `pants generate-lockfiles --resolve=` like normal. diff --git a/versioned_docs/version-2.18/reference/goals/lint.mdx b/versioned_docs/version-2.18/reference/goals/lint.mdx index 9607a4b8b..3ab192176 100644 --- a/versioned_docs/version-2.18/reference/goals/lint.mdx +++ b/versioned_docs/version-2.18/reference/goals/lint.mdx @@ -47,7 +47,7 @@ You can repeat this option, e.g. `lint --only=flake8 --only=shellcheck` or `lint If true, skip running all formatters in check-only mode. -FYI: when running `scie-pants-linux-x86_64 fmt lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `lint` where possible. +FYI: when running `pants fmt lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `lint` where possible. @@ -61,7 +61,7 @@ FYI: when running `scie-pants-linux-x86_64 fmt lint ::`, there should be diminis If true, skip running all fixers in check-only mode. -FYI: when running `scie-pants-linux-x86_64 fix lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fix` when running `lint` where possible. +FYI: when running `pants fix lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fix` when running `lint` where possible. diff --git a/versioned_docs/version-2.18/reference/help-all.json b/versioned_docs/version-2.18/reference/help-all.json index 8ece951f2..4e73ab870 100644 --- a/versioned_docs/version-2.18/reference/help-all.json +++ b/versioned_docs/version-2.18/reference/help-all.json @@ -205,7 +205,7 @@ "display_args": ["--[no-]add-trailing-comma-skip"], "env_var": "PANTS_ADD_TRAILING_COMMA_SKIP", "fromfile": false, - "help": "If true, don't use add-trailing-comma when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use add-trailing-comma when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -563,7 +563,7 @@ "display_args": ["--[no-]autoflake-skip"], "env_var": "PANTS_AUTOFLAKE_SKIP", "fromfile": false, - "help": "If true, don't use Autoflake when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Autoflake when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--autoflake-skip", "--no-autoflake-skip"], @@ -875,7 +875,7 @@ "display_args": ["--[no-]bandit-skip"], "env_var": "PANTS_BANDIT_SKIP", "fromfile": false, - "help": "If true, don't use Bandit when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Bandit when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--bandit-skip", "--no-bandit-skip"], @@ -930,7 +930,7 @@ { "details": "from env var PANTS_BIN_NAME", "rank": "ENVIRONMENT", - "value": "/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64" + "value": "/home/josh/work/scie-pants/dist/pants" } ] } @@ -1200,7 +1200,7 @@ "display_args": ["--[no-]black-skip"], "env_var": "PANTS_BLACK_SKIP", "fromfile": false, - "help": "If true, don't use Black when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Black when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--black-skip", "--no-black-skip"], @@ -1330,7 +1330,7 @@ "display_args": ["--[no-]buf-format-skip"], "env_var": "PANTS_BUF_FORMAT_SKIP", "fromfile": false, - "help": "If true, don't use Buf when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Buf when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--buf-format-skip", "--no-buf-format-skip"], @@ -1439,7 +1439,7 @@ "display_args": ["--[no-]buf-lint-skip"], "env_var": "PANTS_BUF_LINT_SKIP", "fromfile": false, - "help": "If true, don't use Buf when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Buf when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--buf-lint-skip", "--no-buf-lint-skip"], @@ -1696,7 +1696,7 @@ "display_args": ["--[no-]buildifier-skip"], "env_var": "PANTS_BUILDIFIER_SKIP", "fromfile": false, - "help": "If true, don't use Buildifier when running `scie-pants-linux-x86_64 fmt`.", + "help": "If true, don't use Buildifier when running `pants fmt`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--buildifier-skip", "--no-buildifier-skip"], @@ -1875,7 +1875,7 @@ "display_args": ["--[no-]build-deprecations-fixer-skip"], "env_var": "PANTS_BUILD_DEPRECATIONS_FIXER_SKIP", "fromfile": false, - "help": "If true, don't use BUILD Deprecations Fixer when running `scie-pants-linux-x86_64 fix`.", + "help": "If true, don't use BUILD Deprecations Fixer when running `pants fix`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -2228,7 +2228,7 @@ "display_args": ["--cli-alias=\"{'key1': val1, 'key2': val2, ...}\""], "env_var": "PANTS_CLI_ALIAS", "fromfile": false, - "help": "Register command line aliases.\n\nExample:\n\n [cli.alias]\n green = \"fmt lint check\"\n all-changed = \"--changed-since=HEAD --changed-dependents=transitive\"\n\nThis would allow you to run `scie-pants-linux-x86_64 green all-changed`, which is shorthand for `scie-pants-linux-x86_64 fmt lint check --changed-since=HEAD --changed-dependents=transitive`.\n\nNotice: this option must be placed in a config file (e.g. `pants.toml` or `pantsrc`) to have any effect.", + "help": "Register command line aliases.\n\nExample:\n\n [cli.alias]\n green = \"fmt lint check\"\n all-changed = \"--changed-since=HEAD --changed-dependents=transitive\"\n\nThis would allow you to run `pants green all-changed`, which is shorthand for `pants fmt lint check --changed-since=HEAD --changed-dependents=transitive`.\n\nNotice: this option must be placed in a config file (e.g. `pants.toml` or `pantsrc`) to have any effect.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--cli-alias"], @@ -3868,7 +3868,7 @@ "display_args": ["--[no-]docformatter-skip"], "env_var": "PANTS_DOCFORMATTER_SKIP", "fromfile": false, - "help": "If true, don't use docformatter when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use docformatter when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--docformatter-skip", "--no-docformatter-skip"], @@ -4371,7 +4371,7 @@ "display_args": ["--docker-run-args=\"[, , ...]\""], "env_var": "PANTS_DOCKER_RUN_ARGS", "fromfile": false, - "help": "Additional arguments to use for `docker run` invocations.\n\nExample:\n\n $ scie-pants-linux-x86_64 run --docker-run-args=\"-p 127.0.0.1:80:8080/tcp --name demo\" src/example:image -- [image entrypoint args]\n\nTo provide the top-level options to the `docker` client, use `[docker].env_vars` to configure the [Environment variables](https://docs.docker.com/engine/reference/commandline/cli/#environment-variables) as appropriate.\n\nThe arguments for the image entrypoint may be passed on the command line after a double dash (`--`), or using the `--run-args` option.\n\nDefaults to `--interactive --tty` when stdout is connected to a terminal.", + "help": "Additional arguments to use for `docker run` invocations.\n\nExample:\n\n $ pants run --docker-run-args=\"-p 127.0.0.1:80:8080/tcp --name demo\" src/example:image -- [image entrypoint args]\n\nTo provide the top-level options to the `docker` client, use `[docker].env_vars` to configure the [Environment variables](https://docs.docker.com/engine/reference/commandline/cli/#environment-variables) as appropriate.\n\nThe arguments for the image entrypoint may be passed on the command line after a double dash (`--`), or using the `--run-args` option.\n\nDefaults to `--interactive --tty` when stdout is connected to a terminal.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--docker-run-args"], @@ -5270,7 +5270,7 @@ ], "env_var": "PANTS_EXPERIMENTAL_BSP_RUNNER_ENV_VARS", "fromfile": false, - "help": "Environment variables to set in the BSP runner script when setting up BSP in a repository. Entries are either strings in the form `ENV_VAR=value` to set an explicit value; or just `ENV_VAR` to copy the value from Pants' own environment when the experimental-bsp goal was run.\n\nThis option only takes effect when the BSP runner script is written. If the option changes, you must run `scie-pants-linux-x86_64 experimental-bsp` again to write a new copy of the BSP runner script.\n\nNote: The environment variables passed to the Pants BSP server will be those set for your IDE and not your shell. For example, on macOS, the IDE is generally launched by `launchd` after clicking on a Dock icon, and not from the shell. Thus, any environment variables set for your shell will likely not be seen by the Pants BSP server. At the very least, on macOS consider writing an explicit PATH into the BSP runner script via this option.", + "help": "Environment variables to set in the BSP runner script when setting up BSP in a repository. Entries are either strings in the form `ENV_VAR=value` to set an explicit value; or just `ENV_VAR` to copy the value from Pants' own environment when the experimental-bsp goal was run.\n\nThis option only takes effect when the BSP runner script is written. If the option changes, you must run `pants experimental-bsp` again to write a new copy of the BSP runner script.\n\nNote: The environment variables passed to the Pants BSP server will be those set for your IDE and not your shell. For example, on macOS, the IDE is generally launched by `launchd` after clicking on a Dock icon, and not from the shell. Thus, any environment variables set for your shell will likely not be seen by the Pants BSP server. At the very least, on macOS consider writing an explicit PATH into the BSP runner script via this option.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--experimental-bsp-runner-env-vars"], @@ -5975,7 +5975,7 @@ "display_args": ["--[no-]fix-skip-formatters"], "env_var": "PANTS_FIX_SKIP_FORMATTERS", "fromfile": false, - "help": "If true, skip running all formatters.\n\nFYI: when running `scie-pants-linux-x86_64 fix fmt ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `fix` where possible.", + "help": "If true, skip running all formatters.\n\nFYI: when running `pants fix fmt ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `fix` where possible.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -6265,7 +6265,7 @@ "display_args": ["--[no-]flake8-skip"], "env_var": "PANTS_FLAKE8_SKIP", "fromfile": false, - "help": "If true, don't use Flake8 when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Flake8 when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--flake8-skip", "--no-flake8-skip"], @@ -6399,7 +6399,7 @@ "display_args": ["--generate-lockfiles-custom-command="], "env_var": "PANTS_GENERATE_LOCKFILES_CUSTOM_COMMAND", "fromfile": false, - "help": "If set, lockfile headers will say to run this command to regenerate the lockfile, rather than running `scie-pants-linux-x86_64 generate-lockfiles --resolve=` like normal.", + "help": "If set, lockfile headers will say to run this command to regenerate the lockfile, rather than running `pants generate-lockfiles --resolve=` like normal.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--generate-lockfiles-custom-command"], @@ -6504,7 +6504,7 @@ ], "env_var": "PANTS_GENERATE_LOCKFILES_RESOLVE", "fromfile": false, - "help": "Only generate lockfiles for the specified resolve(s).\n\nResolves are the logical names for the different lockfiles used in your project. For your own code's dependencies, these come from backend-specific configuration such as `[python].resolves`. For tool lockfiles, resolve names are the options scope for that tool such as `black`, `pytest`, and `mypy-protobuf`.\n\nFor example, you can run `scie-pants-linux-x86_64 generate-lockfiles --resolve=black --resolve=pytest --resolve=data-science` to only generate lockfiles for those two tools and your resolve named `data-science`.\n\nIf you specify an invalid resolve name, like 'fake', Pants will output all possible values.\n\nIf not specified, Pants will generate lockfiles for all resolves.", + "help": "Only generate lockfiles for the specified resolve(s).\n\nResolves are the logical names for the different lockfiles used in your project. For your own code's dependencies, these come from backend-specific configuration such as `[python].resolves`. For tool lockfiles, resolve names are the options scope for that tool such as `black`, `pytest`, and `mypy-protobuf`.\n\nFor example, you can run `pants generate-lockfiles --resolve=black --resolve=pytest --resolve=data-science` to only generate lockfiles for those two tools and your resolve named `data-science`.\n\nIf you specify an invalid resolve name, like 'fake', Pants will output all possible values.\n\nIf not specified, Pants will generate lockfiles for all resolves.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--generate-lockfiles-resolve"], @@ -6570,7 +6570,7 @@ "display_args": ["--[no-]gofmt-skip"], "env_var": "PANTS_GOFMT_SKIP", "fromfile": false, - "help": "If true, don't use gofmt when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use gofmt when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--gofmt-skip", "--no-gofmt-skip"], @@ -7332,7 +7332,7 @@ "display_args": ["--google-java-format-lockfile="], "env_var": "PANTS_GOOGLE_JAVA_FORMAT_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.18.0rc5/src/python/pants/backend/java/lint/google_java_format/google_java_format.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=google-java-format`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.18.0rc5/src/python/pants/backend/java/lint/google_java_format/google_java_format.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=google-java-format`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--google-java-format-lockfile"], @@ -7365,7 +7365,7 @@ "display_args": ["--[no-]google-java-format-skip"], "env_var": "PANTS_GOOGLE_JAVA_FORMAT_SKIP", "fromfile": false, - "help": "If true, don't use Google Java Format when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Google Java Format when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -7931,7 +7931,7 @@ "display_args": ["--[no-]go-test-skip"], "env_var": "PANTS_GO_TEST_SKIP", "fromfile": false, - "help": "If true, don't use Go test binary when running `scie-pants-linux-x86_64 test`.", + "help": "If true, don't use Go test binary when running `pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--go-test-skip", "--no-go-test-skip"], @@ -8328,7 +8328,7 @@ "display_args": ["--[no-]hadolint-skip"], "env_var": "PANTS_HADOLINT_SKIP", "fromfile": false, - "help": "If true, don't use Hadolint when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Hadolint when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--hadolint-skip", "--no-hadolint-skip"], @@ -9188,7 +9188,7 @@ "display_args": ["--[no-]helm-unittest-skip"], "env_var": "PANTS_HELM_UNITTEST_SKIP", "fromfile": false, - "help": "If true, don't use helmunittestsubsystem when running `scie-pants-linux-x86_64 test`.", + "help": "If true, don't use helmunittestsubsystem when running `pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -10040,7 +10040,7 @@ "display_args": ["--[no-]isort-skip"], "env_var": "PANTS_ISORT_SKIP", "fromfile": false, - "help": "If true, don't use isort when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use isort when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--isort-skip", "--no-isort-skip"], @@ -10139,7 +10139,7 @@ "display_args": ["--jarjar-lockfile="], "env_var": "PANTS_JARJAR_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.18.0rc5/src/python/pants/jvm/shading/jarjar.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=jarjar`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.18.0rc5/src/python/pants/jvm/shading/jarjar.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=jarjar`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--jarjar-lockfile"], @@ -10560,7 +10560,7 @@ "display_args": ["--junit-lockfile="], "env_var": "PANTS_JUNIT_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.18.0rc5/src/python/pants/jvm/test/junit.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=junit`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.18.0rc5/src/python/pants/jvm/test/junit.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=junit`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--junit-lockfile"], @@ -10593,7 +10593,7 @@ "display_args": ["--[no-]junit-skip"], "env_var": "PANTS_JUNIT_SKIP", "fromfile": false, - "help": "If true, don't use JUnit when running `scie-pants-linux-x86_64 test`.", + "help": "If true, don't use JUnit when running `pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--junit-skip", "--no-junit-skip"], @@ -11246,7 +11246,7 @@ "display_args": ["--ktlint-lockfile="], "env_var": "PANTS_KTLINT_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.18.0rc5/src/python/pants/backend/kotlin/lint/ktlint/ktlint.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=ktlint`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.18.0rc5/src/python/pants/backend/kotlin/lint/ktlint/ktlint.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=ktlint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--ktlint-lockfile"], @@ -11279,7 +11279,7 @@ "display_args": ["--[no-]ktlint-skip"], "env_var": "PANTS_KTLINT_SKIP", "fromfile": false, - "help": "If true, don't use Ktlint when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Ktlint when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--ktlint-skip", "--no-ktlint-skip"], @@ -11634,7 +11634,7 @@ "display_args": ["--[no-]lint-skip-fixers"], "env_var": "PANTS_LINT_SKIP_FIXERS", "fromfile": false, - "help": "If true, skip running all fixers in check-only mode.\n\nFYI: when running `scie-pants-linux-x86_64 fix lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fix` when running `lint` where possible.", + "help": "If true, skip running all fixers in check-only mode.\n\nFYI: when running `pants fix lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fix` when running `lint` where possible.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--lint-skip-fixers", "--no-lint-skip-fixers"], @@ -11667,7 +11667,7 @@ "display_args": ["--[no-]lint-skip-formatters"], "env_var": "PANTS_LINT_SKIP_FORMATTERS", "fromfile": false, - "help": "If true, skip running all formatters in check-only mode.\n\nFYI: when running `scie-pants-linux-x86_64 fmt lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `lint` where possible.", + "help": "If true, skip running all formatters in check-only mode.\n\nFYI: when running `pants fmt lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `lint` where possible.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -12548,7 +12548,7 @@ "display_args": ["--[no-]mypy-skip"], "env_var": "PANTS_MYPY_SKIP", "fromfile": false, - "help": "If true, don't use MyPy when running `scie-pants-linux-x86_64 check`.", + "help": "If true, don't use MyPy when running `pants check`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--mypy-skip", "--no-mypy-skip"], @@ -12911,7 +12911,7 @@ ], "env_var": "PANTS_NODEJS_RESOLVES", "fromfile": false, - "help": "A mapping of names to lockfile paths used in your project.\n\nSpecifying a resolve name is optional. If unspecified, the default resolve name is calculated by taking the path from the source root to the directory containing the lockfile and replacing '/' with '.' in that path.\n\nExample: An npm lockfile located at `src/js/package/package-lock.json' will result in a resolve named `js.package`, assuming src/ is a source root.\n\nRun `scie-pants-linux-x86_64 generate-lockfiles` to generate the lockfile(s).", + "help": "A mapping of names to lockfile paths used in your project.\n\nSpecifying a resolve name is optional. If unspecified, the default resolve name is calculated by taking the path from the source root to the directory containing the lockfile and replacing '/' with '.' in that path.\n\nExample: An npm lockfile located at `src/js/package/package-lock.json' will result in a resolve named `js.package`, assuming src/ is a source root.\n\nRun `pants generate-lockfiles` to generate the lockfile(s).", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--nodejs-resolves"], @@ -14002,7 +14002,7 @@ "display_args": ["--[no-]preamble-skip"], "env_var": "PANTS_PREAMBLE_SKIP", "fromfile": false, - "help": "If true, don't use preamble when running `scie-pants-linux-x86_64 fmt`.", + "help": "If true, don't use preamble when running `pants fmt`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--preamble-skip", "--no-preamble-skip"], @@ -14164,7 +14164,7 @@ "display_args": ["--process-execution-graceful-shutdown-timeout="], "env_var": "PANTS_PROCESS_EXECUTION_GRACEFUL_SHUTDOWN_TIMEOUT", "fromfile": false, - "help": "The time in seconds to wait when gracefully shutting down an interactive process (such as one opened using `scie-pants-linux-x86_64 run`) before killing it.", + "help": "The time in seconds to wait when gracefully shutting down an interactive process (such as one opened using `pants run`) before killing it.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--process-execution-graceful-shutdown-timeout"], @@ -14445,7 +14445,7 @@ "display_args": ["--protobuf-java-grpc-lockfile="], "env_var": "PANTS_PROTOBUF_JAVA_GRPC_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.18.0rc5/src/python/pants/backend/codegen/protobuf/java/grpc-java.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=protobuf-java-grpc`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.18.0rc5/src/python/pants/backend/codegen/protobuf/java/grpc-java.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=protobuf-java-grpc`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--protobuf-java-grpc-lockfile"], @@ -15054,7 +15054,7 @@ "display_args": ["--[no-]pydocstyle-skip"], "env_var": "PANTS_PYDOCSTYLE_SKIP", "fromfile": false, - "help": "If true, don't use Pydocstyle when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Pydocstyle when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pydocstyle-skip", "--no-pydocstyle-skip"], @@ -15306,7 +15306,7 @@ "display_args": ["--[no-]pylint-skip"], "env_var": "PANTS_PYLINT_SKIP", "fromfile": false, - "help": "If true, don't use Pylint when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Pylint when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pylint-skip", "--no-pylint-skip"], @@ -15847,7 +15847,7 @@ "display_args": ["--[no-]pytest-skip"], "env_var": "PANTS_PYTEST_SKIP", "fromfile": false, - "help": "If true, don't use Pytest when running `scie-pants-linux-x86_64 test`.", + "help": "If true, don't use Pytest when running `pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pytest-skip", "--no-pytest-skip"], @@ -16527,7 +16527,7 @@ "display_args": ["--python-infer-init-files="], "env_var": "PANTS_PYTHON_INFER_INIT_FILES", "fromfile": false, - "help": "Infer a target's dependencies on any `__init__.py` files in the packages it is located in (recursively upward in the directory structure).\n\nEven if this is set to `never` or `content_only`, Pants will still always include any ancestor `__init__.py` files in the sandbox. Only, they will not be \"proper\" dependencies, e.g. they will not show up in `scie-pants-linux-x86_64 dependencies` and their own dependencies will not be used.\n\nBy default, Pants only adds a \"proper\" dependency if there is content in the `__init__.py` file. This makes sure that dependencies are added when likely necessary to build, while also avoiding adding unnecessary dependencies. While accurate, those unnecessary dependencies can complicate setting metadata like the `interpreter_constraints` and `resolve` fields.", + "help": "Infer a target's dependencies on any `__init__.py` files in the packages it is located in (recursively upward in the directory structure).\n\nEven if this is set to `never` or `content_only`, Pants will still always include any ancestor `__init__.py` files in the sandbox. Only, they will not be \"proper\" dependencies, e.g. they will not show up in `pants dependencies` and their own dependencies will not be used.\n\nBy default, Pants only adds a \"proper\" dependency if there is content in the `__init__.py` file. This makes sure that dependencies are added when likely necessary to build, while also avoiding adding unnecessary dependencies. While accurate, those unnecessary dependencies can complicate setting metadata like the `interpreter_constraints` and `resolve` fields.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--python-infer-init-files"], @@ -16664,7 +16664,7 @@ "display_args": ["--[no-]python-infer-use-rust-parser"], "env_var": "PANTS_PYTHON_INFER_USE_RUST_PARSER", "fromfile": false, - "help": "Use the new Rust-based, multithreaded, in-process dependency parser.\n\nPants 2.17 introduced a new paradigm to dependency parsing for Python by leveraging a Rust-based parser that's called in the same process as Pants itself, instead of farming out to one-python-process-per-file.\n\nAs a result of the switch, cold-cache performance improved by a factor of about 12x, while hot-cache had no difference. Additionally, Pants can now infer dependencies from Python scripts with syntax errors.\n\nAfter leaving this defaulted to disabled for a release cycle, Pants 2.18 started defaulting to enabling this.\n\nIf you think the new behaviour is causing problems, it is recommended that you run `scie-pants-linux-x86_64 peek :: > before.json` and then `scie-pants-linux-x86_64 --python-infer-use-rust-parser=False peek :: > after.json` and compare the two results.\n\nIf you think there is a bug and need to disable it, please file an issue: https://github.com/pantsbuild/pants/issues/new/choose.", + "help": "Use the new Rust-based, multithreaded, in-process dependency parser.\n\nPants 2.17 introduced a new paradigm to dependency parsing for Python by leveraging a Rust-based parser that's called in the same process as Pants itself, instead of farming out to one-python-process-per-file.\n\nAs a result of the switch, cold-cache performance improved by a factor of about 12x, while hot-cache had no difference. Additionally, Pants can now infer dependencies from Python scripts with syntax errors.\n\nAfter leaving this defaulted to disabled for a release cycle, Pants 2.18 started defaulting to enabling this.\n\nIf you think the new behaviour is causing problems, it is recommended that you run `pants peek :: > before.json` and then `pants --python-infer-use-rust-parser=False peek :: > after.json` and compare the two results.\n\nIf you think there is a bug and need to disable it, please file an issue: https://github.com/pantsbuild/pants/issues/new/choose.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -17224,7 +17224,7 @@ "env_var": "PANTS_PYTHON_REQUIREMENT_CONSTRAINTS", "fromfile": false, "help": "When resolving third-party requirements for your own code (vs. tools you run), use this constraints file to determine which versions to use.\n\nMutually exclusive with `[python].enable_resolves`, which we generally recommend as an improvement over constraints file.\n\nSee https://pip.pypa.io/en/stable/user_guide/#constraints-files for more information on the format of constraint files and how constraints are applied in Pex and pip.\n\nThis only applies when resolving user requirements, rather than tools you run like Black and Pytest. To constrain tools, set `[tool].lockfile`, e.g. `[black].lockfile`.", - "removal_hint": "We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.\n\nTo migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `scie-pants-linux-x86_64 generate-lockfiles`.", + "removal_hint": "We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.\n\nTo migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `pants generate-lockfiles`.", "removal_version": "3.0.0.dev0", "scoped_cmd_line_args": ["--python-requirement-constraints"], "target_field_name": null, @@ -17288,7 +17288,7 @@ ], "env_var": "PANTS_PYTHON_RESOLVES", "fromfile": false, - "help": "A mapping of logical names to lockfile paths used in your project.\n\nMany organizations only need a single resolve for their whole project, which is a good default and often the simplest thing to do. However, you may need multiple resolves, such as if you use two conflicting versions of a requirement in your repository.\n\nIf you only need a single resolve, run `scie-pants-linux-x86_64 generate-lockfiles` to generate the lockfile.\n\nIf you need multiple resolves:\n\n 1. Via this option, define multiple resolve names and their lockfile paths. The names should be meaningful to your repository, such as `data-science` or `pants-plugins`.\n 2. Set the default with `[python].default_resolve`.\n 3. Update your `python_requirement` targets with the `resolve` field to declare which resolve they should be available in. They default to `[python].default_resolve`, so you only need to update targets that you want in non-default resolves. (Often you'll set this via the `python_requirements` or `poetry_requirements` target generators)\n 4. Run `scie-pants-linux-x86_64 generate-lockfiles` to generate the lockfiles. If the results aren't what you'd expect, adjust the prior step.\n 5. Update any targets like `python_source` / `python_sources`, `python_test` / `python_tests`, and `pex_binary` which need to set a non-default resolve with the `resolve` field.\n\nIf a target can work with multiple resolves, you can either use the `parametrize` mechanism or manually create a distinct target per resolve. See https://www.pantsbuild.org/v2.18/docs/targets for information about `parametrize`.\n\nFor example:\n\n python_sources(\n resolve=parametrize(\"data-science\", \"web-app\"),\n )\n\nYou can name the lockfile paths what you would like; Pants does not expect a certain file extension or location.\n\nOnly applies if `[python].enable_resolves` is true.", + "help": "A mapping of logical names to lockfile paths used in your project.\n\nMany organizations only need a single resolve for their whole project, which is a good default and often the simplest thing to do. However, you may need multiple resolves, such as if you use two conflicting versions of a requirement in your repository.\n\nIf you only need a single resolve, run `pants generate-lockfiles` to generate the lockfile.\n\nIf you need multiple resolves:\n\n 1. Via this option, define multiple resolve names and their lockfile paths. The names should be meaningful to your repository, such as `data-science` or `pants-plugins`.\n 2. Set the default with `[python].default_resolve`.\n 3. Update your `python_requirement` targets with the `resolve` field to declare which resolve they should be available in. They default to `[python].default_resolve`, so you only need to update targets that you want in non-default resolves. (Often you'll set this via the `python_requirements` or `poetry_requirements` target generators)\n 4. Run `pants generate-lockfiles` to generate the lockfiles. If the results aren't what you'd expect, adjust the prior step.\n 5. Update any targets like `python_source` / `python_sources`, `python_test` / `python_tests`, and `pex_binary` which need to set a non-default resolve with the `resolve` field.\n\nIf a target can work with multiple resolves, you can either use the `parametrize` mechanism or manually create a distinct target per resolve. See https://www.pantsbuild.org/v2.18/docs/targets for information about `parametrize`.\n\nFor example:\n\n python_sources(\n resolve=parametrize(\"data-science\", \"web-app\"),\n )\n\nYou can name the lockfile paths what you would like; Pants does not expect a certain file extension or location.\n\nOnly applies if `[python].enable_resolves` is true.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--python-resolves"], @@ -17503,7 +17503,7 @@ "env_var": "PANTS_PYTHON_RESOLVE_ALL_CONSTRAINTS", "fromfile": false, "help": "(Only relevant when using `[python].requirement_constraints.`) If enabled, when resolving requirements, Pants will first resolve your entire constraints file as a single global resolve. Then, if the code uses a subset of your constraints file, Pants will extract the relevant requirements from that global resolve so that only what's actually needed gets used. If disabled, Pants will not use a global resolve and will resolve each subset of your requirements independently.\n\nUsually this option should be enabled because it can result in far fewer resolves.", - "removal_hint": "We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.\n\nTo migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `scie-pants-linux-x86_64 generate-lockfiles`.", + "removal_hint": "We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.\n\nTo migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `pants generate-lockfiles`.", "removal_version": "3.0.0.dev0", "scoped_cmd_line_args": [ "--python-resolve-all-constraints", @@ -18065,7 +18065,7 @@ "display_args": ["--[no-]pytype-skip"], "env_var": "PANTS_PYTYPE_SKIP", "fromfile": false, - "help": "If true, don't use Pytype when running `scie-pants-linux-x86_64 check`.", + "help": "If true, don't use Pytype when running `pants check`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pytype-skip", "--no-pytype-skip"], @@ -18288,7 +18288,7 @@ "display_args": ["--[no-]pyupgrade-skip"], "env_var": "PANTS_PYUPGRADE_SKIP", "fromfile": false, - "help": "If true, don't use pyupgrade when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use pyupgrade when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pyupgrade-skip", "--no-pyupgrade-skip"], @@ -18453,7 +18453,7 @@ "display_args": ["--[no-]regex-lint-skip"], "env_var": "PANTS_REGEX_LINT_SKIP", "fromfile": false, - "help": "If true, don't use regex-lint when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use regex-lint when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--regex-lint-skip", "--no-regex-lint-skip"], @@ -19705,7 +19705,7 @@ "display_args": ["--[no-]ruff-skip"], "env_var": "PANTS_RUFF_SKIP", "fromfile": false, - "help": "If true, don't use Ruff when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Ruff when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--ruff-skip", "--no-ruff-skip"], @@ -20002,7 +20002,7 @@ "display_args": ["--scalafmt-lockfile="], "env_var": "PANTS_SCALAFMT_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.18.0rc5/src/python/pants/backend/scala/lint/scalafmt/scalafmt.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalafmt`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.18.0rc5/src/python/pants/backend/scala/lint/scalafmt/scalafmt.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=scalafmt`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalafmt-lockfile"], @@ -20035,7 +20035,7 @@ "display_args": ["--[no-]scalafmt-skip"], "env_var": "PANTS_SCALAFMT_SKIP", "fromfile": false, - "help": "If true, don't use scalafmt when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use scalafmt when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalafmt-skip", "--no-scalafmt-skip"], @@ -20200,7 +20200,7 @@ "display_args": ["--scalapb-lockfile="], "env_var": "PANTS_SCALAPB_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.18.0rc5/src/python/pants/backend/codegen/protobuf/scala/scalapbc.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalapb`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.18.0rc5/src/python/pants/backend/codegen/protobuf/scala/scalapbc.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=scalapb`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalapb-lockfile"], @@ -20368,7 +20368,7 @@ "display_args": ["--scalatest-lockfile="], "env_var": "PANTS_SCALATEST_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.18.0rc5/src/python/pants/backend/scala/subsystems/scalatest.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalatest`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.18.0rc5/src/python/pants/backend/scala/subsystems/scalatest.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=scalatest`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalatest-lockfile"], @@ -20401,7 +20401,7 @@ "display_args": ["--[no-]scalatest-skip"], "env_var": "PANTS_SCALATEST_SKIP", "fromfile": false, - "help": "If true, don't use Scalatest when running `scie-pants-linux-x86_64 test`.", + "help": "If true, don't use Scalatest when running `pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalatest-skip", "--no-scalatest-skip"], @@ -21356,7 +21356,7 @@ "display_args": ["--[no-]shellcheck-skip"], "env_var": "PANTS_SHELLCHECK_SKIP", "fromfile": false, - "help": "If true, don't use Shellcheck when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Shellcheck when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--shellcheck-skip", "--no-shellcheck-skip"], @@ -21645,7 +21645,7 @@ "display_args": ["--[no-]shell-test-skip"], "env_var": "PANTS_SHELL_TEST_SKIP", "fromfile": false, - "help": "If true, don't use Test with shell scripts when running `scie-pants-linux-x86_64 test`.", + "help": "If true, don't use Test with shell scripts when running `pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--shell-test-skip", "--no-shell-test-skip"], @@ -21798,7 +21798,7 @@ "display_args": ["--[no-]shfmt-skip"], "env_var": "PANTS_SHFMT_SKIP", "fromfile": false, - "help": "If true, don't use shfmt when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use shfmt when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--shfmt-skip", "--no-shfmt-skip"], @@ -22053,7 +22053,7 @@ "display_args": ["--[no-]shunit2-skip"], "env_var": "PANTS_SHUNIT2_SKIP", "fromfile": false, - "help": "If true, don't use shunit2 when running `scie-pants-linux-x86_64 test`.", + "help": "If true, don't use shunit2 when running `pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--shunit2-skip", "--no-shunit2-skip"], @@ -22368,7 +22368,7 @@ "display_args": ["--[no-]spectral-skip"], "env_var": "PANTS_SPECTRAL_SKIP", "fromfile": false, - "help": "If true, don't use Spectral when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Spectral when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--spectral-skip", "--no-spectral-skip"], @@ -23052,7 +23052,7 @@ "display_args": ["--[no-]terraform-fmt-skip"], "env_var": "PANTS_TERRAFORM_FMT_SKIP", "fromfile": false, - "help": "If true, don't use `terraform fmt` when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use `terraform fmt` when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -23188,7 +23188,7 @@ "display_args": ["--[no-]terraform-validate-skip"], "env_var": "PANTS_TERRAFORM_VALIDATE_SKIP", "fromfile": false, - "help": "If true, don't use `terraform validate` when running `scie-pants-linux-x86_64 check`.", + "help": "If true, don't use `terraform validate` when running `pants check`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -24041,7 +24041,7 @@ "display_args": ["--[no-]twine-skip"], "env_var": "PANTS_TWINE_SKIP", "fromfile": false, - "help": "If true, don't use Twine when running `scie-pants-linux-x86_64 publish`.", + "help": "If true, don't use Twine when running `pants publish`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--twine-skip", "--no-twine-skip"], @@ -24317,7 +24317,7 @@ "display_args": ["--pants-version="], "env_var": "PANTS_VERSION", "fromfile": false, - "help": "Use this Pants version. Note that Pants only uses this to verify that you are using the requested version, as Pants cannot dynamically change the version it is using once the program is already running.\n\nIf you use the `scie-pants-linux-x86_64` script from https://www.pantsbuild.org/v2.18/docs/installation, however, changing the value in your `pants.toml` will cause the new version to be installed and run automatically.\n\nRun `scie-pants-linux-x86_64 --version` to check what is being used.", + "help": "Use this Pants version. Note that Pants only uses this to verify that you are using the requested version, as Pants cannot dynamically change the version it is using once the program is already running.\n\nIf you use the `pants` script from https://www.pantsbuild.org/v2.18/docs/installation, however, changing the value in your `pants.toml` will cause the new version to be installed and run automatically.\n\nRun `pants --version` to check what is being used.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pants-version"], @@ -24779,7 +24779,7 @@ "display_args": ["--[no-]yamllint-skip"], "env_var": "PANTS_YAMLLINT_SKIP", "fromfile": false, - "help": "If true, don't use Yamllint when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Yamllint when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--yamllint-skip", "--no-yamllint-skip"], @@ -25066,7 +25066,7 @@ "display_args": ["--[no-]yapf-skip"], "env_var": "PANTS_YAPF_SKIP", "fromfile": false, - "help": "If true, don't use yapf when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use yapf when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--yapf-skip", "--no-yapf-skip"], @@ -63172,7 +63172,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -63180,7 +63180,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -63204,7 +63204,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -63212,7 +63212,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -63228,7 +63228,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -63244,7 +63244,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -63252,7 +63252,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -63268,7 +63268,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -63284,7 +63284,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -63292,7 +63292,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -63428,7 +63428,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -63436,7 +63436,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -63444,7 +63444,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -63452,7 +63452,7 @@ { "alias": "packages", "default": null, - "description": "Addresses to any targets that can be built with `scie-pants-linux-x86_64 package`, e.g. `[\"project:app\"]`.\n\nPants will build the assets as if you had run `scie-pants-linux-x86_64 package`. It will include the results in your archive using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_aws_lambda_function`, or even another `archive`.", + "description": "Addresses to any targets that can be built with `pants package`, e.g. `[\"project:app\"]`.\n\nPants will build the assets as if you had run `pants package`. It will include the results in your archive using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `pants package`, e.g. a `pex_binary`, `python_aws_lambda_function`, or even another `archive`.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -63484,7 +63484,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -63492,7 +63492,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -63508,7 +63508,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -63516,7 +63516,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -63580,7 +63580,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -63588,7 +63588,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -63844,7 +63844,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -63852,7 +63852,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -63868,7 +63868,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -63956,7 +63956,7 @@ { "alias": "skip_push", "default": "False", - "description": "If true, do not push this image to registries when running `scie-pants-linux-x86_64 publish`.", + "description": "If true, do not push this image to registries when running `pants publish`.", "provider": "", "required": false, "type_hint": "bool" @@ -64004,7 +64004,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -64036,7 +64036,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -64044,7 +64044,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -64132,7 +64132,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -64140,7 +64140,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -64172,7 +64172,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -64180,7 +64180,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -64212,7 +64212,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -64220,7 +64220,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -64252,7 +64252,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -64260,7 +64260,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -64292,7 +64292,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -64300,7 +64300,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -64332,7 +64332,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -64340,7 +64340,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -64372,7 +64372,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -64380,7 +64380,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -64388,7 +64388,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -64412,7 +64412,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -64420,7 +64420,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -64444,7 +64444,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -64460,7 +64460,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -64468,7 +64468,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -64476,7 +64476,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -64572,7 +64572,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -64580,7 +64580,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -64652,7 +64652,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -64660,7 +64660,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -64668,7 +64668,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -64764,7 +64764,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -64772,7 +64772,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -64780,7 +64780,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -64804,7 +64804,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -64812,7 +64812,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -64860,7 +64860,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -64868,7 +64868,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -64892,7 +64892,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -64900,7 +64900,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built directory tree should be located.\n\nIf undefined, this will use the path to the BUILD file, For example, `src/charts/mychart:tgt_name` would be `src.charts.mychart/tgt_name/`.\n\nRegardless of whether you use the default or set this field, the path will end with Helms's file format of `-.tgz`, where `chart_name` and `chart_version` are the values extracted from the Chart.yaml file. So, using the default for this field, the target `src/charts/mychart:tgt_name` might have a final path like `src.charts.mychart/tgt_name/mychart-0.1.0.tgz`.\n\nWhen running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built directory tree should be located.\n\nIf undefined, this will use the path to the BUILD file, For example, `src/charts/mychart:tgt_name` would be `src.charts.mychart/tgt_name/`.\n\nRegardless of whether you use the default or set this field, the path will end with Helms's file format of `-.tgz`, where `chart_name` and `chart_version` are the values extracted from the Chart.yaml file. So, using the default for this field, the target `src/charts/mychart:tgt_name` might have a final path like `src.charts.mychart/tgt_name/mychart-0.1.0.tgz`.\n\nWhen running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -64940,7 +64940,7 @@ { "alias": "skip_push", "default": "False", - "description": "If set to true, do not push this Helm chart to registries when running `scie-pants-linux-x86_64 publish`.", + "description": "If set to true, do not push this Helm chart to registries when running `pants publish`.", "provider": "", "required": false, "type_hint": "bool" @@ -64948,7 +64948,7 @@ { "alias": "skip_lint", "default": "False", - "description": "If set to true, do not run any linting in this Helm chart when running `scie-pants-linux-x86_64 lint`.", + "description": "If set to true, do not run any linting in this Helm chart when running `pants lint`.", "provider": "", "required": false, "type_hint": "bool" @@ -64964,7 +64964,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -64972,7 +64972,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -64996,7 +64996,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -65076,7 +65076,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -65084,7 +65084,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -65100,7 +65100,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -65132,7 +65132,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -65140,7 +65140,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -65156,7 +65156,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -65196,7 +65196,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -65204,7 +65204,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -65212,7 +65212,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -65276,7 +65276,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -65284,7 +65284,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -65308,7 +65308,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -65356,7 +65356,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -65364,7 +65364,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -65396,7 +65396,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -65436,7 +65436,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -65444,7 +65444,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -65476,7 +65476,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -65516,7 +65516,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -65524,7 +65524,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -65620,7 +65620,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -65628,7 +65628,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -65652,7 +65652,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -65676,7 +65676,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -65692,7 +65692,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -65700,7 +65700,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -65708,7 +65708,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -65780,7 +65780,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -65788,7 +65788,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -65804,7 +65804,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -65868,7 +65868,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -65876,7 +65876,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -65884,7 +65884,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -65956,7 +65956,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -65964,7 +65964,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -65988,7 +65988,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66044,7 +66044,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66052,7 +66052,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -66092,7 +66092,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66100,7 +66100,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -66348,7 +66348,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66356,7 +66356,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -66364,7 +66364,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66396,7 +66396,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66404,7 +66404,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -66428,7 +66428,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66444,7 +66444,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66452,7 +66452,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -66460,7 +66460,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66484,7 +66484,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66492,7 +66492,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -66508,7 +66508,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66524,7 +66524,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66532,7 +66532,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -66572,7 +66572,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66580,7 +66580,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -66628,7 +66628,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66772,7 +66772,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66780,7 +66780,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -66812,7 +66812,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66980,7 +66980,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -66996,7 +66996,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -67004,7 +67004,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -67060,7 +67060,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -67068,7 +67068,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -67124,7 +67124,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -67132,7 +67132,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -67140,7 +67140,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -67236,7 +67236,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -67244,7 +67244,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -67340,7 +67340,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -67356,7 +67356,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -67364,7 +67364,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -67372,7 +67372,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built directory tree should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:bin` would be `src.python.project/bin/`.\n\nRegardless of whether you use the default or set this field, the path will end with PyOxidizer's file format of `/{debug,release}/install/`, where `platform` is a Rust platform triplet like `aarch-64-apple-darwin` and `binary_name` is the value of the `binary_name` field. So, using the default for this field, the target `src/python/project:bin` might have a final path like `src.python.project/bin/aarch-64-apple-darwin/release/bin`.\n\nWhen running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built directory tree should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:bin` would be `src.python.project/bin/`.\n\nRegardless of whether you use the default or set this field, the path will end with PyOxidizer's file format of `/{debug,release}/install/`, where `platform` is a Rust platform triplet like `aarch-64-apple-darwin` and `binary_name` is the value of the `binary_name` field. So, using the default for this field, the target `src/python/project:bin` might have a final path like `src.python.project/bin/aarch-64-apple-darwin/release/bin`.\n\nWhen running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -67436,7 +67436,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -67444,7 +67444,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -67452,7 +67452,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -67500,7 +67500,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -67524,7 +67524,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -67532,7 +67532,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -67540,7 +67540,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -67596,7 +67596,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": true, "type_hint": "Iterable[str]" @@ -67612,7 +67612,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -67620,7 +67620,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -67636,7 +67636,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -67644,7 +67644,7 @@ { "alias": "entry_points", "default": null, - "description": "Any entry points, such as `console_scripts` and `gui_scripts`.\n\nSpecify as a nested dictionary, with a dictionary for each type of entry point, e.g. `console_scripts` vs. `gui_scripts`. Each dictionary maps the entry point name to either a setuptools entry point (`\"path.to.module:func\"`) or a Pants target address to a `pex_binary` target.\n\nExample:\n\n entry_points={\n \"console_scripts\": {\n \"my-script\": \"project.app:main\",\n \"another-script\": \"project/subdir:pex_binary_tgt\"\n }\n }\n\nNote that Pants will assume that any value that either starts with `:` or has `/` in it, is a target address to a `pex_binary` target. Otherwise, it will assume it's a setuptools entry point as defined by https://packaging.python.org/specifications/entry-points/#entry-points-specification. Use `//` as a prefix for target addresses if you need to disambiguate.\n\nPants will attempt to infer dependencies, which you can confirm by running:\n\n scie-pants-linux-x86_64 dependencies ", + "description": "Any entry points, such as `console_scripts` and `gui_scripts`.\n\nSpecify as a nested dictionary, with a dictionary for each type of entry point, e.g. `console_scripts` vs. `gui_scripts`. Each dictionary maps the entry point name to either a setuptools entry point (`\"path.to.module:func\"`) or a Pants target address to a `pex_binary` target.\n\nExample:\n\n entry_points={\n \"console_scripts\": {\n \"my-script\": \"project.app:main\",\n \"another-script\": \"project/subdir:pex_binary_tgt\"\n }\n }\n\nNote that Pants will assume that any value that either starts with `:` or has `/` in it, is a target address to a `pex_binary` target. Otherwise, it will assume it's a setuptools entry point as defined by https://packaging.python.org/specifications/entry-points/#entry-points-specification. Use `//` as a prefix for target addresses if you need to disambiguate.\n\nPants will attempt to infer dependencies, which you can confirm by running:\n\n pants dependencies ", "provider": "", "required": false, "type_hint": "Dict[str, Dict[str, str]] | None" @@ -67756,7 +67756,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -67764,7 +67764,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -67772,7 +67772,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -67780,7 +67780,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -67844,7 +67844,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -67852,7 +67852,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -67868,7 +67868,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -67916,7 +67916,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -67924,7 +67924,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -67980,7 +67980,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -67988,7 +67988,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -68004,7 +68004,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -68164,7 +68164,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -68172,7 +68172,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -68324,7 +68324,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -68356,7 +68356,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -68364,7 +68364,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -68372,7 +68372,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -68420,7 +68420,7 @@ { "alias": "runtime_package_dependencies", "default": null, - "description": "Addresses to targets that can be built with the `scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_aws_lambda_function`, or an `archive`.", + "description": "Addresses to targets that can be built with the `pants package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `pants package`, e.g. a `pex_binary`, `python_aws_lambda_function`, or an `archive`.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -68596,7 +68596,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -68604,7 +68604,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -68756,7 +68756,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -68780,7 +68780,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -68788,7 +68788,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -68932,7 +68932,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -68980,7 +68980,7 @@ { "alias": "runtime_package_dependencies", "default": null, - "description": "Addresses to targets that can be built with the `scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_aws_lambda_function`, or an `archive`.", + "description": "Addresses to targets that can be built with the `pants package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `pants package`, e.g. a `pex_binary`, `python_aws_lambda_function`, or an `archive`.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -69028,7 +69028,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -69036,7 +69036,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -69076,7 +69076,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -69084,7 +69084,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -69348,7 +69348,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -69356,7 +69356,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -69364,7 +69364,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -69388,7 +69388,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -69396,7 +69396,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -69420,7 +69420,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -69436,7 +69436,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -69444,7 +69444,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -69492,7 +69492,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -69500,7 +69500,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -69604,7 +69604,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -69612,7 +69612,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -69620,7 +69620,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -69692,7 +69692,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -69700,7 +69700,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -69732,7 +69732,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -69796,7 +69796,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -69804,7 +69804,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -69812,7 +69812,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -69884,7 +69884,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -69892,7 +69892,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -69924,7 +69924,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -69980,7 +69980,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -69988,7 +69988,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -70020,7 +70020,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -70028,7 +70028,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -70036,7 +70036,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -70108,7 +70108,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -70116,7 +70116,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -70140,7 +70140,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -70204,7 +70204,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -70212,7 +70212,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -70332,7 +70332,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -70340,7 +70340,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -70348,7 +70348,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -70388,7 +70388,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -70396,7 +70396,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -70436,7 +70436,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -70452,7 +70452,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -70460,7 +70460,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -70476,7 +70476,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -70508,7 +70508,7 @@ { "alias": "runtime_package_dependencies", "default": null, - "description": "Addresses to targets that can be built with the `scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_aws_lambda_function`, or an `archive`.", + "description": "Addresses to targets that can be built with the `pants package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `pants package`, e.g. a `pex_binary`, `python_aws_lambda_function`, or an `archive`.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -70540,7 +70540,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -70548,7 +70548,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -70588,7 +70588,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -70620,7 +70620,7 @@ { "alias": "runtime_package_dependencies", "default": null, - "description": "Addresses to targets that can be built with the `scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_aws_lambda_function`, or an `archive`.", + "description": "Addresses to targets that can be built with the `pants package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `pants package`, e.g. a `pex_binary`, `python_aws_lambda_function`, or an `archive`.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -70636,7 +70636,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -70644,7 +70644,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -70700,7 +70700,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -70708,7 +70708,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -70716,7 +70716,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -70732,7 +70732,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -70740,7 +70740,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -70748,7 +70748,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -70788,7 +70788,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -70796,7 +70796,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -70804,7 +70804,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -70828,7 +70828,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -70836,7 +70836,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -70844,7 +70844,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -70876,7 +70876,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -70884,7 +70884,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -70916,7 +70916,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -70932,7 +70932,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -70940,7 +70940,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -71307,7 +71307,7 @@ "display_args": ["--pants-version="], "env_var": "PANTS_VERSION", "fromfile": false, - "help": "Use this Pants version. Note that Pants only uses this to verify that you are using the requested version, as Pants cannot dynamically change the version it is using once the program is already running.\n\nIf you use the `scie-pants-linux-x86_64` script from https://www.pantsbuild.org/v2.18/docs/installation, however, changing the value in your `pants.toml` will cause the new version to be installed and run automatically.\n\nRun `scie-pants-linux-x86_64 --version` to check what is being used.", + "help": "Use this Pants version. Note that Pants only uses this to verify that you are using the requested version, as Pants cannot dynamically change the version it is using once the program is already running.\n\nIf you use the `pants` script from https://www.pantsbuild.org/v2.18/docs/installation, however, changing the value in your `pants.toml` will cause the new version to be installed and run automatically.\n\nRun `pants --version` to check what is being used.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pants-version"], @@ -71367,7 +71367,7 @@ { "details": "from env var PANTS_BIN_NAME", "rank": "ENVIRONMENT", - "value": "/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64" + "value": "/home/josh/work/scie-pants/dist/pants" } ] } @@ -72568,7 +72568,7 @@ ], "env_var": "PANTS_PROCESS_EXECUTION_GRACEFUL_SHUTDOWN_TIMEOUT", "fromfile": false, - "help": "The time in seconds to wait when gracefully shutting down an interactive process (such as one opened using `scie-pants-linux-x86_64 run`) before killing it.", + "help": "The time in seconds to wait when gracefully shutting down an interactive process (such as one opened using `pants run`) before killing it.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -74497,7 +74497,7 @@ "display_args": ["--[no-]add-trailing-comma-skip"], "env_var": "PANTS_ADD_TRAILING_COMMA_SKIP", "fromfile": false, - "help": "If true, don't use add-trailing-comma when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use add-trailing-comma when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -74893,7 +74893,7 @@ "display_args": ["--[no-]autoflake-skip"], "env_var": "PANTS_AUTOFLAKE_SKIP", "fromfile": false, - "help": "If true, don't use Autoflake when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Autoflake when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--autoflake-skip", "--no-autoflake-skip"], @@ -75123,7 +75123,7 @@ "display_args": ["--[no-]bandit-skip"], "env_var": "PANTS_BANDIT_SKIP", "fromfile": false, - "help": "If true, don't use Bandit when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Bandit when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--bandit-skip", "--no-bandit-skip"], @@ -75425,7 +75425,7 @@ "display_args": ["--[no-]black-skip"], "env_var": "PANTS_BLACK_SKIP", "fromfile": false, - "help": "If true, don't use Black when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Black when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--black-skip", "--no-black-skip"], @@ -75759,7 +75759,7 @@ "display_args": ["--[no-]buf-format-skip"], "env_var": "PANTS_BUF_FORMAT_SKIP", "fromfile": false, - "help": "If true, don't use Buf when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Buf when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--buf-format-skip", "--no-buf-format-skip"], @@ -75792,7 +75792,7 @@ "display_args": ["--[no-]buf-lint-skip"], "env_var": "PANTS_BUF_LINT_SKIP", "fromfile": false, - "help": "If true, don't use Buf when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Buf when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--buf-lint-skip", "--no-buf-lint-skip"], @@ -75906,7 +75906,7 @@ "display_args": ["--[no-]build-deprecations-fixer-skip"], "env_var": "PANTS_BUILD_DEPRECATIONS_FIXER_SKIP", "fromfile": false, - "help": "If true, don't use BUILD Deprecations Fixer when running `scie-pants-linux-x86_64 fix`.", + "help": "If true, don't use BUILD Deprecations Fixer when running `pants fix`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -76145,7 +76145,7 @@ "display_args": ["--[no-]buildifier-skip"], "env_var": "PANTS_BUILDIFIER_SKIP", "fromfile": false, - "help": "If true, don't use Buildifier when running `scie-pants-linux-x86_64 fmt`.", + "help": "If true, don't use Buildifier when running `pants fmt`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--buildifier-skip", "--no-buildifier-skip"], @@ -76402,7 +76402,7 @@ "display_args": ["--cli-alias=\"{'key1': val1, 'key2': val2, ...}\""], "env_var": "PANTS_CLI_ALIAS", "fromfile": false, - "help": "Register command line aliases.\n\nExample:\n\n [cli.alias]\n green = \"fmt lint check\"\n all-changed = \"--changed-since=HEAD --changed-dependents=transitive\"\n\nThis would allow you to run `scie-pants-linux-x86_64 green all-changed`, which is shorthand for `scie-pants-linux-x86_64 fmt lint check --changed-since=HEAD --changed-dependents=transitive`.\n\nNotice: this option must be placed in a config file (e.g. `pants.toml` or `pantsrc`) to have any effect.", + "help": "Register command line aliases.\n\nExample:\n\n [cli.alias]\n green = \"fmt lint check\"\n all-changed = \"--changed-since=HEAD --changed-dependents=transitive\"\n\nThis would allow you to run `pants green all-changed`, which is shorthand for `pants fmt lint check --changed-since=HEAD --changed-dependents=transitive`.\n\nNotice: this option must be placed in a config file (e.g. `pants.toml` or `pantsrc`) to have any effect.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--cli-alias"], @@ -77992,7 +77992,7 @@ "display_args": ["--[no-]docformatter-skip"], "env_var": "PANTS_DOCFORMATTER_SKIP", "fromfile": false, - "help": "If true, don't use docformatter when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use docformatter when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -78484,7 +78484,7 @@ ], "env_var": "PANTS_DOCKER_RUN_ARGS", "fromfile": false, - "help": "Additional arguments to use for `docker run` invocations.\n\nExample:\n\n $ scie-pants-linux-x86_64 run --docker-run-args=\"-p 127.0.0.1:80:8080/tcp --name demo\" src/example:image -- [image entrypoint args]\n\nTo provide the top-level options to the `docker` client, use `[docker].env_vars` to configure the [Environment variables](https://docs.docker.com/engine/reference/commandline/cli/#environment-variables) as appropriate.\n\nThe arguments for the image entrypoint may be passed on the command line after a double dash (`--`), or using the `--run-args` option.\n\nDefaults to `--interactive --tty` when stdout is connected to a terminal.", + "help": "Additional arguments to use for `docker run` invocations.\n\nExample:\n\n $ pants run --docker-run-args=\"-p 127.0.0.1:80:8080/tcp --name demo\" src/example:image -- [image entrypoint args]\n\nTo provide the top-level options to the `docker` client, use `[docker].env_vars` to configure the [Environment variables](https://docs.docker.com/engine/reference/commandline/cli/#environment-variables) as appropriate.\n\nThe arguments for the image entrypoint may be passed on the command line after a double dash (`--`), or using the `--run-args` option.\n\nDefaults to `--interactive --tty` when stdout is connected to a terminal.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--docker-run-args"], @@ -79370,7 +79370,7 @@ ], "env_var": "PANTS_EXPERIMENTAL_BSP_RUNNER_ENV_VARS", "fromfile": false, - "help": "Environment variables to set in the BSP runner script when setting up BSP in a repository. Entries are either strings in the form `ENV_VAR=value` to set an explicit value; or just `ENV_VAR` to copy the value from Pants' own environment when the experimental-bsp goal was run.\n\nThis option only takes effect when the BSP runner script is written. If the option changes, you must run `scie-pants-linux-x86_64 experimental-bsp` again to write a new copy of the BSP runner script.\n\nNote: The environment variables passed to the Pants BSP server will be those set for your IDE and not your shell. For example, on macOS, the IDE is generally launched by `launchd` after clicking on a Dock icon, and not from the shell. Thus, any environment variables set for your shell will likely not be seen by the Pants BSP server. At the very least, on macOS consider writing an explicit PATH into the BSP runner script via this option.", + "help": "Environment variables to set in the BSP runner script when setting up BSP in a repository. Entries are either strings in the form `ENV_VAR=value` to set an explicit value; or just `ENV_VAR` to copy the value from Pants' own environment when the experimental-bsp goal was run.\n\nThis option only takes effect when the BSP runner script is written. If the option changes, you must run `pants experimental-bsp` again to write a new copy of the BSP runner script.\n\nNote: The environment variables passed to the Pants BSP server will be those set for your IDE and not your shell. For example, on macOS, the IDE is generally launched by `launchd` after clicking on a Dock icon, and not from the shell. Thus, any environment variables set for your shell will likely not be seen by the Pants BSP server. At the very least, on macOS consider writing an explicit PATH into the BSP runner script via this option.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--experimental-bsp-runner-env-vars"], @@ -80157,7 +80157,7 @@ "display_args": ["--[no-]fix-skip-formatters"], "env_var": "PANTS_FIX_SKIP_FORMATTERS", "fromfile": false, - "help": "If true, skip running all formatters.\n\nFYI: when running `scie-pants-linux-x86_64 fix fmt ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `fix` where possible.", + "help": "If true, skip running all formatters.\n\nFYI: when running `pants fix fmt ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `fix` where possible.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -80467,7 +80467,7 @@ "display_args": ["--[no-]flake8-skip"], "env_var": "PANTS_FLAKE8_SKIP", "fromfile": false, - "help": "If true, don't use Flake8 when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Flake8 when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--flake8-skip", "--no-flake8-skip"], @@ -80621,7 +80621,7 @@ "display_args": ["--generate-lockfiles-custom-command="], "env_var": "PANTS_GENERATE_LOCKFILES_CUSTOM_COMMAND", "fromfile": false, - "help": "If set, lockfile headers will say to run this command to regenerate the lockfile, rather than running `scie-pants-linux-x86_64 generate-lockfiles --resolve=` like normal.", + "help": "If set, lockfile headers will say to run this command to regenerate the lockfile, rather than running `pants generate-lockfiles --resolve=` like normal.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--generate-lockfiles-custom-command"], @@ -80653,7 +80653,7 @@ ], "env_var": "PANTS_GENERATE_LOCKFILES_RESOLVE", "fromfile": false, - "help": "Only generate lockfiles for the specified resolve(s).\n\nResolves are the logical names for the different lockfiles used in your project. For your own code's dependencies, these come from backend-specific configuration such as `[python].resolves`. For tool lockfiles, resolve names are the options scope for that tool such as `black`, `pytest`, and `mypy-protobuf`.\n\nFor example, you can run `scie-pants-linux-x86_64 generate-lockfiles --resolve=black --resolve=pytest --resolve=data-science` to only generate lockfiles for those two tools and your resolve named `data-science`.\n\nIf you specify an invalid resolve name, like 'fake', Pants will output all possible values.\n\nIf not specified, Pants will generate lockfiles for all resolves.", + "help": "Only generate lockfiles for the specified resolve(s).\n\nResolves are the logical names for the different lockfiles used in your project. For your own code's dependencies, these come from backend-specific configuration such as `[python].resolves`. For tool lockfiles, resolve names are the options scope for that tool such as `black`, `pytest`, and `mypy-protobuf`.\n\nFor example, you can run `pants generate-lockfiles --resolve=black --resolve=pytest --resolve=data-science` to only generate lockfiles for those two tools and your resolve named `data-science`.\n\nIf you specify an invalid resolve name, like 'fake', Pants will output all possible values.\n\nIf not specified, Pants will generate lockfiles for all resolves.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--generate-lockfiles-resolve"], @@ -81041,7 +81041,7 @@ "display_args": ["--[no-]go-test-skip"], "env_var": "PANTS_GO_TEST_SKIP", "fromfile": false, - "help": "If true, don't use Go test binary when running `scie-pants-linux-x86_64 test`.", + "help": "If true, don't use Go test binary when running `pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--go-test-skip", "--no-go-test-skip"], @@ -81370,7 +81370,7 @@ "display_args": ["--[no-]gofmt-skip"], "env_var": "PANTS_GOFMT_SKIP", "fromfile": false, - "help": "If true, don't use gofmt when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use gofmt when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--gofmt-skip", "--no-gofmt-skip"], @@ -82157,7 +82157,7 @@ "display_args": ["--google-java-format-lockfile="], "env_var": "PANTS_GOOGLE_JAVA_FORMAT_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.18.0rc5/src/python/pants/backend/java/lint/google_java_format/google_java_format.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=google-java-format`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.18.0rc5/src/python/pants/backend/java/lint/google_java_format/google_java_format.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=google-java-format`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--google-java-format-lockfile"], @@ -82227,7 +82227,7 @@ "display_args": ["--[no-]google-java-format-skip"], "env_var": "PANTS_GOOGLE_JAVA_FORMAT_SKIP", "fromfile": false, - "help": "If true, don't use Google Java Format when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Google Java Format when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -82773,7 +82773,7 @@ "display_args": ["--[no-]hadolint-skip"], "env_var": "PANTS_HADOLINT_SKIP", "fromfile": false, - "help": "If true, don't use Hadolint when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Hadolint when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--hadolint-skip", "--no-hadolint-skip"], @@ -83869,7 +83869,7 @@ "display_args": ["--[no-]helm-unittest-skip"], "env_var": "PANTS_HELM_UNITTEST_SKIP", "fromfile": false, - "help": "If true, don't use helmunittestsubsystem when running `scie-pants-linux-x86_64 test`.", + "help": "If true, don't use helmunittestsubsystem when running `pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -84349,7 +84349,7 @@ "display_args": ["--[no-]isort-skip"], "env_var": "PANTS_ISORT_SKIP", "fromfile": false, - "help": "If true, don't use isort when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use isort when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--isort-skip", "--no-isort-skip"], @@ -84491,7 +84491,7 @@ "display_args": ["--jarjar-lockfile="], "env_var": "PANTS_JARJAR_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.18.0rc5/src/python/pants/jvm/shading/jarjar.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=jarjar`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.18.0rc5/src/python/pants/jvm/shading/jarjar.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=jarjar`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--jarjar-lockfile"], @@ -84911,7 +84911,7 @@ "display_args": ["--junit-lockfile="], "env_var": "PANTS_JUNIT_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.18.0rc5/src/python/pants/jvm/test/junit.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=junit`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.18.0rc5/src/python/pants/jvm/test/junit.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=junit`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--junit-lockfile"], @@ -85015,7 +85015,7 @@ "display_args": ["--[no-]junit-skip"], "env_var": "PANTS_JUNIT_SKIP", "fromfile": false, - "help": "If true, don't use JUnit when running `scie-pants-linux-x86_64 test`.", + "help": "If true, don't use JUnit when running `pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--junit-skip", "--no-junit-skip"], @@ -85668,7 +85668,7 @@ "display_args": ["--ktlint-lockfile="], "env_var": "PANTS_KTLINT_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.18.0rc5/src/python/pants/backend/kotlin/lint/ktlint/ktlint.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=ktlint`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.18.0rc5/src/python/pants/backend/kotlin/lint/ktlint/ktlint.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=ktlint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--ktlint-lockfile"], @@ -85736,7 +85736,7 @@ "display_args": ["--[no-]ktlint-skip"], "env_var": "PANTS_KTLINT_SKIP", "fromfile": false, - "help": "If true, don't use Ktlint when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Ktlint when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--ktlint-skip", "--no-ktlint-skip"], @@ -86051,7 +86051,7 @@ "display_args": ["--[no-]lint-skip-formatters"], "env_var": "PANTS_LINT_SKIP_FORMATTERS", "fromfile": false, - "help": "If true, skip running all formatters in check-only mode.\n\nFYI: when running `scie-pants-linux-x86_64 fmt lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `lint` where possible.", + "help": "If true, skip running all formatters in check-only mode.\n\nFYI: when running `pants fmt lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `lint` where possible.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -86090,7 +86090,7 @@ "display_args": ["--[no-]lint-skip-fixers"], "env_var": "PANTS_LINT_SKIP_FIXERS", "fromfile": false, - "help": "If true, skip running all fixers in check-only mode.\n\nFYI: when running `scie-pants-linux-x86_64 fix lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fix` when running `lint` where possible.", + "help": "If true, skip running all fixers in check-only mode.\n\nFYI: when running `pants fix lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fix` when running `lint` where possible.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -86502,7 +86502,7 @@ "display_args": ["--[no-]mypy-skip"], "env_var": "PANTS_MYPY_SKIP", "fromfile": false, - "help": "If true, don't use MyPy when running `scie-pants-linux-x86_64 check`.", + "help": "If true, don't use MyPy when running `pants check`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--mypy-skip", "--no-mypy-skip"], @@ -86845,7 +86845,7 @@ ], "env_var": "PANTS_NODEJS_RESOLVES", "fromfile": false, - "help": "A mapping of names to lockfile paths used in your project.\n\nSpecifying a resolve name is optional. If unspecified, the default resolve name is calculated by taking the path from the source root to the directory containing the lockfile and replacing '/' with '.' in that path.\n\nExample: An npm lockfile located at `src/js/package/package-lock.json' will result in a resolve named `js.package`, assuming src/ is a source root.\n\nRun `scie-pants-linux-x86_64 generate-lockfiles` to generate the lockfile(s).", + "help": "A mapping of names to lockfile paths used in your project.\n\nSpecifying a resolve name is optional. If unspecified, the default resolve name is calculated by taking the path from the source root to the directory containing the lockfile and replacing '/' with '.' in that path.\n\nExample: An npm lockfile located at `src/js/package/package-lock.json' will result in a resolve named `js.package`, assuming src/ is a source root.\n\nRun `pants generate-lockfiles` to generate the lockfile(s).", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--nodejs-resolves"], @@ -87816,7 +87816,7 @@ "display_args": ["--[no-]preamble-skip"], "env_var": "PANTS_PREAMBLE_SKIP", "fromfile": false, - "help": "If true, don't use preamble when running `scie-pants-linux-x86_64 fmt`.", + "help": "If true, don't use preamble when running `pants fmt`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--preamble-skip", "--no-preamble-skip"], @@ -87972,7 +87972,7 @@ "display_args": ["--protobuf-java-grpc-lockfile="], "env_var": "PANTS_PROTOBUF_JAVA_GRPC_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.18.0rc5/src/python/pants/backend/codegen/protobuf/java/grpc-java.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=protobuf-java-grpc`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.18.0rc5/src/python/pants/backend/codegen/protobuf/java/grpc-java.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=protobuf-java-grpc`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--protobuf-java-grpc-lockfile"], @@ -88668,7 +88668,7 @@ "display_args": ["--[no-]pydocstyle-skip"], "env_var": "PANTS_PYDOCSTYLE_SKIP", "fromfile": false, - "help": "If true, don't use Pydocstyle when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Pydocstyle when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pydocstyle-skip", "--no-pydocstyle-skip"], @@ -88972,7 +88972,7 @@ "display_args": ["--[no-]pylint-skip"], "env_var": "PANTS_PYLINT_SKIP", "fromfile": false, - "help": "If true, don't use Pylint when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Pylint when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pylint-skip", "--no-pylint-skip"], @@ -89578,7 +89578,7 @@ "display_args": ["--[no-]pytest-skip"], "env_var": "PANTS_PYTEST_SKIP", "fromfile": false, - "help": "If true, don't use Pytest when running `scie-pants-linux-x86_64 test`.", + "help": "If true, don't use Pytest when running `pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pytest-skip", "--no-pytest-skip"], @@ -89754,7 +89754,7 @@ ], "env_var": "PANTS_PYTHON_RESOLVES", "fromfile": false, - "help": "A mapping of logical names to lockfile paths used in your project.\n\nMany organizations only need a single resolve for their whole project, which is a good default and often the simplest thing to do. However, you may need multiple resolves, such as if you use two conflicting versions of a requirement in your repository.\n\nIf you only need a single resolve, run `scie-pants-linux-x86_64 generate-lockfiles` to generate the lockfile.\n\nIf you need multiple resolves:\n\n 1. Via this option, define multiple resolve names and their lockfile paths. The names should be meaningful to your repository, such as `data-science` or `pants-plugins`.\n 2. Set the default with `[python].default_resolve`.\n 3. Update your `python_requirement` targets with the `resolve` field to declare which resolve they should be available in. They default to `[python].default_resolve`, so you only need to update targets that you want in non-default resolves. (Often you'll set this via the `python_requirements` or `poetry_requirements` target generators)\n 4. Run `scie-pants-linux-x86_64 generate-lockfiles` to generate the lockfiles. If the results aren't what you'd expect, adjust the prior step.\n 5. Update any targets like `python_source` / `python_sources`, `python_test` / `python_tests`, and `pex_binary` which need to set a non-default resolve with the `resolve` field.\n\nIf a target can work with multiple resolves, you can either use the `parametrize` mechanism or manually create a distinct target per resolve. See https://www.pantsbuild.org/v2.18/docs/targets for information about `parametrize`.\n\nFor example:\n\n python_sources(\n resolve=parametrize(\"data-science\", \"web-app\"),\n )\n\nYou can name the lockfile paths what you would like; Pants does not expect a certain file extension or location.\n\nOnly applies if `[python].enable_resolves` is true.", + "help": "A mapping of logical names to lockfile paths used in your project.\n\nMany organizations only need a single resolve for their whole project, which is a good default and often the simplest thing to do. However, you may need multiple resolves, such as if you use two conflicting versions of a requirement in your repository.\n\nIf you only need a single resolve, run `pants generate-lockfiles` to generate the lockfile.\n\nIf you need multiple resolves:\n\n 1. Via this option, define multiple resolve names and their lockfile paths. The names should be meaningful to your repository, such as `data-science` or `pants-plugins`.\n 2. Set the default with `[python].default_resolve`.\n 3. Update your `python_requirement` targets with the `resolve` field to declare which resolve they should be available in. They default to `[python].default_resolve`, so you only need to update targets that you want in non-default resolves. (Often you'll set this via the `python_requirements` or `poetry_requirements` target generators)\n 4. Run `pants generate-lockfiles` to generate the lockfiles. If the results aren't what you'd expect, adjust the prior step.\n 5. Update any targets like `python_source` / `python_sources`, `python_test` / `python_tests`, and `pex_binary` which need to set a non-default resolve with the `resolve` field.\n\nIf a target can work with multiple resolves, you can either use the `parametrize` mechanism or manually create a distinct target per resolve. See https://www.pantsbuild.org/v2.18/docs/targets for information about `parametrize`.\n\nFor example:\n\n python_sources(\n resolve=parametrize(\"data-science\", \"web-app\"),\n )\n\nYou can name the lockfile paths what you would like; Pants does not expect a certain file extension or location.\n\nOnly applies if `[python].enable_resolves` is true.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--python-resolves"], @@ -90507,7 +90507,7 @@ "env_var": "PANTS_PYTHON_REQUIREMENT_CONSTRAINTS", "fromfile": false, "help": "When resolving third-party requirements for your own code (vs. tools you run), use this constraints file to determine which versions to use.\n\nMutually exclusive with `[python].enable_resolves`, which we generally recommend as an improvement over constraints file.\n\nSee https://pip.pypa.io/en/stable/user_guide/#constraints-files for more information on the format of constraint files and how constraints are applied in Pex and pip.\n\nThis only applies when resolving user requirements, rather than tools you run like Black and Pytest. To constrain tools, set `[tool].lockfile`, e.g. `[black].lockfile`.", - "removal_hint": "We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.\n\nTo migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `scie-pants-linux-x86_64 generate-lockfiles`.", + "removal_hint": "We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.\n\nTo migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `pants generate-lockfiles`.", "removal_version": "3.0.0.dev0", "scoped_cmd_line_args": ["--python-requirement-constraints"], "target_field_name": null, @@ -90535,7 +90535,7 @@ "env_var": "PANTS_PYTHON_RESOLVE_ALL_CONSTRAINTS", "fromfile": false, "help": "(Only relevant when using `[python].requirement_constraints.`) If enabled, when resolving requirements, Pants will first resolve your entire constraints file as a single global resolve. Then, if the code uses a subset of your constraints file, Pants will extract the relevant requirements from that global resolve so that only what's actually needed gets used. If disabled, Pants will not use a global resolve and will resolve each subset of your requirements independently.\n\nUsually this option should be enabled because it can result in far fewer resolves.", - "removal_hint": "We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.\n\nTo migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `scie-pants-linux-x86_64 generate-lockfiles`.", + "removal_hint": "We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.\n\nTo migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `pants generate-lockfiles`.", "removal_version": "3.0.0.dev0", "scoped_cmd_line_args": [ "--python-resolve-all-constraints", @@ -90965,7 +90965,7 @@ "display_args": ["--python-infer-init-files="], "env_var": "PANTS_PYTHON_INFER_INIT_FILES", "fromfile": false, - "help": "Infer a target's dependencies on any `__init__.py` files in the packages it is located in (recursively upward in the directory structure).\n\nEven if this is set to `never` or `content_only`, Pants will still always include any ancestor `__init__.py` files in the sandbox. Only, they will not be \"proper\" dependencies, e.g. they will not show up in `scie-pants-linux-x86_64 dependencies` and their own dependencies will not be used.\n\nBy default, Pants only adds a \"proper\" dependency if there is content in the `__init__.py` file. This makes sure that dependencies are added when likely necessary to build, while also avoiding adding unnecessary dependencies. While accurate, those unnecessary dependencies can complicate setting metadata like the `interpreter_constraints` and `resolve` fields.", + "help": "Infer a target's dependencies on any `__init__.py` files in the packages it is located in (recursively upward in the directory structure).\n\nEven if this is set to `never` or `content_only`, Pants will still always include any ancestor `__init__.py` files in the sandbox. Only, they will not be \"proper\" dependencies, e.g. they will not show up in `pants dependencies` and their own dependencies will not be used.\n\nBy default, Pants only adds a \"proper\" dependency if there is content in the `__init__.py` file. This makes sure that dependencies are added when likely necessary to build, while also avoiding adding unnecessary dependencies. While accurate, those unnecessary dependencies can complicate setting metadata like the `interpreter_constraints` and `resolve` fields.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--python-infer-init-files"], @@ -91177,7 +91177,7 @@ "display_args": ["--[no-]python-infer-use-rust-parser"], "env_var": "PANTS_PYTHON_INFER_USE_RUST_PARSER", "fromfile": false, - "help": "Use the new Rust-based, multithreaded, in-process dependency parser.\n\nPants 2.17 introduced a new paradigm to dependency parsing for Python by leveraging a Rust-based parser that's called in the same process as Pants itself, instead of farming out to one-python-process-per-file.\n\nAs a result of the switch, cold-cache performance improved by a factor of about 12x, while hot-cache had no difference. Additionally, Pants can now infer dependencies from Python scripts with syntax errors.\n\nAfter leaving this defaulted to disabled for a release cycle, Pants 2.18 started defaulting to enabling this.\n\nIf you think the new behaviour is causing problems, it is recommended that you run `scie-pants-linux-x86_64 peek :: > before.json` and then `scie-pants-linux-x86_64 --python-infer-use-rust-parser=False peek :: > after.json` and compare the two results.\n\nIf you think there is a bug and need to disable it, please file an issue: https://github.com/pantsbuild/pants/issues/new/choose.", + "help": "Use the new Rust-based, multithreaded, in-process dependency parser.\n\nPants 2.17 introduced a new paradigm to dependency parsing for Python by leveraging a Rust-based parser that's called in the same process as Pants itself, instead of farming out to one-python-process-per-file.\n\nAs a result of the switch, cold-cache performance improved by a factor of about 12x, while hot-cache had no difference. Additionally, Pants can now infer dependencies from Python scripts with syntax errors.\n\nAfter leaving this defaulted to disabled for a release cycle, Pants 2.18 started defaulting to enabling this.\n\nIf you think the new behaviour is causing problems, it is recommended that you run `pants peek :: > before.json` and then `pants --python-infer-use-rust-parser=False peek :: > after.json` and compare the two results.\n\nIf you think there is a bug and need to disable it, please file an issue: https://github.com/pantsbuild/pants/issues/new/choose.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -91790,7 +91790,7 @@ "display_args": ["--[no-]pytype-skip"], "env_var": "PANTS_PYTYPE_SKIP", "fromfile": false, - "help": "If true, don't use Pytype when running `scie-pants-linux-x86_64 check`.", + "help": "If true, don't use Pytype when running `pants check`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pytype-skip", "--no-pytype-skip"], @@ -92055,7 +92055,7 @@ "display_args": ["--[no-]pyupgrade-skip"], "env_var": "PANTS_PYUPGRADE_SKIP", "fromfile": false, - "help": "If true, don't use pyupgrade when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use pyupgrade when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pyupgrade-skip", "--no-pyupgrade-skip"], @@ -92134,7 +92134,7 @@ "display_args": ["--[no-]regex-lint-skip"], "env_var": "PANTS_REGEX_LINT_SKIP", "fromfile": false, - "help": "If true, don't use regex-lint when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use regex-lint when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--regex-lint-skip", "--no-regex-lint-skip"], @@ -92618,7 +92618,7 @@ "display_args": ["--[no-]ruff-skip"], "env_var": "PANTS_RUFF_SKIP", "fromfile": false, - "help": "If true, don't use Ruff when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Ruff when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--ruff-skip", "--no-ruff-skip"], @@ -93171,7 +93171,7 @@ "display_args": ["--scalafmt-lockfile="], "env_var": "PANTS_SCALAFMT_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.18.0rc5/src/python/pants/backend/scala/lint/scalafmt/scalafmt.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalafmt`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.18.0rc5/src/python/pants/backend/scala/lint/scalafmt/scalafmt.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=scalafmt`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalafmt-lockfile"], @@ -93241,7 +93241,7 @@ "display_args": ["--[no-]scalafmt-skip"], "env_var": "PANTS_SCALAFMT_SKIP", "fromfile": false, - "help": "If true, don't use scalafmt when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use scalafmt when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalafmt-skip", "--no-scalafmt-skip"], @@ -93350,7 +93350,7 @@ "display_args": ["--scalapb-lockfile="], "env_var": "PANTS_SCALAPB_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.18.0rc5/src/python/pants/backend/codegen/protobuf/scala/scalapbc.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalapb`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.18.0rc5/src/python/pants/backend/codegen/protobuf/scala/scalapbc.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=scalapb`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalapb-lockfile"], @@ -93527,7 +93527,7 @@ "display_args": ["--scalatest-lockfile="], "env_var": "PANTS_SCALATEST_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.18.0rc5/src/python/pants/backend/scala/subsystems/scalatest.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalatest`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.18.0rc5/src/python/pants/backend/scala/subsystems/scalatest.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=scalatest`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalatest-lockfile"], @@ -93633,7 +93633,7 @@ "display_args": ["--[no-]scalatest-skip"], "env_var": "PANTS_SCALATEST_SKIP", "fromfile": false, - "help": "If true, don't use Scalatest when running `scie-pants-linux-x86_64 test`.", + "help": "If true, don't use Scalatest when running `pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalatest-skip", "--no-scalatest-skip"], @@ -94366,7 +94366,7 @@ "display_args": ["--[no-]shell-test-skip"], "env_var": "PANTS_SHELL_TEST_SKIP", "fromfile": false, - "help": "If true, don't use Test with shell scripts when running `scie-pants-linux-x86_64 test`.", + "help": "If true, don't use Test with shell scripts when running `pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--shell-test-skip", "--no-shell-test-skip"], @@ -94641,7 +94641,7 @@ "display_args": ["--[no-]shellcheck-skip"], "env_var": "PANTS_SHELLCHECK_SKIP", "fromfile": false, - "help": "If true, don't use Shellcheck when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Shellcheck when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--shellcheck-skip", "--no-shellcheck-skip"], @@ -94959,7 +94959,7 @@ "display_args": ["--[no-]shfmt-skip"], "env_var": "PANTS_SHFMT_SKIP", "fromfile": false, - "help": "If true, don't use shfmt when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use shfmt when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--shfmt-skip", "--no-shfmt-skip"], @@ -95213,7 +95213,7 @@ "display_args": ["--[no-]shunit2-skip"], "env_var": "PANTS_SHUNIT2_SKIP", "fromfile": false, - "help": "If true, don't use shunit2 when running `scie-pants-linux-x86_64 test`.", + "help": "If true, don't use shunit2 when running `pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--shunit2-skip", "--no-shunit2-skip"], @@ -95420,7 +95420,7 @@ "display_args": ["--[no-]spectral-skip"], "env_var": "PANTS_SPECTRAL_SKIP", "fromfile": false, - "help": "If true, don't use Spectral when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Spectral when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--spectral-skip", "--no-spectral-skip"], @@ -95879,7 +95879,7 @@ "display_args": ["--[no-]terraform-fmt-skip"], "env_var": "PANTS_TERRAFORM_FMT_SKIP", "fromfile": false, - "help": "If true, don't use `terraform fmt` when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use `terraform fmt` when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -96041,7 +96041,7 @@ "display_args": ["--[no-]terraform-validate-skip"], "env_var": "PANTS_TERRAFORM_VALIDATE_SKIP", "fromfile": false, - "help": "If true, don't use `terraform validate` when running `scie-pants-linux-x86_64 check`.", + "help": "If true, don't use `terraform validate` when running `pants check`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -96903,7 +96903,7 @@ "display_args": ["--[no-]twine-skip"], "env_var": "PANTS_TWINE_SKIP", "fromfile": false, - "help": "If true, don't use Twine when running `scie-pants-linux-x86_64 publish`.", + "help": "If true, don't use Twine when running `pants publish`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--twine-skip", "--no-twine-skip"], @@ -97519,7 +97519,7 @@ "display_args": ["--[no-]yamllint-skip"], "env_var": "PANTS_YAMLLINT_SKIP", "fromfile": false, - "help": "If true, don't use Yamllint when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Yamllint when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--yamllint-skip", "--no-yamllint-skip"], @@ -97788,7 +97788,7 @@ "display_args": ["--[no-]yapf-skip"], "env_var": "PANTS_YAPF_SKIP", "fromfile": false, - "help": "If true, don't use yapf when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use yapf when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--yapf-skip", "--no-yapf-skip"], diff --git a/versioned_docs/version-2.18/reference/subsystems/add-trailing-comma.mdx b/versioned_docs/version-2.18/reference/subsystems/add-trailing-comma.mdx index a22ca149f..ba816f8e1 100644 --- a/versioned_docs/version-2.18/reference/subsystems/add-trailing-comma.mdx +++ b/versioned_docs/version-2.18/reference/subsystems/add-trailing-comma.mdx @@ -25,7 +25,7 @@ Config section: `[add-trailing-comma]` default_repr={`False`} > -If true, don't use add-trailing-comma when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use add-trailing-comma when running `pants fmt` and `pants lint`. diff --git a/versioned_docs/version-2.18/reference/subsystems/autoflake.mdx b/versioned_docs/version-2.18/reference/subsystems/autoflake.mdx index 1c9d22656..eb7c84e6a 100644 --- a/versioned_docs/version-2.18/reference/subsystems/autoflake.mdx +++ b/versioned_docs/version-2.18/reference/subsystems/autoflake.mdx @@ -25,7 +25,7 @@ Config section: `[autoflake]` default_repr={`False`} > -If true, don't use Autoflake when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use Autoflake when running `pants fmt` and `pants lint`. diff --git a/versioned_docs/version-2.18/reference/subsystems/bandit.mdx b/versioned_docs/version-2.18/reference/subsystems/bandit.mdx index a8d5dffe0..77f52d8b3 100644 --- a/versioned_docs/version-2.18/reference/subsystems/bandit.mdx +++ b/versioned_docs/version-2.18/reference/subsystems/bandit.mdx @@ -25,7 +25,7 @@ Config section: `[bandit]` default_repr={`False`} > -If true, don't use Bandit when running `scie-pants-linux-x86_64 lint`. +If true, don't use Bandit when running `pants lint`. diff --git a/versioned_docs/version-2.18/reference/subsystems/black.mdx b/versioned_docs/version-2.18/reference/subsystems/black.mdx index 944c31d44..0ce457141 100644 --- a/versioned_docs/version-2.18/reference/subsystems/black.mdx +++ b/versioned_docs/version-2.18/reference/subsystems/black.mdx @@ -25,7 +25,7 @@ Config section: `[black]` default_repr={`False`} > -If true, don't use Black when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use Black when running `pants fmt` and `pants lint`. diff --git a/versioned_docs/version-2.18/reference/subsystems/buf.mdx b/versioned_docs/version-2.18/reference/subsystems/buf.mdx index ee41083d5..3c2d6e7f5 100644 --- a/versioned_docs/version-2.18/reference/subsystems/buf.mdx +++ b/versioned_docs/version-2.18/reference/subsystems/buf.mdx @@ -25,7 +25,7 @@ Config section: `[buf]` default_repr={`False`} > -If true, don't use Buf when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use Buf when running `pants fmt` and `pants lint`. @@ -37,7 +37,7 @@ If true, don't use Buf when running `scie-pants-linux-x86_64 fmt` and `scie default_repr={`False`} > -If true, don't use Buf when running `scie-pants-linux-x86_64 lint`. +If true, don't use Buf when running `pants lint`. diff --git a/versioned_docs/version-2.18/reference/subsystems/build-deprecations-fixer.mdx b/versioned_docs/version-2.18/reference/subsystems/build-deprecations-fixer.mdx index 7f54c6e7f..663dbb00f 100644 --- a/versioned_docs/version-2.18/reference/subsystems/build-deprecations-fixer.mdx +++ b/versioned_docs/version-2.18/reference/subsystems/build-deprecations-fixer.mdx @@ -30,7 +30,7 @@ Config section: `[build-deprecations-fixer]` -If true, don't use BUILD Deprecations Fixer when running `scie-pants-linux-x86_64 fix`. +If true, don't use BUILD Deprecations Fixer when running `pants fix`. diff --git a/versioned_docs/version-2.18/reference/subsystems/buildifier.mdx b/versioned_docs/version-2.18/reference/subsystems/buildifier.mdx index 08ced40f3..fde15877b 100644 --- a/versioned_docs/version-2.18/reference/subsystems/buildifier.mdx +++ b/versioned_docs/version-2.18/reference/subsystems/buildifier.mdx @@ -32,7 +32,7 @@ Config section: `[buildifier]` default_repr={`False`} > -If true, don't use Buildifier when running `scie-pants-linux-x86_64 fmt`. +If true, don't use Buildifier when running `pants fmt`. diff --git a/versioned_docs/version-2.18/reference/subsystems/cli.mdx b/versioned_docs/version-2.18/reference/subsystems/cli.mdx index c73472624..e471cf70f 100644 --- a/versioned_docs/version-2.18/reference/subsystems/cli.mdx +++ b/versioned_docs/version-2.18/reference/subsystems/cli.mdx @@ -35,7 +35,7 @@ green = "fmt lint check" all-changed = "--changed-since=HEAD --changed-dependents=transitive" ``` -This would allow you to run `scie-pants-linux-x86_64 green all-changed`, which is shorthand for `scie-pants-linux-x86_64 fmt lint check --changed-since=HEAD --changed-dependents=transitive`. +This would allow you to run `pants green all-changed`, which is shorthand for `pants fmt lint check --changed-since=HEAD --changed-dependents=transitive`. Notice: this option must be placed in a config file (e.g. `pants.toml` or `pantsrc`) to have any effect. diff --git a/versioned_docs/version-2.18/reference/subsystems/docformatter.mdx b/versioned_docs/version-2.18/reference/subsystems/docformatter.mdx index 67f8a4ebe..13d82114f 100644 --- a/versioned_docs/version-2.18/reference/subsystems/docformatter.mdx +++ b/versioned_docs/version-2.18/reference/subsystems/docformatter.mdx @@ -25,7 +25,7 @@ Config section: `[docformatter]` default_repr={`False`} > -If true, don't use docformatter when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use docformatter when running `pants fmt` and `pants lint`. diff --git a/versioned_docs/version-2.18/reference/subsystems/docker.mdx b/versioned_docs/version-2.18/reference/subsystems/docker.mdx index e92de9e64..2afeabfa8 100644 --- a/versioned_docs/version-2.18/reference/subsystems/docker.mdx +++ b/versioned_docs/version-2.18/reference/subsystems/docker.mdx @@ -202,7 +202,7 @@ Additional arguments to use for `docker run` invocations. Example: ``` -$ scie-pants-linux-x86_64 run --docker-run-args="-p 127.0.0.1:80:8080/tcp --name demo" src/example:image -- [image entrypoint args] +$ pants run --docker-run-args="-p 127.0.0.1:80:8080/tcp --name demo" src/example:image -- [image entrypoint args] ``` To provide the top-level options to the `docker` client, use `[docker].env_vars` to configure the [Environment variables](https://docs.docker.com/engine/reference/commandline/cli/#environment-variables) as appropriate. diff --git a/versioned_docs/version-2.18/reference/subsystems/flake8.mdx b/versioned_docs/version-2.18/reference/subsystems/flake8.mdx index 0d397351c..9444290ca 100644 --- a/versioned_docs/version-2.18/reference/subsystems/flake8.mdx +++ b/versioned_docs/version-2.18/reference/subsystems/flake8.mdx @@ -25,7 +25,7 @@ Config section: `[flake8]` default_repr={`False`} > -If true, don't use Flake8 when running `scie-pants-linux-x86_64 lint`. +If true, don't use Flake8 when running `pants lint`. diff --git a/versioned_docs/version-2.18/reference/subsystems/go-test.mdx b/versioned_docs/version-2.18/reference/subsystems/go-test.mdx index f3fd9afb4..125a6e1b5 100644 --- a/versioned_docs/version-2.18/reference/subsystems/go-test.mdx +++ b/versioned_docs/version-2.18/reference/subsystems/go-test.mdx @@ -88,7 +88,7 @@ This option is similar to the `go test -coverpkg` option, but without support cu default_repr={`False`} > -If true, don't use Go test binary when running `scie-pants-linux-x86_64 test`. +If true, don't use Go test binary when running `pants test`. diff --git a/versioned_docs/version-2.18/reference/subsystems/gofmt.mdx b/versioned_docs/version-2.18/reference/subsystems/gofmt.mdx index 0e737213e..b4fad02eb 100644 --- a/versioned_docs/version-2.18/reference/subsystems/gofmt.mdx +++ b/versioned_docs/version-2.18/reference/subsystems/gofmt.mdx @@ -25,7 +25,7 @@ Config section: `[gofmt]` default_repr={`False`} > -If true, don't use gofmt when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use gofmt when running `pants fmt` and `pants lint`. diff --git a/versioned_docs/version-2.18/reference/subsystems/google-java-format.mdx b/versioned_docs/version-2.18/reference/subsystems/google-java-format.mdx index 4860b700b..e4c631876 100644 --- a/versioned_docs/version-2.18/reference/subsystems/google-java-format.mdx +++ b/versioned_docs/version-2.18/reference/subsystems/google-java-format.mdx @@ -25,7 +25,7 @@ Config section: `[google-java-format]` default_repr={`False`} > -If true, don't use Google Java Format when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use Google Java Format when running `pants fmt` and `pants lint`. @@ -79,7 +79,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.18.0rc5/src/python/pants/backend/java/lint/google_java_format/google_java_format.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=google-java-format`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=google-java-format`. diff --git a/versioned_docs/version-2.18/reference/subsystems/hadolint.mdx b/versioned_docs/version-2.18/reference/subsystems/hadolint.mdx index 623fdcf4c..3b385d923 100644 --- a/versioned_docs/version-2.18/reference/subsystems/hadolint.mdx +++ b/versioned_docs/version-2.18/reference/subsystems/hadolint.mdx @@ -25,7 +25,7 @@ Config section: `[hadolint]` default_repr={`False`} > -If true, don't use Hadolint when running `scie-pants-linux-x86_64 lint`. +If true, don't use Hadolint when running `pants lint`. diff --git a/versioned_docs/version-2.18/reference/subsystems/helm-unittest.mdx b/versioned_docs/version-2.18/reference/subsystems/helm-unittest.mdx index 87edf0793..6a3fe929a 100644 --- a/versioned_docs/version-2.18/reference/subsystems/helm-unittest.mdx +++ b/versioned_docs/version-2.18/reference/subsystems/helm-unittest.mdx @@ -50,7 +50,7 @@ Output type used for the test report. default_repr={`False`} > -If true, don't use helmunittestsubsystem when running `scie-pants-linux-x86_64 test`. +If true, don't use helmunittestsubsystem when running `pants test`. diff --git a/versioned_docs/version-2.18/reference/subsystems/isort.mdx b/versioned_docs/version-2.18/reference/subsystems/isort.mdx index aa711f7e0..1e40640dc 100644 --- a/versioned_docs/version-2.18/reference/subsystems/isort.mdx +++ b/versioned_docs/version-2.18/reference/subsystems/isort.mdx @@ -25,7 +25,7 @@ Config section: `[isort]` default_repr={`False`} > -If true, don't use isort when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use isort when running `pants fmt` and `pants lint`. diff --git a/versioned_docs/version-2.18/reference/subsystems/jarjar.mdx b/versioned_docs/version-2.18/reference/subsystems/jarjar.mdx index f63784701..2fca70e50 100644 --- a/versioned_docs/version-2.18/reference/subsystems/jarjar.mdx +++ b/versioned_docs/version-2.18/reference/subsystems/jarjar.mdx @@ -80,7 +80,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.18.0rc5/src/python/pants/jvm/shading/jarjar.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=jarjar`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=jarjar`. diff --git a/versioned_docs/version-2.18/reference/subsystems/junit.mdx b/versioned_docs/version-2.18/reference/subsystems/junit.mdx index 176b620e7..b4c8a328f 100644 --- a/versioned_docs/version-2.18/reference/subsystems/junit.mdx +++ b/versioned_docs/version-2.18/reference/subsystems/junit.mdx @@ -37,7 +37,7 @@ Arguments to pass directly to JUnit, e.g. `--junit-args='--disable-ansi-colors'` default_repr={`False`} > -If true, don't use JUnit when running `scie-pants-linux-x86_64 test`. +If true, don't use JUnit when running `pants test`. @@ -79,7 +79,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.18.0rc5/src/python/pants/jvm/test/junit.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=junit`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=junit`. diff --git a/versioned_docs/version-2.18/reference/subsystems/ktlint.mdx b/versioned_docs/version-2.18/reference/subsystems/ktlint.mdx index 62f027480..efaefef42 100644 --- a/versioned_docs/version-2.18/reference/subsystems/ktlint.mdx +++ b/versioned_docs/version-2.18/reference/subsystems/ktlint.mdx @@ -25,7 +25,7 @@ Config section: `[ktlint]` default_repr={`False`} > -If true, don't use Ktlint when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use Ktlint when running `pants fmt` and `pants lint`. @@ -67,7 +67,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.18.0rc5/src/python/pants/backend/kotlin/lint/ktlint/ktlint.lock for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=ktlint`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=ktlint`. diff --git a/versioned_docs/version-2.18/reference/subsystems/mypy.mdx b/versioned_docs/version-2.18/reference/subsystems/mypy.mdx index 089475143..a73a2a2e4 100644 --- a/versioned_docs/version-2.18/reference/subsystems/mypy.mdx +++ b/versioned_docs/version-2.18/reference/subsystems/mypy.mdx @@ -25,7 +25,7 @@ Config section: `[mypy]` default_repr={`False`} > -If true, don't use MyPy when running `scie-pants-linux-x86_64 check`. +If true, don't use MyPy when running `pants check`. diff --git a/versioned_docs/version-2.18/reference/subsystems/nodejs.mdx b/versioned_docs/version-2.18/reference/subsystems/nodejs.mdx index 436271a89..bfb740f3a 100644 --- a/versioned_docs/version-2.18/reference/subsystems/nodejs.mdx +++ b/versioned_docs/version-2.18/reference/subsystems/nodejs.mdx @@ -136,7 +136,7 @@ Specifying a resolve name is optional. If unspecified, the default resolve name Example: An npm lockfile located at `src/js/package/package-lock.json' will result in a resolve named `js.package`, assuming src/ is a source root. -Run `scie-pants-linux-x86_64 generate-lockfiles` to generate the lockfile(s). +Run `pants generate-lockfiles` to generate the lockfile(s). diff --git a/versioned_docs/version-2.18/reference/subsystems/preamble.mdx b/versioned_docs/version-2.18/reference/subsystems/preamble.mdx index 8577e4ba8..27fb5eb3f 100644 --- a/versioned_docs/version-2.18/reference/subsystems/preamble.mdx +++ b/versioned_docs/version-2.18/reference/subsystems/preamble.mdx @@ -29,7 +29,7 @@ Config section: `[preamble]` default_repr={`False`} > -If true, don't use preamble when running `scie-pants-linux-x86_64 fmt`. +If true, don't use preamble when running `pants fmt`. diff --git a/versioned_docs/version-2.18/reference/subsystems/protobuf-java-grpc.mdx b/versioned_docs/version-2.18/reference/subsystems/protobuf-java-grpc.mdx index 03dd94b1f..c5eb0a704 100644 --- a/versioned_docs/version-2.18/reference/subsystems/protobuf-java-grpc.mdx +++ b/versioned_docs/version-2.18/reference/subsystems/protobuf-java-grpc.mdx @@ -57,7 +57,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.18.0rc5/src/python/pants/backend/codegen/protobuf/java/grpc-java.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=protobuf-java-grpc`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=protobuf-java-grpc`. diff --git a/versioned_docs/version-2.18/reference/subsystems/pydocstyle.mdx b/versioned_docs/version-2.18/reference/subsystems/pydocstyle.mdx index c9fe69e53..ab49eabfb 100644 --- a/versioned_docs/version-2.18/reference/subsystems/pydocstyle.mdx +++ b/versioned_docs/version-2.18/reference/subsystems/pydocstyle.mdx @@ -25,7 +25,7 @@ Config section: `[pydocstyle]` default_repr={`False`} > -If true, don't use Pydocstyle when running `scie-pants-linux-x86_64 lint`. +If true, don't use Pydocstyle when running `pants lint`. diff --git a/versioned_docs/version-2.18/reference/subsystems/pylint.mdx b/versioned_docs/version-2.18/reference/subsystems/pylint.mdx index 24e514922..71b11c51e 100644 --- a/versioned_docs/version-2.18/reference/subsystems/pylint.mdx +++ b/versioned_docs/version-2.18/reference/subsystems/pylint.mdx @@ -25,7 +25,7 @@ Config section: `[pylint]` default_repr={`False`} > -If true, don't use Pylint when running `scie-pants-linux-x86_64 lint`. +If true, don't use Pylint when running `pants lint`. diff --git a/versioned_docs/version-2.18/reference/subsystems/pytest.mdx b/versioned_docs/version-2.18/reference/subsystems/pytest.mdx index e9da9da04..d8a59d6a2 100644 --- a/versioned_docs/version-2.18/reference/subsystems/pytest.mdx +++ b/versioned_docs/version-2.18/reference/subsystems/pytest.mdx @@ -51,7 +51,7 @@ NOTE: Enabling `pytest-xdist` can cause high-level scoped fixtures (for example default_repr={`False`} > -If true, don't use Pytest when running `scie-pants-linux-x86_64 test`. +If true, don't use Pytest when running `pants test`. diff --git a/versioned_docs/version-2.18/reference/subsystems/python-infer.mdx b/versioned_docs/version-2.18/reference/subsystems/python-infer.mdx index a26783884..21d901feb 100644 --- a/versioned_docs/version-2.18/reference/subsystems/python-infer.mdx +++ b/versioned_docs/version-2.18/reference/subsystems/python-infer.mdx @@ -94,7 +94,7 @@ If `--assets` is True, treat valid-looking strings with at least this many forwa Infer a target's dependencies on any `__init__.py` files in the packages it is located in (recursively upward in the directory structure). -Even if this is set to `never` or `content_only`, Pants will still always include any ancestor `__init__.py` files in the sandbox. Only, they will not be "proper" dependencies, e.g. they will not show up in `scie-pants-linux-x86_64 dependencies` and their own dependencies will not be used. +Even if this is set to `never` or `content_only`, Pants will still always include any ancestor `__init__.py` files in the sandbox. Only, they will not be "proper" dependencies, e.g. they will not show up in `pants dependencies` and their own dependencies will not be used. By default, Pants only adds a "proper" dependency if there is content in the `__init__.py` file. This makes sure that dependencies are added when likely necessary to build, while also avoiding adding unnecessary dependencies. While accurate, those unnecessary dependencies can complicate setting metadata like the `interpreter_constraints` and `resolve` fields. @@ -199,7 +199,7 @@ As a result of the switch, cold-cache performance improved by a factor of about After leaving this defaulted to disabled for a release cycle, Pants 2.18 started defaulting to enabling this. -If you think the new behaviour is causing problems, it is recommended that you run `scie-pants-linux-x86_64 peek :: > before.json` and then `scie-pants-linux-x86_64 --python-infer-use-rust-parser=False peek :: > after.json` and compare the two results. +If you think the new behaviour is causing problems, it is recommended that you run `pants peek :: > before.json` and then `pants --python-infer-use-rust-parser=False peek :: > after.json` and compare the two results. If you think there is a bug and need to disable it, please file an issue: https://github.com/pantsbuild/pants/issues/new/choose. diff --git a/versioned_docs/version-2.18/reference/subsystems/python.mdx b/versioned_docs/version-2.18/reference/subsystems/python.mdx index 149f16997..7115f21a8 100644 --- a/versioned_docs/version-2.18/reference/subsystems/python.mdx +++ b/versioned_docs/version-2.18/reference/subsystems/python.mdx @@ -107,14 +107,14 @@ A mapping of logical names to lockfile paths used in your project. Many organizations only need a single resolve for their whole project, which is a good default and often the simplest thing to do. However, you may need multiple resolves, such as if you use two conflicting versions of a requirement in your repository. -If you only need a single resolve, run `scie-pants-linux-x86_64 generate-lockfiles` to generate the lockfile. +If you only need a single resolve, run `pants generate-lockfiles` to generate the lockfile. If you need multiple resolves: 1. Via this option, define multiple resolve names and their lockfile paths. The names should be meaningful to your repository, such as `data-science` or `pants-plugins`. 2. Set the default with `[python].default_resolve`. 3. Update your `python_requirement` targets with the `resolve` field to declare which resolve they should be available in. They default to `[python].default_resolve`, so you only need to update targets that you want in non-default resolves. (Often you'll set this via the `python_requirements` or `poetry_requirements` target generators) -4. Run `scie-pants-linux-x86_64 generate-lockfiles` to generate the lockfiles. If the results aren't what you'd expect, adjust the prior step. +4. Run `pants generate-lockfiles` to generate the lockfiles. If the results aren't what you'd expect, adjust the prior step. 5. Update any targets like `python_source` / `python_sources`, `python_test` / `python_tests`, and `pex_binary` which need to set a non-default resolve with the `resolve` field. If a target can work with multiple resolves, you can either use the `parametrize` mechanism or manually create a distinct target per resolve. See https://www.pantsbuild.org/v2.18/docs/targets for information about `parametrize`. @@ -416,7 +416,7 @@ If another targets address is in conflict with the created lockfile target, it w env_repr='PANTS_PYTHON_REQUIREMENT_CONSTRAINTS' default_repr={`None`} removal_version='3.0.0.dev0' - removal_hint={'We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.

To migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `scie-pants-linux-x86_64 generate-lockfiles`.'} + removal_hint={'We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.

To migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `pants generate-lockfiles`.'} > When resolving third-party requirements for your own code (vs. tools you run), use this constraints file to determine which versions to use. @@ -436,7 +436,7 @@ This only applies when resolving user requirements, rather than tools you run li env_repr='PANTS_PYTHON_RESOLVE_ALL_CONSTRAINTS' default_repr={`True`} removal_version='3.0.0.dev0' - removal_hint={'We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.

To migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `scie-pants-linux-x86_64 generate-lockfiles`.'} + removal_hint={'We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.

To migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `pants generate-lockfiles`.'} > (Only relevant when using `[python].requirement_constraints.`) If enabled, when resolving requirements, Pants will first resolve your entire constraints file as a single global resolve. Then, if the code uses a subset of your constraints file, Pants will extract the relevant requirements from that global resolve so that only what's actually needed gets used. If disabled, Pants will not use a global resolve and will resolve each subset of your requirements independently. diff --git a/versioned_docs/version-2.18/reference/subsystems/pytype.mdx b/versioned_docs/version-2.18/reference/subsystems/pytype.mdx index 506e2da7f..48a78b0a1 100644 --- a/versioned_docs/version-2.18/reference/subsystems/pytype.mdx +++ b/versioned_docs/version-2.18/reference/subsystems/pytype.mdx @@ -25,7 +25,7 @@ Config section: `[pytype]` default_repr={`False`} > -If true, don't use Pytype when running `scie-pants-linux-x86_64 check`. +If true, don't use Pytype when running `pants check`. diff --git a/versioned_docs/version-2.18/reference/subsystems/pyupgrade.mdx b/versioned_docs/version-2.18/reference/subsystems/pyupgrade.mdx index a8142f056..3dee179a0 100644 --- a/versioned_docs/version-2.18/reference/subsystems/pyupgrade.mdx +++ b/versioned_docs/version-2.18/reference/subsystems/pyupgrade.mdx @@ -25,7 +25,7 @@ Config section: `[pyupgrade]` default_repr={`False`} > -If true, don't use pyupgrade when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use pyupgrade when running `pants fmt` and `pants lint`. diff --git a/versioned_docs/version-2.18/reference/subsystems/regex-lint.mdx b/versioned_docs/version-2.18/reference/subsystems/regex-lint.mdx index a919e6ff4..20d8d1542 100644 --- a/versioned_docs/version-2.18/reference/subsystems/regex-lint.mdx +++ b/versioned_docs/version-2.18/reference/subsystems/regex-lint.mdx @@ -29,7 +29,7 @@ Config section: `[regex-lint]` default_repr={`False`} > -If true, don't use regex-lint when running `scie-pants-linux-x86_64 lint`. +If true, don't use regex-lint when running `pants lint`. diff --git a/versioned_docs/version-2.18/reference/subsystems/ruff.mdx b/versioned_docs/version-2.18/reference/subsystems/ruff.mdx index f7c858ef1..7f5388d07 100644 --- a/versioned_docs/version-2.18/reference/subsystems/ruff.mdx +++ b/versioned_docs/version-2.18/reference/subsystems/ruff.mdx @@ -25,7 +25,7 @@ Config section: `[ruff]` default_repr={`False`} > -If true, don't use Ruff when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use Ruff when running `pants fmt` and `pants lint`. diff --git a/versioned_docs/version-2.18/reference/subsystems/scalafmt.mdx b/versioned_docs/version-2.18/reference/subsystems/scalafmt.mdx index e46eef232..15157d1db 100644 --- a/versioned_docs/version-2.18/reference/subsystems/scalafmt.mdx +++ b/versioned_docs/version-2.18/reference/subsystems/scalafmt.mdx @@ -25,7 +25,7 @@ Config section: `[scalafmt]` default_repr={`False`} > -If true, don't use scalafmt when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use scalafmt when running `pants fmt` and `pants lint`. @@ -67,7 +67,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.18.0rc5/src/python/pants/backend/scala/lint/scalafmt/scalafmt.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalafmt`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=scalafmt`. diff --git a/versioned_docs/version-2.18/reference/subsystems/scalapb.mdx b/versioned_docs/version-2.18/reference/subsystems/scalapb.mdx index 053de1cb9..c5e54312c 100644 --- a/versioned_docs/version-2.18/reference/subsystems/scalapb.mdx +++ b/versioned_docs/version-2.18/reference/subsystems/scalapb.mdx @@ -69,7 +69,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.18.0rc5/src/python/pants/backend/codegen/protobuf/scala/scalapbc.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalapb`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=scalapb`. diff --git a/versioned_docs/version-2.18/reference/subsystems/scalatest.mdx b/versioned_docs/version-2.18/reference/subsystems/scalatest.mdx index 3e73a054f..4cdcc971d 100644 --- a/versioned_docs/version-2.18/reference/subsystems/scalatest.mdx +++ b/versioned_docs/version-2.18/reference/subsystems/scalatest.mdx @@ -39,7 +39,7 @@ See https://www.scalatest.org/user_guide/using_the_runner for supported argument default_repr={`False`} > -If true, don't use Scalatest when running `scie-pants-linux-x86_64 test`. +If true, don't use Scalatest when running `pants test`. @@ -81,7 +81,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.18.0rc5/src/python/pants/backend/scala/subsystems/scalatest.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalatest`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=scalatest`. diff --git a/versioned_docs/version-2.18/reference/subsystems/shell-test.mdx b/versioned_docs/version-2.18/reference/subsystems/shell-test.mdx index 3c748d702..1a371c907 100644 --- a/versioned_docs/version-2.18/reference/subsystems/shell-test.mdx +++ b/versioned_docs/version-2.18/reference/subsystems/shell-test.mdx @@ -25,7 +25,7 @@ Config section: `[shell-test]` default_repr={`False`} > -If true, don't use Test with shell scripts when running `scie-pants-linux-x86_64 test`. +If true, don't use Test with shell scripts when running `pants test`. diff --git a/versioned_docs/version-2.18/reference/subsystems/shellcheck.mdx b/versioned_docs/version-2.18/reference/subsystems/shellcheck.mdx index 822d54955..09fe7d8d1 100644 --- a/versioned_docs/version-2.18/reference/subsystems/shellcheck.mdx +++ b/versioned_docs/version-2.18/reference/subsystems/shellcheck.mdx @@ -25,7 +25,7 @@ Config section: `[shellcheck]` default_repr={`False`} > -If true, don't use Shellcheck when running `scie-pants-linux-x86_64 lint`. +If true, don't use Shellcheck when running `pants lint`. diff --git a/versioned_docs/version-2.18/reference/subsystems/shfmt.mdx b/versioned_docs/version-2.18/reference/subsystems/shfmt.mdx index b28e0433d..1050b09a8 100644 --- a/versioned_docs/version-2.18/reference/subsystems/shfmt.mdx +++ b/versioned_docs/version-2.18/reference/subsystems/shfmt.mdx @@ -25,7 +25,7 @@ Config section: `[shfmt]` default_repr={`False`} > -If true, don't use shfmt when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use shfmt when running `pants fmt` and `pants lint`. diff --git a/versioned_docs/version-2.18/reference/subsystems/shunit2.mdx b/versioned_docs/version-2.18/reference/subsystems/shunit2.mdx index 74fccd0df..510f62cc5 100644 --- a/versioned_docs/version-2.18/reference/subsystems/shunit2.mdx +++ b/versioned_docs/version-2.18/reference/subsystems/shunit2.mdx @@ -25,7 +25,7 @@ Config section: `[shunit2]` default_repr={`False`} > -If true, don't use shunit2 when running `scie-pants-linux-x86_64 test`. +If true, don't use shunit2 when running `pants test`. diff --git a/versioned_docs/version-2.18/reference/subsystems/spectral.mdx b/versioned_docs/version-2.18/reference/subsystems/spectral.mdx index 2f9588306..a5ab244bd 100644 --- a/versioned_docs/version-2.18/reference/subsystems/spectral.mdx +++ b/versioned_docs/version-2.18/reference/subsystems/spectral.mdx @@ -25,7 +25,7 @@ Config section: `[spectral]` default_repr={`False`} > -If true, don't use Spectral when running `scie-pants-linux-x86_64 lint`. +If true, don't use Spectral when running `pants lint`. diff --git a/versioned_docs/version-2.18/reference/subsystems/terraform-fmt.mdx b/versioned_docs/version-2.18/reference/subsystems/terraform-fmt.mdx index 968e542ad..c675ed16b 100644 --- a/versioned_docs/version-2.18/reference/subsystems/terraform-fmt.mdx +++ b/versioned_docs/version-2.18/reference/subsystems/terraform-fmt.mdx @@ -25,7 +25,7 @@ Config section: `[terraform-fmt]` default_repr={`False`} > -If true, don't use `terraform fmt` when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use `terraform fmt` when running `pants fmt` and `pants lint`. diff --git a/versioned_docs/version-2.18/reference/subsystems/terraform-validate.mdx b/versioned_docs/version-2.18/reference/subsystems/terraform-validate.mdx index a84bf5b6c..e7686bc2f 100644 --- a/versioned_docs/version-2.18/reference/subsystems/terraform-validate.mdx +++ b/versioned_docs/version-2.18/reference/subsystems/terraform-validate.mdx @@ -25,7 +25,7 @@ Config section: `[terraform-validate]` default_repr={`False`} > -If true, don't use `terraform validate` when running `scie-pants-linux-x86_64 check`. +If true, don't use `terraform validate` when running `pants check`. diff --git a/versioned_docs/version-2.18/reference/subsystems/twine.mdx b/versioned_docs/version-2.18/reference/subsystems/twine.mdx index 7fb4fe588..b4fa8e1b4 100644 --- a/versioned_docs/version-2.18/reference/subsystems/twine.mdx +++ b/versioned_docs/version-2.18/reference/subsystems/twine.mdx @@ -25,7 +25,7 @@ Config section: `[twine]` default_repr={`False`} > -If true, don't use Twine when running `scie-pants-linux-x86_64 publish`. +If true, don't use Twine when running `pants publish`. diff --git a/versioned_docs/version-2.18/reference/subsystems/yamllint.mdx b/versioned_docs/version-2.18/reference/subsystems/yamllint.mdx index c807f56be..0fc1bb13f 100644 --- a/versioned_docs/version-2.18/reference/subsystems/yamllint.mdx +++ b/versioned_docs/version-2.18/reference/subsystems/yamllint.mdx @@ -61,7 +61,7 @@ Arguments to pass directly to Yamllint, e.g. `--yamllint-args='-d relaxed'`. default_repr={`False`} > -If true, don't use Yamllint when running `scie-pants-linux-x86_64 lint`. +If true, don't use Yamllint when running `pants lint`. diff --git a/versioned_docs/version-2.18/reference/subsystems/yapf.mdx b/versioned_docs/version-2.18/reference/subsystems/yapf.mdx index d7a95a452..0ac558b28 100644 --- a/versioned_docs/version-2.18/reference/subsystems/yapf.mdx +++ b/versioned_docs/version-2.18/reference/subsystems/yapf.mdx @@ -25,7 +25,7 @@ Config section: `[yapf]` default_repr={`False`} > -If true, don't use yapf when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use yapf when running `pants fmt` and `pants lint`. diff --git a/versioned_docs/version-2.18/reference/targets/adhoc_tool.mdx b/versioned_docs/version-2.18/reference/targets/adhoc_tool.mdx index 4378a4583..985e36caa 100644 --- a/versioned_docs/version-2.18/reference/targets/adhoc_tool.mdx +++ b/versioned_docs/version-2.18/reference/targets/adhoc_tool.mdx @@ -38,7 +38,7 @@ Backend: `pants.backend.experimental.adhoc` @@ -51,7 +51,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.18/reference/targets/archive.mdx b/versioned_docs/version-2.18/reference/targets/archive.mdx index 534717852..c52c5ec85 100644 --- a/versioned_docs/version-2.18/reference/targets/archive.mdx +++ b/versioned_docs/version-2.18/reference/targets/archive.mdx @@ -24,7 +24,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -52,7 +52,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. @@ -65,11 +65,11 @@ Warning: setting this value risks naming collisions with other package targets y default_repr={`None`} > -Addresses to any targets that can be built with `scie-pants-linux-x86_64 package`, e.g. `["project:app"]`. +Addresses to any targets that can be built with `pants package`, e.g. `["project:app"]`. -Pants will build the assets as if you had run `scie-pants-linux-x86_64 package`. It will include the results in your archive using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). +Pants will build the assets as if you had run `pants package`. It will include the results in your archive using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). -You can include anything that can be built by `scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_aws_lambda_function`, or even another `archive`. +You can include anything that can be built by `pants package`, e.g. a `pex_binary`, `python_aws_lambda_function`, or even another `archive`. diff --git a/versioned_docs/version-2.18/reference/targets/deploy_jar.mdx b/versioned_docs/version-2.18/reference/targets/deploy_jar.mdx index eb0eb5f25..774318363 100644 --- a/versioned_docs/version-2.18/reference/targets/deploy_jar.mdx +++ b/versioned_docs/version-2.18/reference/targets/deploy_jar.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.experimental.java` @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -65,7 +65,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. @@ -80,9 +80,9 @@ Warning: setting this value risks naming collisions with other package targets y Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.18/reference/targets/docker_environment.mdx b/versioned_docs/version-2.18/reference/targets/docker_environment.mdx index 36d94cc0c..4ed09d62d 100644 --- a/versioned_docs/version-2.18/reference/targets/docker_environment.mdx +++ b/versioned_docs/version-2.18/reference/targets/docker_environment.mdx @@ -30,7 +30,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.18/reference/targets/docker_image.mdx b/versioned_docs/version-2.18/reference/targets/docker_image.mdx index dd7073caf..92749aae5 100644 --- a/versioned_docs/version-2.18/reference/targets/docker_image.mdx +++ b/versioned_docs/version-2.18/reference/targets/docker_image.mdx @@ -39,7 +39,7 @@ Backend: `pants.backend.docker` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -52,7 +52,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -78,9 +78,9 @@ Use `[docker].build_args` to set default build args for all images. Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -291,7 +291,7 @@ See [Docker documentation](https://docs.docker.com/develop/develop-images/build_ default_repr={`False`} > -If true, do not push this image to registries when running `scie-pants-linux-x86_64 publish`. +If true, do not push this image to registries when running `pants publish`. @@ -369,7 +369,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. diff --git a/versioned_docs/version-2.18/reference/targets/experimental_test_shell_command.mdx b/versioned_docs/version-2.18/reference/targets/experimental_test_shell_command.mdx index d9cbf0eed..58eccc73a 100644 --- a/versioned_docs/version-2.18/reference/targets/experimental_test_shell_command.mdx +++ b/versioned_docs/version-2.18/reference/targets/experimental_test_shell_command.mdx @@ -39,7 +39,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -52,7 +52,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.18/reference/targets/experimental_wrap_as_go_package_sources.mdx b/versioned_docs/version-2.18/reference/targets/experimental_wrap_as_go_package_sources.mdx index 76db3f1ba..0630639a4 100644 --- a/versioned_docs/version-2.18/reference/targets/experimental_wrap_as_go_package_sources.mdx +++ b/versioned_docs/version-2.18/reference/targets/experimental_wrap_as_go_package_sources.mdx @@ -30,7 +30,7 @@ Backend: `pants.backend.experimental.go` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.18/reference/targets/experimental_wrap_as_java_sources.mdx b/versioned_docs/version-2.18/reference/targets/experimental_wrap_as_java_sources.mdx index 940029f9b..ff3e04681 100644 --- a/versioned_docs/version-2.18/reference/targets/experimental_wrap_as_java_sources.mdx +++ b/versioned_docs/version-2.18/reference/targets/experimental_wrap_as_java_sources.mdx @@ -30,7 +30,7 @@ Backend: `pants.backend.experimental.java` @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.18/reference/targets/experimental_wrap_as_kotlin_sources.mdx b/versioned_docs/version-2.18/reference/targets/experimental_wrap_as_kotlin_sources.mdx index 003b6ad9a..bae3428a7 100644 --- a/versioned_docs/version-2.18/reference/targets/experimental_wrap_as_kotlin_sources.mdx +++ b/versioned_docs/version-2.18/reference/targets/experimental_wrap_as_kotlin_sources.mdx @@ -30,7 +30,7 @@ Backend: `pants.backend.experimental.kotlin` @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.18/reference/targets/experimental_wrap_as_python_sources.mdx b/versioned_docs/version-2.18/reference/targets/experimental_wrap_as_python_sources.mdx index a341b498b..5751ec09f 100644 --- a/versioned_docs/version-2.18/reference/targets/experimental_wrap_as_python_sources.mdx +++ b/versioned_docs/version-2.18/reference/targets/experimental_wrap_as_python_sources.mdx @@ -30,7 +30,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.18/reference/targets/experimental_wrap_as_resources.mdx b/versioned_docs/version-2.18/reference/targets/experimental_wrap_as_resources.mdx index bdb4704b5..7f60252a5 100644 --- a/versioned_docs/version-2.18/reference/targets/experimental_wrap_as_resources.mdx +++ b/versioned_docs/version-2.18/reference/targets/experimental_wrap_as_resources.mdx @@ -30,7 +30,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.18/reference/targets/experimental_wrap_as_scala_sources.mdx b/versioned_docs/version-2.18/reference/targets/experimental_wrap_as_scala_sources.mdx index df94d3733..5548c481b 100644 --- a/versioned_docs/version-2.18/reference/targets/experimental_wrap_as_scala_sources.mdx +++ b/versioned_docs/version-2.18/reference/targets/experimental_wrap_as_scala_sources.mdx @@ -30,7 +30,7 @@ Backend: `pants.backend.experimental.scala` @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.18/reference/targets/file.mdx b/versioned_docs/version-2.18/reference/targets/file.mdx index 9f9ef1da9..b814b434b 100644 --- a/versioned_docs/version-2.18/reference/targets/file.mdx +++ b/versioned_docs/version-2.18/reference/targets/file.mdx @@ -26,7 +26,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -52,9 +52,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.18/reference/targets/files.mdx b/versioned_docs/version-2.18/reference/targets/files.mdx index 5da99bc60..68adbc45f 100644 --- a/versioned_docs/version-2.18/reference/targets/files.mdx +++ b/versioned_docs/version-2.18/reference/targets/files.mdx @@ -24,7 +24,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -94,9 +94,9 @@ You can specify the same file name in multiple keys, so long as you don't o Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.18/reference/targets/go_binary.mdx b/versioned_docs/version-2.18/reference/targets/go_binary.mdx index 55a27e2dd..e1a85a7a6 100644 --- a/versioned_docs/version-2.18/reference/targets/go_binary.mdx +++ b/versioned_docs/version-2.18/reference/targets/go_binary.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.go` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -52,7 +52,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. diff --git a/versioned_docs/version-2.18/reference/targets/go_mod.mdx b/versioned_docs/version-2.18/reference/targets/go_mod.mdx index ea3d4e8ad..a0cfd6173 100644 --- a/versioned_docs/version-2.18/reference/targets/go_mod.mdx +++ b/versioned_docs/version-2.18/reference/targets/go_mod.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.go` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.18/reference/targets/go_package.mdx b/versioned_docs/version-2.18/reference/targets/go_package.mdx index ed56089fc..fbb802ab4 100644 --- a/versioned_docs/version-2.18/reference/targets/go_package.mdx +++ b/versioned_docs/version-2.18/reference/targets/go_package.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.experimental.go` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -52,9 +52,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.18/reference/targets/go_third_party_package.mdx b/versioned_docs/version-2.18/reference/targets/go_third_party_package.mdx index 89d297917..f6dd9e5ee 100644 --- a/versioned_docs/version-2.18/reference/targets/go_third_party_package.mdx +++ b/versioned_docs/version-2.18/reference/targets/go_third_party_package.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.go` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -54,9 +54,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.18/reference/targets/helm_artifact.mdx b/versioned_docs/version-2.18/reference/targets/helm_artifact.mdx index 0c94682be..df2c66974 100644 --- a/versioned_docs/version-2.18/reference/targets/helm_artifact.mdx +++ b/versioned_docs/version-2.18/reference/targets/helm_artifact.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.helm` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.18/reference/targets/helm_chart.mdx b/versioned_docs/version-2.18/reference/targets/helm_chart.mdx index cbf1ddc49..5a811b8c3 100644 --- a/versioned_docs/version-2.18/reference/targets/helm_chart.mdx +++ b/versioned_docs/version-2.18/reference/targets/helm_chart.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.helm` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -76,9 +76,9 @@ Example: `sources=['values.yaml', 'templates/*.yaml', '!values_ignore.yaml']` Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -99,7 +99,7 @@ If undefined, this will use the path to the BUILD file, For example, `src/charts Regardless of whether you use the default or set this field, the path will end with Helms's file format of `-.tgz`, where `chart_name` and `chart_version` are the values extracted from the Chart.yaml file. So, using the default for this field, the target `src/charts/mychart:tgt_name` might have a final path like `src.charts.mychart/tgt_name/mychart-0.1.0.tgz`. -When running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. @@ -183,7 +183,7 @@ The above example shows two valid `registry` options: using an alias to a config default_repr={`False`} > -If set to true, do not push this Helm chart to registries when running `scie-pants-linux-x86_64 publish`. +If set to true, do not push this Helm chart to registries when running `pants publish`. @@ -194,7 +194,7 @@ If set to true, do not push this Helm chart to registries when running `scie-pan default_repr={`False`} > -If set to true, do not run any linting in this Helm chart when running `scie-pants-linux-x86_64 lint`. +If set to true, do not run any linting in this Helm chart when running `pants lint`. diff --git a/versioned_docs/version-2.18/reference/targets/helm_deployment.mdx b/versioned_docs/version-2.18/reference/targets/helm_deployment.mdx index dd2fe06e4..736bae300 100644 --- a/versioned_docs/version-2.18/reference/targets/helm_deployment.mdx +++ b/versioned_docs/version-2.18/reference/targets/helm_deployment.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.helm` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -72,9 +72,9 @@ Name of the release used in the deployment. If not set, the target name will be Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.18/reference/targets/helm_unittest_test.mdx b/versioned_docs/version-2.18/reference/targets/helm_unittest_test.mdx index f75a43706..d7cb4dd80 100644 --- a/versioned_docs/version-2.18/reference/targets/helm_unittest_test.mdx +++ b/versioned_docs/version-2.18/reference/targets/helm_unittest_test.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.helm` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -63,9 +63,9 @@ Path is relative to the BUILD file's directory, e.g. `source='example.ext'` Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.18/reference/targets/helm_unittest_tests.mdx b/versioned_docs/version-2.18/reference/targets/helm_unittest_tests.mdx index b8280998f..c994a7105 100644 --- a/versioned_docs/version-2.18/reference/targets/helm_unittest_tests.mdx +++ b/versioned_docs/version-2.18/reference/targets/helm_unittest_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.helm` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -65,9 +65,9 @@ Example: `sources=['*_test.yaml', '!ignore_test.yaml']` Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.18/reference/targets/java_source.mdx b/versioned_docs/version-2.18/reference/targets/java_source.mdx index 72e09e5d0..4ba82bc8b 100644 --- a/versioned_docs/version-2.18/reference/targets/java_source.mdx +++ b/versioned_docs/version-2.18/reference/targets/java_source.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.java` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.18/reference/targets/java_sources.mdx b/versioned_docs/version-2.18/reference/targets/java_sources.mdx index 4449eb514..de38e0b49 100644 --- a/versioned_docs/version-2.18/reference/targets/java_sources.mdx +++ b/versioned_docs/version-2.18/reference/targets/java_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.java` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -77,9 +77,9 @@ If true, don't run Google Java Format on this target's code. Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.18/reference/targets/junit_test.mdx b/versioned_docs/version-2.18/reference/targets/junit_test.mdx index 24136c34a..85d49c629 100644 --- a/versioned_docs/version-2.18/reference/targets/junit_test.mdx +++ b/versioned_docs/version-2.18/reference/targets/junit_test.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.java` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -91,9 +91,9 @@ This will be merged with and override values from `[test].extra_env_vars`. Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.18/reference/targets/junit_tests.mdx b/versioned_docs/version-2.18/reference/targets/junit_tests.mdx index dd5f0e339..ee5419530 100644 --- a/versioned_docs/version-2.18/reference/targets/junit_tests.mdx +++ b/versioned_docs/version-2.18/reference/targets/junit_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.java` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -93,9 +93,9 @@ This will be merged with and override values from `[test].extra_env_vars`. Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.18/reference/targets/jvm_artifact.mdx b/versioned_docs/version-2.18/reference/targets/jvm_artifact.mdx index f935b3358..ead71287d 100644 --- a/versioned_docs/version-2.18/reference/targets/jvm_artifact.mdx +++ b/versioned_docs/version-2.18/reference/targets/jvm_artifact.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.java` @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.18/reference/targets/jvm_war.mdx b/versioned_docs/version-2.18/reference/targets/jvm_war.mdx index 007447e3f..b949fe9d7 100644 --- a/versioned_docs/version-2.18/reference/targets/jvm_war.mdx +++ b/versioned_docs/version-2.18/reference/targets/jvm_war.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.java` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -74,9 +74,9 @@ A list of addresses to `resources` and `files` targets with content to place in Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -126,7 +126,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. diff --git a/versioned_docs/version-2.18/reference/targets/kotlin_junit_test.mdx b/versioned_docs/version-2.18/reference/targets/kotlin_junit_test.mdx index abc022acd..222f1f9fa 100644 --- a/versioned_docs/version-2.18/reference/targets/kotlin_junit_test.mdx +++ b/versioned_docs/version-2.18/reference/targets/kotlin_junit_test.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.kotlin` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.18/reference/targets/kotlin_junit_tests.mdx b/versioned_docs/version-2.18/reference/targets/kotlin_junit_tests.mdx index 550ff50ae..2d80d87cb 100644 --- a/versioned_docs/version-2.18/reference/targets/kotlin_junit_tests.mdx +++ b/versioned_docs/version-2.18/reference/targets/kotlin_junit_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.kotlin` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -65,9 +65,9 @@ Example: `sources=['*Test.kt', '!TestIgnore.kt']` Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.18/reference/targets/kotlin_source.mdx b/versioned_docs/version-2.18/reference/targets/kotlin_source.mdx index bb78a2302..c79606ce2 100644 --- a/versioned_docs/version-2.18/reference/targets/kotlin_source.mdx +++ b/versioned_docs/version-2.18/reference/targets/kotlin_source.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.kotlin` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.18/reference/targets/kotlin_sources.mdx b/versioned_docs/version-2.18/reference/targets/kotlin_sources.mdx index 7838ae373..d48edefaa 100644 --- a/versioned_docs/version-2.18/reference/targets/kotlin_sources.mdx +++ b/versioned_docs/version-2.18/reference/targets/kotlin_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.kotlin` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -77,9 +77,9 @@ If true, don't run Ktlint on this target's code. Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.18/reference/targets/kotlinc_plugin.mdx b/versioned_docs/version-2.18/reference/targets/kotlinc_plugin.mdx index c8ad9eb36..828754fa0 100644 --- a/versioned_docs/version-2.18/reference/targets/kotlinc_plugin.mdx +++ b/versioned_docs/version-2.18/reference/targets/kotlinc_plugin.mdx @@ -34,7 +34,7 @@ Backend: `pants.backend.experimental.kotlin` @@ -47,7 +47,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.18/reference/targets/local_environment.mdx b/versioned_docs/version-2.18/reference/targets/local_environment.mdx index 2c04b85a3..1d2e1f114 100644 --- a/versioned_docs/version-2.18/reference/targets/local_environment.mdx +++ b/versioned_docs/version-2.18/reference/targets/local_environment.mdx @@ -30,7 +30,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.18/reference/targets/openapi_document.mdx b/versioned_docs/version-2.18/reference/targets/openapi_document.mdx index 980544ccc..77e38957a 100644 --- a/versioned_docs/version-2.18/reference/targets/openapi_document.mdx +++ b/versioned_docs/version-2.18/reference/targets/openapi_document.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.openapi` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.18/reference/targets/openapi_documents.mdx b/versioned_docs/version-2.18/reference/targets/openapi_documents.mdx index a912f4912..52ab7c31c 100644 --- a/versioned_docs/version-2.18/reference/targets/openapi_documents.mdx +++ b/versioned_docs/version-2.18/reference/targets/openapi_documents.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.openapi` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -77,9 +77,9 @@ If true, don't run `spectral lint` on this target's code. Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.18/reference/targets/openapi_source.mdx b/versioned_docs/version-2.18/reference/targets/openapi_source.mdx index 312e82d86..91d534433 100644 --- a/versioned_docs/version-2.18/reference/targets/openapi_source.mdx +++ b/versioned_docs/version-2.18/reference/targets/openapi_source.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.openapi` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.18/reference/targets/openapi_sources.mdx b/versioned_docs/version-2.18/reference/targets/openapi_sources.mdx index c7d494308..019faaf18 100644 --- a/versioned_docs/version-2.18/reference/targets/openapi_sources.mdx +++ b/versioned_docs/version-2.18/reference/targets/openapi_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.openapi` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -65,9 +65,9 @@ Example: `sources=['*.json']` Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.18/reference/targets/pants_requirements.mdx b/versioned_docs/version-2.18/reference/targets/pants_requirements.mdx index 2df0f954f..c37aabd33 100644 --- a/versioned_docs/version-2.18/reference/targets/pants_requirements.mdx +++ b/versioned_docs/version-2.18/reference/targets/pants_requirements.mdx @@ -30,7 +30,7 @@ Backend: `pants.backend.plugin_development` @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.18/reference/targets/pex_binaries.mdx b/versioned_docs/version-2.18/reference/targets/pex_binaries.mdx index b26c7e4c0..99892019d 100644 --- a/versioned_docs/version-2.18/reference/targets/pex_binaries.mdx +++ b/versioned_docs/version-2.18/reference/targets/pex_binaries.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -147,9 +147,9 @@ All dependencies must share the same value for their `resolve` field. Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.18/reference/targets/pex_binary.mdx b/versioned_docs/version-2.18/reference/targets/pex_binary.mdx index 25ba046ef..e66770f79 100644 --- a/versioned_docs/version-2.18/reference/targets/pex_binary.mdx +++ b/versioned_docs/version-2.18/reference/targets/pex_binary.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -101,9 +101,9 @@ All dependencies must share the same value for their `resolve` field. Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -398,7 +398,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. diff --git a/versioned_docs/version-2.18/reference/targets/pipenv_requirements.mdx b/versioned_docs/version-2.18/reference/targets/pipenv_requirements.mdx index e06585179..f67f613c7 100644 --- a/versioned_docs/version-2.18/reference/targets/pipenv_requirements.mdx +++ b/versioned_docs/version-2.18/reference/targets/pipenv_requirements.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.18/reference/targets/poetry_requirements.mdx b/versioned_docs/version-2.18/reference/targets/poetry_requirements.mdx index 82136c634..6edf88e02 100644 --- a/versioned_docs/version-2.18/reference/targets/poetry_requirements.mdx +++ b/versioned_docs/version-2.18/reference/targets/poetry_requirements.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.18/reference/targets/protobuf_source.mdx b/versioned_docs/version-2.18/reference/targets/protobuf_source.mdx index 779ebb8eb..9de4efce8 100644 --- a/versioned_docs/version-2.18/reference/targets/protobuf_source.mdx +++ b/versioned_docs/version-2.18/reference/targets/protobuf_source.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.codegen.protobuf.python Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -54,9 +54,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.18/reference/targets/protobuf_sources.mdx b/versioned_docs/version-2.18/reference/targets/protobuf_sources.mdx index 0ef79afba..08bddc240 100644 --- a/versioned_docs/version-2.18/reference/targets/protobuf_sources.mdx +++ b/versioned_docs/version-2.18/reference/targets/protobuf_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.codegen.protobuf.python Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -221,9 +221,9 @@ Whether to generate gRPC code or not. Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.18/reference/targets/pyoxidizer_binary.mdx b/versioned_docs/version-2.18/reference/targets/pyoxidizer_binary.mdx index eebaa5ddb..559b10b7f 100644 --- a/versioned_docs/version-2.18/reference/targets/pyoxidizer_binary.mdx +++ b/versioned_docs/version-2.18/reference/targets/pyoxidizer_binary.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.python.pac Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -58,7 +58,7 @@ If undefined, this will use the path to the BUILD file, followed by the target n Regardless of whether you use the default or set this field, the path will end with PyOxidizer's file format of `/{debug,release}/install/`, where `platform` is a Rust platform triplet like `aarch-64-apple-darwin` and `binary_name` is the value of the `binary_name` field. So, using the default for this field, the target `src/python/project:bin` might have a final path like `src.python.project/bin/aarch-64-apple-darwin/release/bin`. -When running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. diff --git a/versioned_docs/version-2.18/reference/targets/python_aws_lambda_function.mdx b/versioned_docs/version-2.18/reference/targets/python_aws_lambda_function.mdx index 3b610a8dd..9d5d8d73d 100644 --- a/versioned_docs/version-2.18/reference/targets/python_aws_lambda_function.mdx +++ b/versioned_docs/version-2.18/reference/targets/python_aws_lambda_function.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.awslambda.python` @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -54,7 +54,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. @@ -142,9 +142,9 @@ You can specify multiple valid environments by using `parametrize`. If `__local_ Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.18/reference/targets/python_aws_lambda_layer.mdx b/versioned_docs/version-2.18/reference/targets/python_aws_lambda_layer.mdx index a2ebd630a..76169e1d8 100644 --- a/versioned_docs/version-2.18/reference/targets/python_aws_lambda_layer.mdx +++ b/versioned_docs/version-2.18/reference/targets/python_aws_lambda_layer.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.awslambda.python` @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -54,7 +54,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. @@ -153,9 +153,9 @@ Whether to resolve first party sources and include them in the AWS Lambda artifa Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.18/reference/targets/python_distribution.mdx b/versioned_docs/version-2.18/reference/targets/python_distribution.mdx index 186b73073..9d0608231 100644 --- a/versioned_docs/version-2.18/reference/targets/python_distribution.mdx +++ b/versioned_docs/version-2.18/reference/targets/python_distribution.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -71,9 +71,9 @@ See https://www.pantsbuild.org/v2.18/docs/python-interpreter-compatibility for h Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -108,7 +108,7 @@ Note that Pants will assume that any value that either starts with `:` or has `/ Pants will attempt to infer dependencies, which you can confirm by running: ``` -scie-pants-linux-x86_64 dependencies +pants dependencies ``` diff --git a/versioned_docs/version-2.18/reference/targets/python_google_cloud_function.mdx b/versioned_docs/version-2.18/reference/targets/python_google_cloud_function.mdx index 0336bf841..2d92eec6d 100644 --- a/versioned_docs/version-2.18/reference/targets/python_google_cloud_function.mdx +++ b/versioned_docs/version-2.18/reference/targets/python_google_cloud_function.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.google_cloud_function.p Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -54,7 +54,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. @@ -69,9 +69,9 @@ Warning: setting this value risks naming collisions with other package targets y Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.18/reference/targets/python_requirement.mdx b/versioned_docs/version-2.18/reference/targets/python_requirement.mdx index 9312b5e2d..014355c28 100644 --- a/versioned_docs/version-2.18/reference/targets/python_requirement.mdx +++ b/versioned_docs/version-2.18/reference/targets/python_requirement.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -69,9 +69,9 @@ If the requirement depends on some other requirement to work, such as needing `s Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.18/reference/targets/python_requirements.mdx b/versioned_docs/version-2.18/reference/targets/python_requirements.mdx index 621be0c31..b4078a301 100644 --- a/versioned_docs/version-2.18/reference/targets/python_requirements.mdx +++ b/versioned_docs/version-2.18/reference/targets/python_requirements.mdx @@ -30,7 +30,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.18/reference/targets/python_source.mdx b/versioned_docs/version-2.18/reference/targets/python_source.mdx index d924812fc..6b2904fb1 100644 --- a/versioned_docs/version-2.18/reference/targets/python_source.mdx +++ b/versioned_docs/version-2.18/reference/targets/python_source.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -69,9 +69,9 @@ See https://www.pantsbuild.org/v2.18/docs/python-interpreter-compatibility for h Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.18/reference/targets/python_sources.mdx b/versioned_docs/version-2.18/reference/targets/python_sources.mdx index c9b4db4d1..40f0a86d8 100644 --- a/versioned_docs/version-2.18/reference/targets/python_sources.mdx +++ b/versioned_docs/version-2.18/reference/targets/python_sources.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -300,9 +300,9 @@ The latter mode is similar to creating, activating, and using a virtual environm Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.18/reference/targets/python_test.mdx b/versioned_docs/version-2.18/reference/targets/python_test.mdx index 7779081e8..f8bd1fb73 100644 --- a/versioned_docs/version-2.18/reference/targets/python_test.mdx +++ b/versioned_docs/version-2.18/reference/targets/python_test.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -54,9 +54,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -161,11 +161,11 @@ When tests with the same `batch_compatibility_tag` have incompatibilities in som default_repr={`None`} > -Addresses to targets that can be built with the `scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run. +Addresses to targets that can be built with the `pants package` goal and whose resulting artifacts should be included in the test run. -Pants will build the artifacts as if you had run `scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). +Pants will build the artifacts as if you had run `pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). -You can include anything that can be built by `scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_aws_lambda_function`, or an `archive`. +You can include anything that can be built by `pants package`, e.g. a `pex_binary`, `python_aws_lambda_function`, or an `archive`. diff --git a/versioned_docs/version-2.18/reference/targets/python_test_utils.mdx b/versioned_docs/version-2.18/reference/targets/python_test_utils.mdx index a96e783af..3e123cf34 100644 --- a/versioned_docs/version-2.18/reference/targets/python_test_utils.mdx +++ b/versioned_docs/version-2.18/reference/targets/python_test_utils.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -300,9 +300,9 @@ The latter mode is similar to creating, activating, and using a virtual environm Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.18/reference/targets/python_tests.mdx b/versioned_docs/version-2.18/reference/targets/python_tests.mdx index 972bbfaef..f43e78553 100644 --- a/versioned_docs/version-2.18/reference/targets/python_tests.mdx +++ b/versioned_docs/version-2.18/reference/targets/python_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -282,9 +282,9 @@ If true, don't run Black on this target's code. Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -389,11 +389,11 @@ When tests with the same `batch_compatibility_tag` have incompatibilities in som default_repr={`None`} > -Addresses to targets that can be built with the `scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run. +Addresses to targets that can be built with the `pants package` goal and whose resulting artifacts should be included in the test run. -Pants will build the artifacts as if you had run `scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). +Pants will build the artifacts as if you had run `pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). -You can include anything that can be built by `scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_aws_lambda_function`, or an `archive`. +You can include anything that can be built by `pants package`, e.g. a `pex_binary`, `python_aws_lambda_function`, or an `archive`. diff --git a/versioned_docs/version-2.18/reference/targets/relocated_files.mdx b/versioned_docs/version-2.18/reference/targets/relocated_files.mdx index 62f3ec4e4..346339e69 100644 --- a/versioned_docs/version-2.18/reference/targets/relocated_files.mdx +++ b/versioned_docs/version-2.18/reference/targets/relocated_files.mdx @@ -61,7 +61,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -74,7 +74,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.18/reference/targets/remote_environment.mdx b/versioned_docs/version-2.18/reference/targets/remote_environment.mdx index 3fd9a40fe..5ecb7d127 100644 --- a/versioned_docs/version-2.18/reference/targets/remote_environment.mdx +++ b/versioned_docs/version-2.18/reference/targets/remote_environment.mdx @@ -32,7 +32,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -45,7 +45,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.18/reference/targets/resource.mdx b/versioned_docs/version-2.18/reference/targets/resource.mdx index c63ec5c2c..8573949b0 100644 --- a/versioned_docs/version-2.18/reference/targets/resource.mdx +++ b/versioned_docs/version-2.18/reference/targets/resource.mdx @@ -26,7 +26,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -52,9 +52,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.18/reference/targets/resources.mdx b/versioned_docs/version-2.18/reference/targets/resources.mdx index 531e7126f..4bab2b636 100644 --- a/versioned_docs/version-2.18/reference/targets/resources.mdx +++ b/versioned_docs/version-2.18/reference/targets/resources.mdx @@ -24,7 +24,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -94,9 +94,9 @@ You can specify the same file name in multiple keys, so long as you don't o Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.18/reference/targets/run_shell_command.mdx b/versioned_docs/version-2.18/reference/targets/run_shell_command.mdx index 96824cfac..bf8dfe79c 100644 --- a/versioned_docs/version-2.18/reference/targets/run_shell_command.mdx +++ b/versioned_docs/version-2.18/reference/targets/run_shell_command.mdx @@ -37,7 +37,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -50,7 +50,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.18/reference/targets/scala_artifact.mdx b/versioned_docs/version-2.18/reference/targets/scala_artifact.mdx index bff81afed..2bea85779 100644 --- a/versioned_docs/version-2.18/reference/targets/scala_artifact.mdx +++ b/versioned_docs/version-2.18/reference/targets/scala_artifact.mdx @@ -30,7 +30,7 @@ Backend: `pants.backend.experimental.scala` @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.18/reference/targets/scala_junit_test.mdx b/versioned_docs/version-2.18/reference/targets/scala_junit_test.mdx index 5d58ce5ca..4435e1f2c 100644 --- a/versioned_docs/version-2.18/reference/targets/scala_junit_test.mdx +++ b/versioned_docs/version-2.18/reference/targets/scala_junit_test.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.scala` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.18/reference/targets/scala_junit_tests.mdx b/versioned_docs/version-2.18/reference/targets/scala_junit_tests.mdx index 1a65b3282..e0a6b8fa3 100644 --- a/versioned_docs/version-2.18/reference/targets/scala_junit_tests.mdx +++ b/versioned_docs/version-2.18/reference/targets/scala_junit_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.scala` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -107,9 +107,9 @@ If unset, will default to `[test].timeout_default`; if that option is also unset Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.18/reference/targets/scala_source.mdx b/versioned_docs/version-2.18/reference/targets/scala_source.mdx index 6ea5d9236..9a1c6e5c6 100644 --- a/versioned_docs/version-2.18/reference/targets/scala_source.mdx +++ b/versioned_docs/version-2.18/reference/targets/scala_source.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.scala` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.18/reference/targets/scala_sources.mdx b/versioned_docs/version-2.18/reference/targets/scala_sources.mdx index 56d04e3f5..d61b675d0 100644 --- a/versioned_docs/version-2.18/reference/targets/scala_sources.mdx +++ b/versioned_docs/version-2.18/reference/targets/scala_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.scala` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -106,9 +106,9 @@ If true, don't run `scalafmt` on this target's code. Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.18/reference/targets/scalac_plugin.mdx b/versioned_docs/version-2.18/reference/targets/scalac_plugin.mdx index 2e9c51213..5debfdf3a 100644 --- a/versioned_docs/version-2.18/reference/targets/scalac_plugin.mdx +++ b/versioned_docs/version-2.18/reference/targets/scalac_plugin.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.scala` @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.18/reference/targets/scalatest_test.mdx b/versioned_docs/version-2.18/reference/targets/scalatest_test.mdx index 54e9a6d9e..d16770489 100644 --- a/versioned_docs/version-2.18/reference/targets/scalatest_test.mdx +++ b/versioned_docs/version-2.18/reference/targets/scalatest_test.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.scala` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.18/reference/targets/scalatest_tests.mdx b/versioned_docs/version-2.18/reference/targets/scalatest_tests.mdx index 6b798054b..d9f116bcd 100644 --- a/versioned_docs/version-2.18/reference/targets/scalatest_tests.mdx +++ b/versioned_docs/version-2.18/reference/targets/scalatest_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.scala` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -94,9 +94,9 @@ You can specify the same file name in multiple keys, so long as you don't o Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.18/reference/targets/shell_command.mdx b/versioned_docs/version-2.18/reference/targets/shell_command.mdx index f7dc848c2..507f27c3c 100644 --- a/versioned_docs/version-2.18/reference/targets/shell_command.mdx +++ b/versioned_docs/version-2.18/reference/targets/shell_command.mdx @@ -42,7 +42,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -55,7 +55,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.18/reference/targets/shell_source.mdx b/versioned_docs/version-2.18/reference/targets/shell_source.mdx index 92ae90112..4b901cc57 100644 --- a/versioned_docs/version-2.18/reference/targets/shell_source.mdx +++ b/versioned_docs/version-2.18/reference/targets/shell_source.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.18/reference/targets/shell_sources.mdx b/versioned_docs/version-2.18/reference/targets/shell_sources.mdx index 419f97b62..a8604d467 100644 --- a/versioned_docs/version-2.18/reference/targets/shell_sources.mdx +++ b/versioned_docs/version-2.18/reference/targets/shell_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -118,9 +118,9 @@ If true, don't run shfmt on this target's code. Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.18/reference/targets/shunit2_test.mdx b/versioned_docs/version-2.18/reference/targets/shunit2_test.mdx index b9cfd5533..423986ddf 100644 --- a/versioned_docs/version-2.18/reference/targets/shunit2_test.mdx +++ b/versioned_docs/version-2.18/reference/targets/shunit2_test.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -67,9 +67,9 @@ Path is relative to the BUILD file's directory, e.g. `source='example.ext'` Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -119,11 +119,11 @@ Which shell to run the tests with. If unspecified, Pants will look for a shebang default_repr={`None`} > -Addresses to targets that can be built with the `scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run. +Addresses to targets that can be built with the `pants package` goal and whose resulting artifacts should be included in the test run. -Pants will build the artifacts as if you had run `scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). +Pants will build the artifacts as if you had run `pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). -You can include anything that can be built by `scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_aws_lambda_function`, or an `archive`. +You can include anything that can be built by `pants package`, e.g. a `pex_binary`, `python_aws_lambda_function`, or an `archive`. diff --git a/versioned_docs/version-2.18/reference/targets/shunit2_tests.mdx b/versioned_docs/version-2.18/reference/targets/shunit2_tests.mdx index 72e092e2e..0d2b385ff 100644 --- a/versioned_docs/version-2.18/reference/targets/shunit2_tests.mdx +++ b/versioned_docs/version-2.18/reference/targets/shunit2_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -118,9 +118,9 @@ If true, don't run shfmt on this target's code. Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -170,11 +170,11 @@ Which shell to run the tests with. If unspecified, Pants will look for a shebang default_repr={`None`} > -Addresses to targets that can be built with the `scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run. +Addresses to targets that can be built with the `pants package` goal and whose resulting artifacts should be included in the test run. -Pants will build the artifacts as if you had run `scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). +Pants will build the artifacts as if you had run `pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). -You can include anything that can be built by `scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_aws_lambda_function`, or an `archive`. +You can include anything that can be built by `pants package`, e.g. a `pex_binary`, `python_aws_lambda_function`, or an `archive`. diff --git a/versioned_docs/version-2.18/reference/targets/system_binary.mdx b/versioned_docs/version-2.18/reference/targets/system_binary.mdx index 9920f16b2..d7bd775a0 100644 --- a/versioned_docs/version-2.18/reference/targets/system_binary.mdx +++ b/versioned_docs/version-2.18/reference/targets/system_binary.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.adhoc` @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.18/reference/targets/target.mdx b/versioned_docs/version-2.18/reference/targets/target.mdx index 54170a25b..0daebe015 100644 --- a/versioned_docs/version-2.18/reference/targets/target.mdx +++ b/versioned_docs/version-2.18/reference/targets/target.mdx @@ -26,7 +26,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -52,9 +52,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.18/reference/targets/terraform_deployment.mdx b/versioned_docs/version-2.18/reference/targets/terraform_deployment.mdx index 5cb4fb7b8..8a0324a13 100644 --- a/versioned_docs/version-2.18/reference/targets/terraform_deployment.mdx +++ b/versioned_docs/version-2.18/reference/targets/terraform_deployment.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.terraform` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.18/reference/targets/terraform_module.mdx b/versioned_docs/version-2.18/reference/targets/terraform_module.mdx index 14c55489f..5d4192fb2 100644 --- a/versioned_docs/version-2.18/reference/targets/terraform_module.mdx +++ b/versioned_docs/version-2.18/reference/targets/terraform_module.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.terraform` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -54,9 +54,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.18/reference/targets/thrift_source.mdx b/versioned_docs/version-2.18/reference/targets/thrift_source.mdx index 7264a94cf..98e2b349b 100644 --- a/versioned_docs/version-2.18/reference/targets/thrift_source.mdx +++ b/versioned_docs/version-2.18/reference/targets/thrift_source.mdx @@ -27,7 +27,7 @@ Backend: `pants.backend.codegen.thrift.apache.p Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -40,7 +40,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -53,9 +53,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.18/reference/targets/thrift_sources.mdx b/versioned_docs/version-2.18/reference/targets/thrift_sources.mdx index d20113976..598b6f430 100644 --- a/versioned_docs/version-2.18/reference/targets/thrift_sources.mdx +++ b/versioned_docs/version-2.18/reference/targets/thrift_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.codegen.thrift.apache.p Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -109,9 +109,9 @@ All dependencies must share the same value for their `resolve` field. Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.18/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.18/reference/targets/vcs_version.mdx b/versioned_docs/version-2.18/reference/targets/vcs_version.mdx index d244b6916..421691958 100644 --- a/versioned_docs/version-2.18/reference/targets/vcs_version.mdx +++ b/versioned_docs/version-2.18/reference/targets/vcs_version.mdx @@ -30,7 +30,7 @@ Backend: `pants.backend.experimental.python` @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.19/reference/global-options.mdx b/versioned_docs/version-2.19/reference/global-options.mdx index 60ec27504..b30755b39 100644 --- a/versioned_docs/version-2.19/reference/global-options.mdx +++ b/versioned_docs/version-2.19/reference/global-options.mdx @@ -317,9 +317,9 @@ ignore_warnings = [ Use this Pants version. Note that Pants only uses this to verify that you are using the requested version, as Pants cannot dynamically change the version it is using once the program is already running. -If you use the `scie-pants-linux-x86_64` script from https://www.pantsbuild.org/v2.19/docs/installation, however, changing the value in your `pants.toml` will cause the new version to be installed and run automatically. +If you use the `pants` script from https://www.pantsbuild.org/v2.19/docs/installation, however, changing the value in your `pants.toml` will cause the new version to be installed and run automatically. -Run `scie-pants-linux-x86_64 --version` to check what is being used. +Run `pants --version` to check what is being used. @@ -832,7 +832,7 @@ Whether or not to use nailgun to run JVM requests that are marked as supporting default_repr={`3`} > -The time in seconds to wait when gracefully shutting down an interactive process (such as one opened using `scie-pants-linux-x86_64 run`) before killing it. +The time in seconds to wait when gracefully shutting down an interactive process (such as one opened using `pants run`) before killing it. diff --git a/versioned_docs/version-2.19/reference/goals/experimental-bsp.mdx b/versioned_docs/version-2.19/reference/goals/experimental-bsp.mdx index 5362d9e2f..501fe81ee 100644 --- a/versioned_docs/version-2.19/reference/goals/experimental-bsp.mdx +++ b/versioned_docs/version-2.19/reference/goals/experimental-bsp.mdx @@ -79,7 +79,7 @@ Run the Build Server Protocol server. Pants will receive BSP RPC requests via th Environment variables to set in the BSP runner script when setting up BSP in a repository. Entries are either strings in the form `ENV_VAR=value` to set an explicit value; or just `ENV_VAR` to copy the value from Pants' own environment when the experimental-bsp goal was run. -This option only takes effect when the BSP runner script is written. If the option changes, you must run `scie-pants-linux-x86_64 experimental-bsp` again to write a new copy of the BSP runner script. +This option only takes effect when the BSP runner script is written. If the option changes, you must run `pants experimental-bsp` again to write a new copy of the BSP runner script. Note: The environment variables passed to the Pants BSP server will be those set for your IDE and not your shell. For example, on macOS, the IDE is generally launched by `launchd` after clicking on a Dock icon, and not from the shell. Thus, any environment variables set for your shell will likely not be seen by the Pants BSP server. At the very least, on macOS consider writing an explicit PATH into the BSP runner script via this option. diff --git a/versioned_docs/version-2.19/reference/goals/fix.mdx b/versioned_docs/version-2.19/reference/goals/fix.mdx index 1f996ab0d..7c7407fae 100644 --- a/versioned_docs/version-2.19/reference/goals/fix.mdx +++ b/versioned_docs/version-2.19/reference/goals/fix.mdx @@ -47,7 +47,7 @@ You can repeat this option, e.g. `fix --only=autoflake --only=pyupgrade` or `fix If true, skip running all formatters. -FYI: when running `scie-pants-linux-x86_64 fix fmt ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `fix` where possible. +FYI: when running `pants fix fmt ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `fix` where possible. diff --git a/versioned_docs/version-2.19/reference/goals/generate-lockfiles.mdx b/versioned_docs/version-2.19/reference/goals/generate-lockfiles.mdx index 08231e6ad..2782ac00a 100644 --- a/versioned_docs/version-2.19/reference/goals/generate-lockfiles.mdx +++ b/versioned_docs/version-2.19/reference/goals/generate-lockfiles.mdx @@ -33,7 +33,7 @@ Only generate lockfiles for the specified resolve(s). Resolves are the logical names for the different lockfiles used in your project. For your own code's dependencies, these come from backend-specific configuration such as `[python].resolves`. For tool lockfiles, resolve names are the options scope for that tool such as `black`, `pytest`, and `mypy-protobuf`. -For example, you can run `scie-pants-linux-x86_64 generate-lockfiles --resolve=black --resolve=pytest --resolve=data-science` to only generate lockfiles for those two tools and your resolve named `data-science`. +For example, you can run `pants generate-lockfiles --resolve=black --resolve=pytest --resolve=data-science` to only generate lockfiles for those two tools and your resolve named `data-science`. If you specify an invalid resolve name, like 'fake', Pants will output all possible values. @@ -75,7 +75,7 @@ Include unchanged distributions in the diff summary output. Implies `diff=true`. default_repr={`None`} > -If set, lockfile headers will say to run this command to regenerate the lockfile, rather than running `scie-pants-linux-x86_64 generate-lockfiles --resolve=` like normal. +If set, lockfile headers will say to run this command to regenerate the lockfile, rather than running `pants generate-lockfiles --resolve=` like normal. diff --git a/versioned_docs/version-2.19/reference/goals/lint.mdx b/versioned_docs/version-2.19/reference/goals/lint.mdx index 9607a4b8b..3ab192176 100644 --- a/versioned_docs/version-2.19/reference/goals/lint.mdx +++ b/versioned_docs/version-2.19/reference/goals/lint.mdx @@ -47,7 +47,7 @@ You can repeat this option, e.g. `lint --only=flake8 --only=shellcheck` or `lint If true, skip running all formatters in check-only mode. -FYI: when running `scie-pants-linux-x86_64 fmt lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `lint` where possible. +FYI: when running `pants fmt lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `lint` where possible. @@ -61,7 +61,7 @@ FYI: when running `scie-pants-linux-x86_64 fmt lint ::`, there should be diminis If true, skip running all fixers in check-only mode. -FYI: when running `scie-pants-linux-x86_64 fix lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fix` when running `lint` where possible. +FYI: when running `pants fix lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fix` when running `lint` where possible. diff --git a/versioned_docs/version-2.19/reference/help-all.json b/versioned_docs/version-2.19/reference/help-all.json index 3df23067c..a9649c3fe 100644 --- a/versioned_docs/version-2.19/reference/help-all.json +++ b/versioned_docs/version-2.19/reference/help-all.json @@ -205,7 +205,7 @@ "display_args": ["--[no-]add-trailing-comma-skip"], "env_var": "PANTS_ADD_TRAILING_COMMA_SKIP", "fromfile": false, - "help": "If true, don't use add-trailing-comma when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use add-trailing-comma when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -563,7 +563,7 @@ "display_args": ["--[no-]autoflake-skip"], "env_var": "PANTS_AUTOFLAKE_SKIP", "fromfile": false, - "help": "If true, don't use Autoflake when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Autoflake when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--autoflake-skip", "--no-autoflake-skip"], @@ -877,7 +877,7 @@ "display_args": ["--[no-]bandit-skip"], "env_var": "PANTS_BANDIT_SKIP", "fromfile": false, - "help": "If true, don't use Bandit when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Bandit when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--bandit-skip", "--no-bandit-skip"], @@ -932,7 +932,7 @@ { "details": "from env var PANTS_BIN_NAME", "rank": "ENVIRONMENT", - "value": "/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64" + "value": "/home/josh/work/scie-pants/dist/pants" } ] } @@ -1202,7 +1202,7 @@ "display_args": ["--[no-]black-skip"], "env_var": "PANTS_BLACK_SKIP", "fromfile": false, - "help": "If true, don't use Black when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Black when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--black-skip", "--no-black-skip"], @@ -1332,7 +1332,7 @@ "display_args": ["--[no-]buf-format-skip"], "env_var": "PANTS_BUF_FORMAT_SKIP", "fromfile": false, - "help": "If true, don't use Buf when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Buf when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--buf-format-skip", "--no-buf-format-skip"], @@ -1441,7 +1441,7 @@ "display_args": ["--[no-]buf-lint-skip"], "env_var": "PANTS_BUF_LINT_SKIP", "fromfile": false, - "help": "If true, don't use Buf when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Buf when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--buf-lint-skip", "--no-buf-lint-skip"], @@ -1698,7 +1698,7 @@ "display_args": ["--[no-]buildifier-skip"], "env_var": "PANTS_BUILDIFIER_SKIP", "fromfile": false, - "help": "If true, don't use Buildifier when running `scie-pants-linux-x86_64 fmt`.", + "help": "If true, don't use Buildifier when running `pants fmt`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--buildifier-skip", "--no-buildifier-skip"], @@ -1877,7 +1877,7 @@ "display_args": ["--[no-]build-deprecations-fixer-skip"], "env_var": "PANTS_BUILD_DEPRECATIONS_FIXER_SKIP", "fromfile": false, - "help": "If true, don't use BUILD Deprecations Fixer when running `scie-pants-linux-x86_64 fix`.", + "help": "If true, don't use BUILD Deprecations Fixer when running `pants fix`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -2230,7 +2230,7 @@ "display_args": ["--cli-alias=\"{'key1': val1, 'key2': val2, ...}\""], "env_var": "PANTS_CLI_ALIAS", "fromfile": false, - "help": "Register command line aliases.\n\nExample:\n\n [cli.alias]\n green = \"fmt lint check\"\n all-changed = \"--changed-since=HEAD --changed-dependents=transitive\"\n\nThis would allow you to run `scie-pants-linux-x86_64 green all-changed`, which is shorthand for `scie-pants-linux-x86_64 fmt lint check --changed-since=HEAD --changed-dependents=transitive`.\n\nNotice: this option must be placed in a config file (e.g. `pants.toml` or `pantsrc`) to have any effect.", + "help": "Register command line aliases.\n\nExample:\n\n [cli.alias]\n green = \"fmt lint check\"\n all-changed = \"--changed-since=HEAD --changed-dependents=transitive\"\n\nThis would allow you to run `pants green all-changed`, which is shorthand for `pants fmt lint check --changed-since=HEAD --changed-dependents=transitive`.\n\nNotice: this option must be placed in a config file (e.g. `pants.toml` or `pantsrc`) to have any effect.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--cli-alias"], @@ -3870,7 +3870,7 @@ "display_args": ["--[no-]docformatter-skip"], "env_var": "PANTS_DOCFORMATTER_SKIP", "fromfile": false, - "help": "If true, don't use docformatter when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use docformatter when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--docformatter-skip", "--no-docformatter-skip"], @@ -4373,7 +4373,7 @@ "display_args": ["--docker-run-args=\"[, , ...]\""], "env_var": "PANTS_DOCKER_RUN_ARGS", "fromfile": false, - "help": "Additional arguments to use for `docker run` invocations.\n\nExample:\n\n $ scie-pants-linux-x86_64 run --docker-run-args=\"-p 127.0.0.1:80:8080/tcp --name demo\" src/example:image -- [image entrypoint args]\n\nTo provide the top-level options to the `docker` client, use `[docker].env_vars` to configure the [Environment variables](https://docs.docker.com/engine/reference/commandline/cli/#environment-variables) as appropriate.\n\nThe arguments for the image entrypoint may be passed on the command line after a double dash (`--`), or using the `--run-args` option.\n\nDefaults to `--interactive --tty` when stdout is connected to a terminal.", + "help": "Additional arguments to use for `docker run` invocations.\n\nExample:\n\n $ pants run --docker-run-args=\"-p 127.0.0.1:80:8080/tcp --name demo\" src/example:image -- [image entrypoint args]\n\nTo provide the top-level options to the `docker` client, use `[docker].env_vars` to configure the [Environment variables](https://docs.docker.com/engine/reference/commandline/cli/#environment-variables) as appropriate.\n\nThe arguments for the image entrypoint may be passed on the command line after a double dash (`--`), or using the `--run-args` option.\n\nDefaults to `--interactive --tty` when stdout is connected to a terminal.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--docker-run-args"], @@ -5305,7 +5305,7 @@ ], "env_var": "PANTS_EXPERIMENTAL_BSP_RUNNER_ENV_VARS", "fromfile": false, - "help": "Environment variables to set in the BSP runner script when setting up BSP in a repository. Entries are either strings in the form `ENV_VAR=value` to set an explicit value; or just `ENV_VAR` to copy the value from Pants' own environment when the experimental-bsp goal was run.\n\nThis option only takes effect when the BSP runner script is written. If the option changes, you must run `scie-pants-linux-x86_64 experimental-bsp` again to write a new copy of the BSP runner script.\n\nNote: The environment variables passed to the Pants BSP server will be those set for your IDE and not your shell. For example, on macOS, the IDE is generally launched by `launchd` after clicking on a Dock icon, and not from the shell. Thus, any environment variables set for your shell will likely not be seen by the Pants BSP server. At the very least, on macOS consider writing an explicit PATH into the BSP runner script via this option.", + "help": "Environment variables to set in the BSP runner script when setting up BSP in a repository. Entries are either strings in the form `ENV_VAR=value` to set an explicit value; or just `ENV_VAR` to copy the value from Pants' own environment when the experimental-bsp goal was run.\n\nThis option only takes effect when the BSP runner script is written. If the option changes, you must run `pants experimental-bsp` again to write a new copy of the BSP runner script.\n\nNote: The environment variables passed to the Pants BSP server will be those set for your IDE and not your shell. For example, on macOS, the IDE is generally launched by `launchd` after clicking on a Dock icon, and not from the shell. Thus, any environment variables set for your shell will likely not be seen by the Pants BSP server. At the very least, on macOS consider writing an explicit PATH into the BSP runner script via this option.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--experimental-bsp-runner-env-vars"], @@ -6010,7 +6010,7 @@ "display_args": ["--[no-]fix-skip-formatters"], "env_var": "PANTS_FIX_SKIP_FORMATTERS", "fromfile": false, - "help": "If true, skip running all formatters.\n\nFYI: when running `scie-pants-linux-x86_64 fix fmt ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `fix` where possible.", + "help": "If true, skip running all formatters.\n\nFYI: when running `pants fix fmt ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `fix` where possible.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -6300,7 +6300,7 @@ "display_args": ["--[no-]flake8-skip"], "env_var": "PANTS_FLAKE8_SKIP", "fromfile": false, - "help": "If true, don't use Flake8 when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Flake8 when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--flake8-skip", "--no-flake8-skip"], @@ -6434,7 +6434,7 @@ "display_args": ["--generate-lockfiles-custom-command="], "env_var": "PANTS_GENERATE_LOCKFILES_CUSTOM_COMMAND", "fromfile": false, - "help": "If set, lockfile headers will say to run this command to regenerate the lockfile, rather than running `scie-pants-linux-x86_64 generate-lockfiles --resolve=` like normal.", + "help": "If set, lockfile headers will say to run this command to regenerate the lockfile, rather than running `pants generate-lockfiles --resolve=` like normal.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--generate-lockfiles-custom-command"], @@ -6539,7 +6539,7 @@ ], "env_var": "PANTS_GENERATE_LOCKFILES_RESOLVE", "fromfile": false, - "help": "Only generate lockfiles for the specified resolve(s).\n\nResolves are the logical names for the different lockfiles used in your project. For your own code's dependencies, these come from backend-specific configuration such as `[python].resolves`. For tool lockfiles, resolve names are the options scope for that tool such as `black`, `pytest`, and `mypy-protobuf`.\n\nFor example, you can run `scie-pants-linux-x86_64 generate-lockfiles --resolve=black --resolve=pytest --resolve=data-science` to only generate lockfiles for those two tools and your resolve named `data-science`.\n\nIf you specify an invalid resolve name, like 'fake', Pants will output all possible values.\n\nIf not specified, Pants will generate lockfiles for all resolves.", + "help": "Only generate lockfiles for the specified resolve(s).\n\nResolves are the logical names for the different lockfiles used in your project. For your own code's dependencies, these come from backend-specific configuration such as `[python].resolves`. For tool lockfiles, resolve names are the options scope for that tool such as `black`, `pytest`, and `mypy-protobuf`.\n\nFor example, you can run `pants generate-lockfiles --resolve=black --resolve=pytest --resolve=data-science` to only generate lockfiles for those two tools and your resolve named `data-science`.\n\nIf you specify an invalid resolve name, like 'fake', Pants will output all possible values.\n\nIf not specified, Pants will generate lockfiles for all resolves.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--generate-lockfiles-resolve"], @@ -6605,7 +6605,7 @@ "display_args": ["--[no-]gofmt-skip"], "env_var": "PANTS_GOFMT_SKIP", "fromfile": false, - "help": "If true, don't use gofmt when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use gofmt when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--gofmt-skip", "--no-gofmt-skip"], @@ -7367,7 +7367,7 @@ "display_args": ["--google-java-format-lockfile="], "env_var": "PANTS_GOOGLE_JAVA_FORMAT_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.19.0rc1/src/python/pants/backend/java/lint/google_java_format/google_java_format.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=google-java-format`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.19.0rc1/src/python/pants/backend/java/lint/google_java_format/google_java_format.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=google-java-format`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--google-java-format-lockfile"], @@ -7400,7 +7400,7 @@ "display_args": ["--[no-]google-java-format-skip"], "env_var": "PANTS_GOOGLE_JAVA_FORMAT_SKIP", "fromfile": false, - "help": "If true, don't use Google Java Format when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Google Java Format when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -7966,7 +7966,7 @@ "display_args": ["--[no-]go-test-skip"], "env_var": "PANTS_GO_TEST_SKIP", "fromfile": false, - "help": "If true, don't use Go test binary when running `scie-pants-linux-x86_64 test`.", + "help": "If true, don't use Go test binary when running `pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--go-test-skip", "--no-go-test-skip"], @@ -8363,7 +8363,7 @@ "display_args": ["--[no-]hadolint-skip"], "env_var": "PANTS_HADOLINT_SKIP", "fromfile": false, - "help": "If true, don't use Hadolint when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Hadolint when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--hadolint-skip", "--no-hadolint-skip"], @@ -9190,7 +9190,7 @@ "display_args": ["--[no-]helm-unittest-skip"], "env_var": "PANTS_HELM_UNITTEST_SKIP", "fromfile": false, - "help": "If true, don't use helmunittestsubsystem when running `scie-pants-linux-x86_64 test`.", + "help": "If true, don't use helmunittestsubsystem when running `pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -10042,7 +10042,7 @@ "display_args": ["--[no-]isort-skip"], "env_var": "PANTS_ISORT_SKIP", "fromfile": false, - "help": "If true, don't use isort when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use isort when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--isort-skip", "--no-isort-skip"], @@ -10141,7 +10141,7 @@ "display_args": ["--jarjar-lockfile="], "env_var": "PANTS_JARJAR_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.19.0rc1/src/python/pants/jvm/shading/jarjar.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=jarjar`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.19.0rc1/src/python/pants/jvm/shading/jarjar.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=jarjar`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--jarjar-lockfile"], @@ -10562,7 +10562,7 @@ "display_args": ["--junit-lockfile="], "env_var": "PANTS_JUNIT_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.19.0rc1/src/python/pants/jvm/test/junit.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=junit`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.19.0rc1/src/python/pants/jvm/test/junit.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=junit`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--junit-lockfile"], @@ -10595,7 +10595,7 @@ "display_args": ["--[no-]junit-skip"], "env_var": "PANTS_JUNIT_SKIP", "fromfile": false, - "help": "If true, don't use JUnit when running `scie-pants-linux-x86_64 test`.", + "help": "If true, don't use JUnit when running `pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--junit-skip", "--no-junit-skip"], @@ -11248,7 +11248,7 @@ "display_args": ["--ktlint-lockfile="], "env_var": "PANTS_KTLINT_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.19.0rc1/src/python/pants/backend/kotlin/lint/ktlint/ktlint.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=ktlint`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.19.0rc1/src/python/pants/backend/kotlin/lint/ktlint/ktlint.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=ktlint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--ktlint-lockfile"], @@ -11281,7 +11281,7 @@ "display_args": ["--[no-]ktlint-skip"], "env_var": "PANTS_KTLINT_SKIP", "fromfile": false, - "help": "If true, don't use Ktlint when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Ktlint when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--ktlint-skip", "--no-ktlint-skip"], @@ -11446,7 +11446,7 @@ "display_args": ["--[no-]lint-skip-fixers"], "env_var": "PANTS_LINT_SKIP_FIXERS", "fromfile": false, - "help": "If true, skip running all fixers in check-only mode.\n\nFYI: when running `scie-pants-linux-x86_64 fix lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fix` when running `lint` where possible.", + "help": "If true, skip running all fixers in check-only mode.\n\nFYI: when running `pants fix lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fix` when running `lint` where possible.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--lint-skip-fixers", "--no-lint-skip-fixers"], @@ -11479,7 +11479,7 @@ "display_args": ["--[no-]lint-skip-formatters"], "env_var": "PANTS_LINT_SKIP_FORMATTERS", "fromfile": false, - "help": "If true, skip running all formatters in check-only mode.\n\nFYI: when running `scie-pants-linux-x86_64 fmt lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `lint` where possible.", + "help": "If true, skip running all formatters in check-only mode.\n\nFYI: when running `pants fmt lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `lint` where possible.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -12360,7 +12360,7 @@ "display_args": ["--[no-]mypy-skip"], "env_var": "PANTS_MYPY_SKIP", "fromfile": false, - "help": "If true, don't use MyPy when running `scie-pants-linux-x86_64 check`.", + "help": "If true, don't use MyPy when running `pants check`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--mypy-skip", "--no-mypy-skip"], @@ -12723,7 +12723,7 @@ ], "env_var": "PANTS_NODEJS_RESOLVES", "fromfile": false, - "help": "A mapping of names to lockfile paths used in your project.\n\nSpecifying a resolve name is optional. If unspecified, the default resolve name is calculated by taking the path from the source root to the directory containing the lockfile and replacing '/' with '.' in that path.\n\nExample: An npm lockfile located at `src/js/package/package-lock.json' will result in a resolve named `js.package`, assuming src/ is a source root.\n\nRun `scie-pants-linux-x86_64 generate-lockfiles` to generate the lockfile(s).", + "help": "A mapping of names to lockfile paths used in your project.\n\nSpecifying a resolve name is optional. If unspecified, the default resolve name is calculated by taking the path from the source root to the directory containing the lockfile and replacing '/' with '.' in that path.\n\nExample: An npm lockfile located at `src/js/package/package-lock.json' will result in a resolve named `js.package`, assuming src/ is a source root.\n\nRun `pants generate-lockfiles` to generate the lockfile(s).", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--nodejs-resolves"], @@ -12965,7 +12965,7 @@ "display_args": ["--[no-]openapi-format-skip"], "env_var": "PANTS_OPENAPI_FORMAT_SKIP", "fromfile": false, - "help": "If true, don't use openapi-format when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use openapi-format when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -13946,7 +13946,7 @@ "display_args": ["--[no-]preamble-skip"], "env_var": "PANTS_PREAMBLE_SKIP", "fromfile": false, - "help": "If true, don't use preamble when running `scie-pants-linux-x86_64 fmt`.", + "help": "If true, don't use preamble when running `pants fmt`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--preamble-skip", "--no-preamble-skip"], @@ -14108,7 +14108,7 @@ "display_args": ["--process-execution-graceful-shutdown-timeout="], "env_var": "PANTS_PROCESS_EXECUTION_GRACEFUL_SHUTDOWN_TIMEOUT", "fromfile": false, - "help": "The time in seconds to wait when gracefully shutting down an interactive process (such as one opened using `scie-pants-linux-x86_64 run`) before killing it.", + "help": "The time in seconds to wait when gracefully shutting down an interactive process (such as one opened using `pants run`) before killing it.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--process-execution-graceful-shutdown-timeout"], @@ -14389,7 +14389,7 @@ "display_args": ["--protobuf-java-grpc-lockfile="], "env_var": "PANTS_PROTOBUF_JAVA_GRPC_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.19.0rc1/src/python/pants/backend/codegen/protobuf/java/grpc-java.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=protobuf-java-grpc`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.19.0rc1/src/python/pants/backend/codegen/protobuf/java/grpc-java.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=protobuf-java-grpc`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--protobuf-java-grpc-lockfile"], @@ -15006,7 +15006,7 @@ "display_args": ["--[no-]pydocstyle-skip"], "env_var": "PANTS_PYDOCSTYLE_SKIP", "fromfile": false, - "help": "If true, don't use Pydocstyle when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Pydocstyle when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pydocstyle-skip", "--no-pydocstyle-skip"], @@ -15258,7 +15258,7 @@ "display_args": ["--[no-]pylint-skip"], "env_var": "PANTS_PYLINT_SKIP", "fromfile": false, - "help": "If true, don't use Pylint when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Pylint when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pylint-skip", "--no-pylint-skip"], @@ -15799,7 +15799,7 @@ "display_args": ["--[no-]pytest-skip"], "env_var": "PANTS_PYTEST_SKIP", "fromfile": false, - "help": "If true, don't use Pytest when running `scie-pants-linux-x86_64 test`.", + "help": "If true, don't use Pytest when running `pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pytest-skip", "--no-pytest-skip"], @@ -16479,7 +16479,7 @@ "display_args": ["--python-infer-init-files="], "env_var": "PANTS_PYTHON_INFER_INIT_FILES", "fromfile": false, - "help": "Infer a target's dependencies on any `__init__.py` files in the packages it is located in (recursively upward in the directory structure).\n\nEven if this is set to `never` or `content_only`, Pants will still always include any ancestor `__init__.py` files in the sandbox. Only, they will not be \"proper\" dependencies, e.g. they will not show up in `scie-pants-linux-x86_64 dependencies` and their own dependencies will not be used.\n\nBy default, Pants only adds a \"proper\" dependency if there is content in the `__init__.py` file. This makes sure that dependencies are added when likely necessary to build, while also avoiding adding unnecessary dependencies. While accurate, those unnecessary dependencies can complicate setting metadata like the `interpreter_constraints` and `resolve` fields.", + "help": "Infer a target's dependencies on any `__init__.py` files in the packages it is located in (recursively upward in the directory structure).\n\nEven if this is set to `never` or `content_only`, Pants will still always include any ancestor `__init__.py` files in the sandbox. Only, they will not be \"proper\" dependencies, e.g. they will not show up in `pants dependencies` and their own dependencies will not be used.\n\nBy default, Pants only adds a \"proper\" dependency if there is content in the `__init__.py` file. This makes sure that dependencies are added when likely necessary to build, while also avoiding adding unnecessary dependencies. While accurate, those unnecessary dependencies can complicate setting metadata like the `interpreter_constraints` and `resolve` fields.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--python-infer-init-files"], @@ -16616,7 +16616,7 @@ "display_args": ["--[no-]python-infer-use-rust-parser"], "env_var": "PANTS_PYTHON_INFER_USE_RUST_PARSER", "fromfile": false, - "help": "Use the new Rust-based, multithreaded, in-process dependency parser.\n\nPants 2.17 introduced a new paradigm to dependency parsing for Python by leveraging a Rust-based parser that's called in the same process as Pants itself, instead of farming out to one-python-process-per-file.\n\nAs a result of the switch, cold-cache performance improved by a factor of about 12x, while hot-cache had no difference. Additionally, Pants can now infer dependencies from Python scripts with syntax errors.\n\nAfter leaving this defaulted to disabled for a release cycle, Pants 2.18 started defaulting to enabling this.\n\nIf you think the new behaviour is causing problems, it is recommended that you run `scie-pants-linux-x86_64 peek :: > before.json` and then `scie-pants-linux-x86_64 --python-infer-use-rust-parser=False peek :: > after.json` and compare the two results.\n\nIf you think there is a bug and need to disable it, please file an issue: https://github.com/pantsbuild/pants/issues/new/choose.", + "help": "Use the new Rust-based, multithreaded, in-process dependency parser.\n\nPants 2.17 introduced a new paradigm to dependency parsing for Python by leveraging a Rust-based parser that's called in the same process as Pants itself, instead of farming out to one-python-process-per-file.\n\nAs a result of the switch, cold-cache performance improved by a factor of about 12x, while hot-cache had no difference. Additionally, Pants can now infer dependencies from Python scripts with syntax errors.\n\nAfter leaving this defaulted to disabled for a release cycle, Pants 2.18 started defaulting to enabling this.\n\nIf you think the new behaviour is causing problems, it is recommended that you run `pants peek :: > before.json` and then `pants --python-infer-use-rust-parser=False peek :: > after.json` and compare the two results.\n\nIf you think there is a bug and need to disable it, please file an issue: https://github.com/pantsbuild/pants/issues/new/choose.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -17165,7 +17165,7 @@ "env_var": "PANTS_PYTHON_REQUIREMENT_CONSTRAINTS", "fromfile": false, "help": "When resolving third-party requirements for your own code (vs. tools you run), use this constraints file to determine which versions to use.\n\nMutually exclusive with `[python].enable_resolves`, which we generally recommend as an improvement over constraints file.\n\nSee https://pip.pypa.io/en/stable/user_guide/#constraints-files for more information on the format of constraint files and how constraints are applied in Pex and pip.\n\nThis only applies when resolving user requirements, rather than tools you run like Black and Pytest. To constrain tools, set `[tool].lockfile`, e.g. `[black].lockfile`.", - "removal_hint": "We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.\n\nTo migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `scie-pants-linux-x86_64 generate-lockfiles`.", + "removal_hint": "We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.\n\nTo migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `pants generate-lockfiles`.", "removal_version": "3.0.0.dev0", "scoped_cmd_line_args": ["--python-requirement-constraints"], "target_field_name": null, @@ -17229,7 +17229,7 @@ ], "env_var": "PANTS_PYTHON_RESOLVES", "fromfile": false, - "help": "A mapping of logical names to lockfile paths used in your project.\n\nMany organizations only need a single resolve for their whole project, which is a good default and often the simplest thing to do. However, you may need multiple resolves, such as if you use two conflicting versions of a requirement in your repository.\n\nIf you only need a single resolve, run `scie-pants-linux-x86_64 generate-lockfiles` to generate the lockfile.\n\nIf you need multiple resolves:\n\n 1. Via this option, define multiple resolve names and their lockfile paths. The names should be meaningful to your repository, such as `data-science` or `pants-plugins`.\n 2. Set the default with `[python].default_resolve`.\n 3. Update your `python_requirement` targets with the `resolve` field to declare which resolve they should be available in. They default to `[python].default_resolve`, so you only need to update targets that you want in non-default resolves. (Often you'll set this via the `python_requirements` or `poetry_requirements` target generators)\n 4. Run `scie-pants-linux-x86_64 generate-lockfiles` to generate the lockfiles. If the results aren't what you'd expect, adjust the prior step.\n 5. Update any targets like `python_source` / `python_sources`, `python_test` / `python_tests`, and `pex_binary` which need to set a non-default resolve with the `resolve` field.\n\nIf a target can work with multiple resolves, you can either use the `parametrize` mechanism or manually create a distinct target per resolve. See https://www.pantsbuild.org/v2.19/docs/targets for information about `parametrize`.\n\nFor example:\n\n python_sources(\n resolve=parametrize(\"data-science\", \"web-app\"),\n )\n\nYou can name the lockfile paths what you would like; Pants does not expect a certain file extension or location.\n\nOnly applies if `[python].enable_resolves` is true.", + "help": "A mapping of logical names to lockfile paths used in your project.\n\nMany organizations only need a single resolve for their whole project, which is a good default and often the simplest thing to do. However, you may need multiple resolves, such as if you use two conflicting versions of a requirement in your repository.\n\nIf you only need a single resolve, run `pants generate-lockfiles` to generate the lockfile.\n\nIf you need multiple resolves:\n\n 1. Via this option, define multiple resolve names and their lockfile paths. The names should be meaningful to your repository, such as `data-science` or `pants-plugins`.\n 2. Set the default with `[python].default_resolve`.\n 3. Update your `python_requirement` targets with the `resolve` field to declare which resolve they should be available in. They default to `[python].default_resolve`, so you only need to update targets that you want in non-default resolves. (Often you'll set this via the `python_requirements` or `poetry_requirements` target generators)\n 4. Run `pants generate-lockfiles` to generate the lockfiles. If the results aren't what you'd expect, adjust the prior step.\n 5. Update any targets like `python_source` / `python_sources`, `python_test` / `python_tests`, and `pex_binary` which need to set a non-default resolve with the `resolve` field.\n\nIf a target can work with multiple resolves, you can either use the `parametrize` mechanism or manually create a distinct target per resolve. See https://www.pantsbuild.org/v2.19/docs/targets for information about `parametrize`.\n\nFor example:\n\n python_sources(\n resolve=parametrize(\"data-science\", \"web-app\"),\n )\n\nYou can name the lockfile paths what you would like; Pants does not expect a certain file extension or location.\n\nOnly applies if `[python].enable_resolves` is true.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--python-resolves"], @@ -17444,7 +17444,7 @@ "env_var": "PANTS_PYTHON_RESOLVE_ALL_CONSTRAINTS", "fromfile": false, "help": "(Only relevant when using `[python].requirement_constraints.`) If enabled, when resolving requirements, Pants will first resolve your entire constraints file as a single global resolve. Then, if the code uses a subset of your constraints file, Pants will extract the relevant requirements from that global resolve so that only what's actually needed gets used. If disabled, Pants will not use a global resolve and will resolve each subset of your requirements independently.\n\nUsually this option should be enabled because it can result in far fewer resolves.", - "removal_hint": "We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.\n\nTo migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `scie-pants-linux-x86_64 generate-lockfiles`.", + "removal_hint": "We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.\n\nTo migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `pants generate-lockfiles`.", "removal_version": "3.0.0.dev0", "scoped_cmd_line_args": [ "--python-resolve-all-constraints", @@ -18006,7 +18006,7 @@ "display_args": ["--[no-]pytype-skip"], "env_var": "PANTS_PYTYPE_SKIP", "fromfile": false, - "help": "If true, don't use Pytype when running `scie-pants-linux-x86_64 check`.", + "help": "If true, don't use Pytype when running `pants check`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pytype-skip", "--no-pytype-skip"], @@ -18229,7 +18229,7 @@ "display_args": ["--[no-]pyupgrade-skip"], "env_var": "PANTS_PYUPGRADE_SKIP", "fromfile": false, - "help": "If true, don't use pyupgrade when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use pyupgrade when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pyupgrade-skip", "--no-pyupgrade-skip"], @@ -18394,7 +18394,7 @@ "display_args": ["--[no-]regex-lint-skip"], "env_var": "PANTS_REGEX_LINT_SKIP", "fromfile": false, - "help": "If true, don't use regex-lint when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use regex-lint when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--regex-lint-skip", "--no-regex-lint-skip"], @@ -19616,7 +19616,7 @@ "display_args": ["--[no-]ruff-skip"], "env_var": "PANTS_RUFF_SKIP", "fromfile": false, - "help": "If true, don't use Ruff when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Ruff when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--ruff-skip", "--no-ruff-skip"], @@ -19913,7 +19913,7 @@ "display_args": ["--scalafmt-lockfile="], "env_var": "PANTS_SCALAFMT_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.19.0rc1/src/python/pants/backend/scala/lint/scalafmt/scalafmt.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalafmt`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.19.0rc1/src/python/pants/backend/scala/lint/scalafmt/scalafmt.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=scalafmt`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalafmt-lockfile"], @@ -19946,7 +19946,7 @@ "display_args": ["--[no-]scalafmt-skip"], "env_var": "PANTS_SCALAFMT_SKIP", "fromfile": false, - "help": "If true, don't use scalafmt when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use scalafmt when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalafmt-skip", "--no-scalafmt-skip"], @@ -20111,7 +20111,7 @@ "display_args": ["--scalapb-lockfile="], "env_var": "PANTS_SCALAPB_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.19.0rc1/src/python/pants/backend/codegen/protobuf/scala/scalapbc.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalapb`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.19.0rc1/src/python/pants/backend/codegen/protobuf/scala/scalapbc.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=scalapb`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalapb-lockfile"], @@ -20279,7 +20279,7 @@ "display_args": ["--scalatest-lockfile="], "env_var": "PANTS_SCALATEST_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.19.0rc1/src/python/pants/backend/scala/subsystems/scalatest.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalatest`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.19.0rc1/src/python/pants/backend/scala/subsystems/scalatest.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=scalatest`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalatest-lockfile"], @@ -20312,7 +20312,7 @@ "display_args": ["--[no-]scalatest-skip"], "env_var": "PANTS_SCALATEST_SKIP", "fromfile": false, - "help": "If true, don't use Scalatest when running `scie-pants-linux-x86_64 test`.", + "help": "If true, don't use Scalatest when running `pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalatest-skip", "--no-scalatest-skip"], @@ -21047,7 +21047,7 @@ "display_args": ["--[no-]semgrep-skip"], "env_var": "PANTS_SEMGREP_SKIP", "fromfile": false, - "help": "If true, don't use Semgrep when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Semgrep when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--semgrep-skip", "--no-semgrep-skip"], @@ -21523,7 +21523,7 @@ "display_args": ["--[no-]shellcheck-skip"], "env_var": "PANTS_SHELLCHECK_SKIP", "fromfile": false, - "help": "If true, don't use Shellcheck when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Shellcheck when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--shellcheck-skip", "--no-shellcheck-skip"], @@ -21812,7 +21812,7 @@ "display_args": ["--[no-]shell-test-skip"], "env_var": "PANTS_SHELL_TEST_SKIP", "fromfile": false, - "help": "If true, don't use Test with shell scripts when running `scie-pants-linux-x86_64 test`.", + "help": "If true, don't use Test with shell scripts when running `pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--shell-test-skip", "--no-shell-test-skip"], @@ -21965,7 +21965,7 @@ "display_args": ["--[no-]shfmt-skip"], "env_var": "PANTS_SHFMT_SKIP", "fromfile": false, - "help": "If true, don't use shfmt when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use shfmt when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--shfmt-skip", "--no-shfmt-skip"], @@ -22220,7 +22220,7 @@ "display_args": ["--[no-]shunit2-skip"], "env_var": "PANTS_SHUNIT2_SKIP", "fromfile": false, - "help": "If true, don't use shunit2 when running `scie-pants-linux-x86_64 test`.", + "help": "If true, don't use shunit2 when running `pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--shunit2-skip", "--no-shunit2-skip"], @@ -22535,7 +22535,7 @@ "display_args": ["--[no-]spectral-skip"], "env_var": "PANTS_SPECTRAL_SKIP", "fromfile": false, - "help": "If true, don't use Spectral when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Spectral when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--spectral-skip", "--no-spectral-skip"], @@ -23254,7 +23254,7 @@ "display_args": ["--[no-]terraform-fmt-skip"], "env_var": "PANTS_TERRAFORM_FMT_SKIP", "fromfile": false, - "help": "If true, don't use `terraform fmt` when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use `terraform fmt` when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -23390,7 +23390,7 @@ "display_args": ["--[no-]terraform-validate-skip"], "env_var": "PANTS_TERRAFORM_VALIDATE_SKIP", "fromfile": false, - "help": "If true, don't use `terraform validate` when running `scie-pants-linux-x86_64 check`.", + "help": "If true, don't use `terraform validate` when running `pants check`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -24276,7 +24276,7 @@ "display_args": ["--[no-]twine-skip"], "env_var": "PANTS_TWINE_SKIP", "fromfile": false, - "help": "If true, don't use Twine when running `scie-pants-linux-x86_64 publish`.", + "help": "If true, don't use Twine when running `pants publish`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--twine-skip", "--no-twine-skip"], @@ -24552,7 +24552,7 @@ "display_args": ["--pants-version="], "env_var": "PANTS_VERSION", "fromfile": false, - "help": "Use this Pants version. Note that Pants only uses this to verify that you are using the requested version, as Pants cannot dynamically change the version it is using once the program is already running.\n\nIf you use the `scie-pants-linux-x86_64` script from https://www.pantsbuild.org/v2.19/docs/installation, however, changing the value in your `pants.toml` will cause the new version to be installed and run automatically.\n\nRun `scie-pants-linux-x86_64 --version` to check what is being used.", + "help": "Use this Pants version. Note that Pants only uses this to verify that you are using the requested version, as Pants cannot dynamically change the version it is using once the program is already running.\n\nIf you use the `pants` script from https://www.pantsbuild.org/v2.19/docs/installation, however, changing the value in your `pants.toml` will cause the new version to be installed and run automatically.\n\nRun `pants --version` to check what is being used.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pants-version"], @@ -25014,7 +25014,7 @@ "display_args": ["--[no-]yamllint-skip"], "env_var": "PANTS_YAMLLINT_SKIP", "fromfile": false, - "help": "If true, don't use Yamllint when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Yamllint when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--yamllint-skip", "--no-yamllint-skip"], @@ -25301,7 +25301,7 @@ "display_args": ["--[no-]yapf-skip"], "env_var": "PANTS_YAPF_SKIP", "fromfile": false, - "help": "If true, don't use yapf when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use yapf when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--yapf-skip", "--no-yapf-skip"], @@ -64229,7 +64229,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -64237,7 +64237,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -64261,7 +64261,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -64269,7 +64269,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -64285,7 +64285,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -64301,7 +64301,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -64309,7 +64309,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -64325,7 +64325,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -64341,7 +64341,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -64349,7 +64349,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -64485,7 +64485,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -64493,7 +64493,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -64501,7 +64501,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -64509,7 +64509,7 @@ { "alias": "packages", "default": null, - "description": "Addresses to any targets that can be built with `scie-pants-linux-x86_64 package`, e.g. `[\"project:app\"]`.\n\nPants will build the assets as if you had run `scie-pants-linux-x86_64 package`. It will include the results in your archive using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or even another `archive`.", + "description": "Addresses to any targets that can be built with `pants package`, e.g. `[\"project:app\"]`.\n\nPants will build the assets as if you had run `pants package`. It will include the results in your archive using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `pants package`, e.g. a `pex_binary`, `python_awslambda`, or even another `archive`.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -64541,7 +64541,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -64549,7 +64549,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -64565,7 +64565,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -64573,7 +64573,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -64637,7 +64637,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -64645,7 +64645,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -64909,7 +64909,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -64917,7 +64917,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -64933,7 +64933,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -65021,7 +65021,7 @@ { "alias": "skip_push", "default": "False", - "description": "If true, do not push this image to registries when running `scie-pants-linux-x86_64 publish`.", + "description": "If true, do not push this image to registries when running `pants publish`.", "provider": "", "required": false, "type_hint": "bool" @@ -65093,7 +65093,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -65125,7 +65125,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -65133,7 +65133,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -65221,7 +65221,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -65229,7 +65229,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -65261,7 +65261,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -65269,7 +65269,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -65301,7 +65301,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -65309,7 +65309,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -65341,7 +65341,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -65349,7 +65349,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -65381,7 +65381,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -65389,7 +65389,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -65421,7 +65421,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -65429,7 +65429,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -65461,7 +65461,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -65469,7 +65469,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -65477,7 +65477,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -65501,7 +65501,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -65509,7 +65509,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -65533,7 +65533,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -65549,7 +65549,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -65557,7 +65557,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -65565,7 +65565,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -65661,7 +65661,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -65669,7 +65669,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -65741,7 +65741,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -65749,7 +65749,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -65757,7 +65757,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -65853,7 +65853,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -65861,7 +65861,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -65869,7 +65869,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -65893,7 +65893,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -65901,7 +65901,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -65949,7 +65949,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -65957,7 +65957,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -65981,7 +65981,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -65989,7 +65989,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built directory tree should be located.\n\nIf undefined, this will use the path to the BUILD file, For example, `src/charts/mychart:tgt_name` would be `src.charts.mychart/tgt_name/`.\n\nRegardless of whether you use the default or set this field, the path will end with Helms's file format of `-.tgz`, where `chart_name` and `chart_version` are the values extracted from the Chart.yaml file. So, using the default for this field, the target `src/charts/mychart:tgt_name` might have a final path like `src.charts.mychart/tgt_name/mychart-0.1.0.tgz`.\n\nWhen running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built directory tree should be located.\n\nIf undefined, this will use the path to the BUILD file, For example, `src/charts/mychart:tgt_name` would be `src.charts.mychart/tgt_name/`.\n\nRegardless of whether you use the default or set this field, the path will end with Helms's file format of `-.tgz`, where `chart_name` and `chart_version` are the values extracted from the Chart.yaml file. So, using the default for this field, the target `src/charts/mychart:tgt_name` might have a final path like `src.charts.mychart/tgt_name/mychart-0.1.0.tgz`.\n\nWhen running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -66029,7 +66029,7 @@ { "alias": "skip_push", "default": "False", - "description": "If set to true, do not push this Helm chart to registries when running `scie-pants-linux-x86_64 publish`.", + "description": "If set to true, do not push this Helm chart to registries when running `pants publish`.", "provider": "", "required": false, "type_hint": "bool" @@ -66037,7 +66037,7 @@ { "alias": "skip_lint", "default": "False", - "description": "If set to true, do not run any linting in this Helm chart when running `scie-pants-linux-x86_64 lint`.", + "description": "If set to true, do not run any linting in this Helm chart when running `pants lint`.", "provider": "", "required": false, "type_hint": "bool" @@ -66053,7 +66053,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66061,7 +66061,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -66085,7 +66085,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66165,7 +66165,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66173,7 +66173,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -66189,7 +66189,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66221,7 +66221,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66229,7 +66229,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -66245,7 +66245,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66285,7 +66285,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66293,7 +66293,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -66301,7 +66301,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66365,7 +66365,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66373,7 +66373,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -66397,7 +66397,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66445,7 +66445,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66453,7 +66453,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -66485,7 +66485,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66525,7 +66525,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66533,7 +66533,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -66565,7 +66565,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66605,7 +66605,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66613,7 +66613,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -66709,7 +66709,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66717,7 +66717,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -66741,7 +66741,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66765,7 +66765,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -66781,7 +66781,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66789,7 +66789,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -66797,7 +66797,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66869,7 +66869,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66877,7 +66877,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -66893,7 +66893,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66957,7 +66957,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -66965,7 +66965,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -66973,7 +66973,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -67045,7 +67045,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -67053,7 +67053,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -67077,7 +67077,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -67133,7 +67133,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -67141,7 +67141,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -67181,7 +67181,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -67189,7 +67189,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -67445,7 +67445,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -67453,7 +67453,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -67461,7 +67461,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -67493,7 +67493,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -67501,7 +67501,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -67525,7 +67525,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -67541,7 +67541,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -67549,7 +67549,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -67557,7 +67557,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -67589,7 +67589,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -67597,7 +67597,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -67621,7 +67621,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -67637,7 +67637,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -67645,7 +67645,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -67685,7 +67685,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -67693,7 +67693,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -67741,7 +67741,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -67877,7 +67877,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -67885,7 +67885,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -67917,7 +67917,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -68077,7 +68077,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -68093,7 +68093,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -68101,7 +68101,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -68157,7 +68157,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -68165,7 +68165,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -68221,7 +68221,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -68229,7 +68229,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -68237,7 +68237,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -68333,7 +68333,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -68341,7 +68341,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -68437,7 +68437,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -68453,7 +68453,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -68461,7 +68461,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -68469,7 +68469,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built directory tree should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:bin` would be `src.python.project/bin/`.\n\nRegardless of whether you use the default or set this field, the path will end with PyOxidizer's file format of `/{debug,release}/install/`, where `platform` is a Rust platform triplet like `aarch-64-apple-darwin` and `binary_name` is the value of the `binary_name` field. So, using the default for this field, the target `src/python/project:bin` might have a final path like `src.python.project/bin/aarch-64-apple-darwin/release/bin`.\n\nWhen running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built directory tree should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:bin` would be `src.python.project/bin/`.\n\nRegardless of whether you use the default or set this field, the path will end with PyOxidizer's file format of `/{debug,release}/install/`, where `platform` is a Rust platform triplet like `aarch-64-apple-darwin` and `binary_name` is the value of the `binary_name` field. So, using the default for this field, the target `src/python/project:bin` might have a final path like `src.python.project/bin/aarch-64-apple-darwin/release/bin`.\n\nWhen running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -68533,7 +68533,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -68541,7 +68541,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -68549,7 +68549,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -68597,7 +68597,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -68621,7 +68621,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -68629,7 +68629,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -68637,7 +68637,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -68693,7 +68693,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": true, "type_hint": "Iterable[str]" @@ -68709,7 +68709,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -68717,7 +68717,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -68733,7 +68733,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -68741,7 +68741,7 @@ { "alias": "entry_points", "default": null, - "description": "Any entry points, such as `console_scripts` and `gui_scripts`.\n\nSpecify as a nested dictionary, with a dictionary for each type of entry point, e.g. `console_scripts` vs. `gui_scripts`. Each dictionary maps the entry point name to either a setuptools entry point (`\"path.to.module:func\"`) or a Pants target address to a `pex_binary` target.\n\nExample:\n\n entry_points={\n \"console_scripts\": {\n \"my-script\": \"project.app:main\",\n \"another-script\": \"project/subdir:pex_binary_tgt\"\n }\n }\n\nNote that Pants will assume that any value that either starts with `:` or has `/` in it, is a target address to a `pex_binary` target. Otherwise, it will assume it's a setuptools entry point as defined by https://packaging.python.org/specifications/entry-points/#entry-points-specification. Use `//` as a prefix for target addresses if you need to disambiguate.\n\nPants will attempt to infer dependencies, which you can confirm by running:\n\n scie-pants-linux-x86_64 dependencies ", + "description": "Any entry points, such as `console_scripts` and `gui_scripts`.\n\nSpecify as a nested dictionary, with a dictionary for each type of entry point, e.g. `console_scripts` vs. `gui_scripts`. Each dictionary maps the entry point name to either a setuptools entry point (`\"path.to.module:func\"`) or a Pants target address to a `pex_binary` target.\n\nExample:\n\n entry_points={\n \"console_scripts\": {\n \"my-script\": \"project.app:main\",\n \"another-script\": \"project/subdir:pex_binary_tgt\"\n }\n }\n\nNote that Pants will assume that any value that either starts with `:` or has `/` in it, is a target address to a `pex_binary` target. Otherwise, it will assume it's a setuptools entry point as defined by https://packaging.python.org/specifications/entry-points/#entry-points-specification. Use `//` as a prefix for target addresses if you need to disambiguate.\n\nPants will attempt to infer dependencies, which you can confirm by running:\n\n pants dependencies ", "provider": "", "required": false, "type_hint": "Dict[str, Dict[str, str]] | None" @@ -68853,7 +68853,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -68861,7 +68861,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -68869,7 +68869,7 @@ { "alias": "output_path", "default": null, - "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", + "description": "Where the built asset should be located.\n\nIf undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`.\n\nWhen running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`).\n\nWarning: setting this value risks naming collisions with other package targets you may have.", "provider": "", "required": false, "type_hint": "str | None" @@ -68877,7 +68877,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -68941,7 +68941,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -68949,7 +68949,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -68965,7 +68965,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -69013,7 +69013,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -69021,7 +69021,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -69077,7 +69077,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -69085,7 +69085,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -69101,7 +69101,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -69261,7 +69261,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -69269,7 +69269,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -69421,7 +69421,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -69453,7 +69453,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -69461,7 +69461,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -69469,7 +69469,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -69517,7 +69517,7 @@ { "alias": "runtime_package_dependencies", "default": null, - "description": "Addresses to targets that can be built with the `scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_aws_lambda_function`, or an `archive`.", + "description": "Addresses to targets that can be built with the `pants package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `pants package`, e.g. a `pex_binary`, `python_aws_lambda_function`, or an `archive`.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -69693,7 +69693,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -69701,7 +69701,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -69853,7 +69853,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -69877,7 +69877,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -69885,7 +69885,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -70029,7 +70029,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -70077,7 +70077,7 @@ { "alias": "runtime_package_dependencies", "default": null, - "description": "Addresses to targets that can be built with the `scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_aws_lambda_function`, or an `archive`.", + "description": "Addresses to targets that can be built with the `pants package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `pants package`, e.g. a `pex_binary`, `python_aws_lambda_function`, or an `archive`.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -70125,7 +70125,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -70133,7 +70133,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -70173,7 +70173,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -70181,7 +70181,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -70453,7 +70453,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -70461,7 +70461,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -70469,7 +70469,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -70493,7 +70493,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -70501,7 +70501,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -70525,7 +70525,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -70541,7 +70541,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -70549,7 +70549,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -70597,7 +70597,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -70605,7 +70605,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -70709,7 +70709,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -70717,7 +70717,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -70725,7 +70725,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -70797,7 +70797,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -70805,7 +70805,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -70837,7 +70837,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -70901,7 +70901,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -70909,7 +70909,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -70917,7 +70917,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -70989,7 +70989,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -70997,7 +70997,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -71029,7 +71029,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -71085,7 +71085,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -71093,7 +71093,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -71125,7 +71125,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -71133,7 +71133,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -71141,7 +71141,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -71213,7 +71213,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -71221,7 +71221,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -71245,7 +71245,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -71309,7 +71309,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -71317,7 +71317,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -71445,7 +71445,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -71453,7 +71453,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -71461,7 +71461,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -71501,7 +71501,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -71509,7 +71509,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -71549,7 +71549,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -71565,7 +71565,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -71573,7 +71573,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -71589,7 +71589,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -71621,7 +71621,7 @@ { "alias": "runtime_package_dependencies", "default": null, - "description": "Addresses to targets that can be built with the `scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_aws_lambda_function`, or an `archive`.", + "description": "Addresses to targets that can be built with the `pants package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `pants package`, e.g. a `pex_binary`, `python_aws_lambda_function`, or an `archive`.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -71653,7 +71653,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -71661,7 +71661,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -71701,7 +71701,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -71733,7 +71733,7 @@ { "alias": "runtime_package_dependencies", "default": null, - "description": "Addresses to targets that can be built with the `scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_aws_lambda_function`, or an `archive`.", + "description": "Addresses to targets that can be built with the `pants package` goal and whose resulting artifacts should be included in the test run.\n\nPants will build the artifacts as if you had run `pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`).\n\nYou can include anything that can be built by `pants package`, e.g. a `pex_binary`, `python_aws_lambda_function`, or an `archive`.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -71749,7 +71749,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -71757,7 +71757,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -71813,7 +71813,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -71821,7 +71821,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -71829,7 +71829,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -71845,7 +71845,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -71853,7 +71853,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -71861,7 +71861,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -71901,7 +71901,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -71909,7 +71909,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -71917,7 +71917,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -71941,7 +71941,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -71949,7 +71949,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -71957,7 +71957,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -71989,7 +71989,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -71997,7 +71997,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -72029,7 +72029,7 @@ { "alias": "dependencies", "default": null, - "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", + "description": "Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`.\n\nThis augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result.\n\nSee https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory.\n\nIf the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`.\n\nYou may exclude dependencies by prefixing with `!`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -72045,7 +72045,7 @@ { "alias": "tags", "default": null, - "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag.", + "description": "Arbitrary strings to describe a target.\n\nFor example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag.", "provider": "", "required": false, "type_hint": "Iterable[str] | None" @@ -72053,7 +72053,7 @@ { "alias": "description", "default": null, - "description": "A human-readable description of the target.\n\nUse `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions.", + "description": "A human-readable description of the target.\n\nUse `pants list --documented ::` to see all targets with descriptions.", "provider": "", "required": false, "type_hint": "str | None" @@ -72422,7 +72422,7 @@ "display_args": ["--pants-version="], "env_var": "PANTS_VERSION", "fromfile": false, - "help": "Use this Pants version. Note that Pants only uses this to verify that you are using the requested version, as Pants cannot dynamically change the version it is using once the program is already running.\n\nIf you use the `scie-pants-linux-x86_64` script from https://www.pantsbuild.org/v2.19/docs/installation, however, changing the value in your `pants.toml` will cause the new version to be installed and run automatically.\n\nRun `scie-pants-linux-x86_64 --version` to check what is being used.", + "help": "Use this Pants version. Note that Pants only uses this to verify that you are using the requested version, as Pants cannot dynamically change the version it is using once the program is already running.\n\nIf you use the `pants` script from https://www.pantsbuild.org/v2.19/docs/installation, however, changing the value in your `pants.toml` will cause the new version to be installed and run automatically.\n\nRun `pants --version` to check what is being used.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pants-version"], @@ -72482,7 +72482,7 @@ { "details": "from env var PANTS_BIN_NAME", "rank": "ENVIRONMENT", - "value": "/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64" + "value": "/home/josh/work/scie-pants/dist/pants" } ] } @@ -73683,7 +73683,7 @@ ], "env_var": "PANTS_PROCESS_EXECUTION_GRACEFUL_SHUTDOWN_TIMEOUT", "fromfile": false, - "help": "The time in seconds to wait when gracefully shutting down an interactive process (such as one opened using `scie-pants-linux-x86_64 run`) before killing it.", + "help": "The time in seconds to wait when gracefully shutting down an interactive process (such as one opened using `pants run`) before killing it.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -75542,7 +75542,7 @@ "display_args": ["--[no-]add-trailing-comma-skip"], "env_var": "PANTS_ADD_TRAILING_COMMA_SKIP", "fromfile": false, - "help": "If true, don't use add-trailing-comma when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use add-trailing-comma when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -75938,7 +75938,7 @@ "display_args": ["--[no-]autoflake-skip"], "env_var": "PANTS_AUTOFLAKE_SKIP", "fromfile": false, - "help": "If true, don't use Autoflake when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Autoflake when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--autoflake-skip", "--no-autoflake-skip"], @@ -76168,7 +76168,7 @@ "display_args": ["--[no-]bandit-skip"], "env_var": "PANTS_BANDIT_SKIP", "fromfile": false, - "help": "If true, don't use Bandit when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Bandit when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--bandit-skip", "--no-bandit-skip"], @@ -76470,7 +76470,7 @@ "display_args": ["--[no-]black-skip"], "env_var": "PANTS_BLACK_SKIP", "fromfile": false, - "help": "If true, don't use Black when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Black when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--black-skip", "--no-black-skip"], @@ -76804,7 +76804,7 @@ "display_args": ["--[no-]buf-format-skip"], "env_var": "PANTS_BUF_FORMAT_SKIP", "fromfile": false, - "help": "If true, don't use Buf when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Buf when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--buf-format-skip", "--no-buf-format-skip"], @@ -76837,7 +76837,7 @@ "display_args": ["--[no-]buf-lint-skip"], "env_var": "PANTS_BUF_LINT_SKIP", "fromfile": false, - "help": "If true, don't use Buf when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Buf when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--buf-lint-skip", "--no-buf-lint-skip"], @@ -76951,7 +76951,7 @@ "display_args": ["--[no-]build-deprecations-fixer-skip"], "env_var": "PANTS_BUILD_DEPRECATIONS_FIXER_SKIP", "fromfile": false, - "help": "If true, don't use BUILD Deprecations Fixer when running `scie-pants-linux-x86_64 fix`.", + "help": "If true, don't use BUILD Deprecations Fixer when running `pants fix`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -77190,7 +77190,7 @@ "display_args": ["--[no-]buildifier-skip"], "env_var": "PANTS_BUILDIFIER_SKIP", "fromfile": false, - "help": "If true, don't use Buildifier when running `scie-pants-linux-x86_64 fmt`.", + "help": "If true, don't use Buildifier when running `pants fmt`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--buildifier-skip", "--no-buildifier-skip"], @@ -77447,7 +77447,7 @@ "display_args": ["--cli-alias=\"{'key1': val1, 'key2': val2, ...}\""], "env_var": "PANTS_CLI_ALIAS", "fromfile": false, - "help": "Register command line aliases.\n\nExample:\n\n [cli.alias]\n green = \"fmt lint check\"\n all-changed = \"--changed-since=HEAD --changed-dependents=transitive\"\n\nThis would allow you to run `scie-pants-linux-x86_64 green all-changed`, which is shorthand for `scie-pants-linux-x86_64 fmt lint check --changed-since=HEAD --changed-dependents=transitive`.\n\nNotice: this option must be placed in a config file (e.g. `pants.toml` or `pantsrc`) to have any effect.", + "help": "Register command line aliases.\n\nExample:\n\n [cli.alias]\n green = \"fmt lint check\"\n all-changed = \"--changed-since=HEAD --changed-dependents=transitive\"\n\nThis would allow you to run `pants green all-changed`, which is shorthand for `pants fmt lint check --changed-since=HEAD --changed-dependents=transitive`.\n\nNotice: this option must be placed in a config file (e.g. `pants.toml` or `pantsrc`) to have any effect.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--cli-alias"], @@ -79037,7 +79037,7 @@ "display_args": ["--[no-]docformatter-skip"], "env_var": "PANTS_DOCFORMATTER_SKIP", "fromfile": false, - "help": "If true, don't use docformatter when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use docformatter when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -79565,7 +79565,7 @@ ], "env_var": "PANTS_DOCKER_RUN_ARGS", "fromfile": false, - "help": "Additional arguments to use for `docker run` invocations.\n\nExample:\n\n $ scie-pants-linux-x86_64 run --docker-run-args=\"-p 127.0.0.1:80:8080/tcp --name demo\" src/example:image -- [image entrypoint args]\n\nTo provide the top-level options to the `docker` client, use `[docker].env_vars` to configure the [Environment variables](https://docs.docker.com/engine/reference/commandline/cli/#environment-variables) as appropriate.\n\nThe arguments for the image entrypoint may be passed on the command line after a double dash (`--`), or using the `--run-args` option.\n\nDefaults to `--interactive --tty` when stdout is connected to a terminal.", + "help": "Additional arguments to use for `docker run` invocations.\n\nExample:\n\n $ pants run --docker-run-args=\"-p 127.0.0.1:80:8080/tcp --name demo\" src/example:image -- [image entrypoint args]\n\nTo provide the top-level options to the `docker` client, use `[docker].env_vars` to configure the [Environment variables](https://docs.docker.com/engine/reference/commandline/cli/#environment-variables) as appropriate.\n\nThe arguments for the image entrypoint may be passed on the command line after a double dash (`--`), or using the `--run-args` option.\n\nDefaults to `--interactive --tty` when stdout is connected to a terminal.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--docker-run-args"], @@ -80451,7 +80451,7 @@ ], "env_var": "PANTS_EXPERIMENTAL_BSP_RUNNER_ENV_VARS", "fromfile": false, - "help": "Environment variables to set in the BSP runner script when setting up BSP in a repository. Entries are either strings in the form `ENV_VAR=value` to set an explicit value; or just `ENV_VAR` to copy the value from Pants' own environment when the experimental-bsp goal was run.\n\nThis option only takes effect when the BSP runner script is written. If the option changes, you must run `scie-pants-linux-x86_64 experimental-bsp` again to write a new copy of the BSP runner script.\n\nNote: The environment variables passed to the Pants BSP server will be those set for your IDE and not your shell. For example, on macOS, the IDE is generally launched by `launchd` after clicking on a Dock icon, and not from the shell. Thus, any environment variables set for your shell will likely not be seen by the Pants BSP server. At the very least, on macOS consider writing an explicit PATH into the BSP runner script via this option.", + "help": "Environment variables to set in the BSP runner script when setting up BSP in a repository. Entries are either strings in the form `ENV_VAR=value` to set an explicit value; or just `ENV_VAR` to copy the value from Pants' own environment when the experimental-bsp goal was run.\n\nThis option only takes effect when the BSP runner script is written. If the option changes, you must run `pants experimental-bsp` again to write a new copy of the BSP runner script.\n\nNote: The environment variables passed to the Pants BSP server will be those set for your IDE and not your shell. For example, on macOS, the IDE is generally launched by `launchd` after clicking on a Dock icon, and not from the shell. Thus, any environment variables set for your shell will likely not be seen by the Pants BSP server. At the very least, on macOS consider writing an explicit PATH into the BSP runner script via this option.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--experimental-bsp-runner-env-vars"], @@ -81238,7 +81238,7 @@ "display_args": ["--[no-]fix-skip-formatters"], "env_var": "PANTS_FIX_SKIP_FORMATTERS", "fromfile": false, - "help": "If true, skip running all formatters.\n\nFYI: when running `scie-pants-linux-x86_64 fix fmt ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `fix` where possible.", + "help": "If true, skip running all formatters.\n\nFYI: when running `pants fix fmt ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `fix` where possible.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -81548,7 +81548,7 @@ "display_args": ["--[no-]flake8-skip"], "env_var": "PANTS_FLAKE8_SKIP", "fromfile": false, - "help": "If true, don't use Flake8 when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Flake8 when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--flake8-skip", "--no-flake8-skip"], @@ -81702,7 +81702,7 @@ "display_args": ["--generate-lockfiles-custom-command="], "env_var": "PANTS_GENERATE_LOCKFILES_CUSTOM_COMMAND", "fromfile": false, - "help": "If set, lockfile headers will say to run this command to regenerate the lockfile, rather than running `scie-pants-linux-x86_64 generate-lockfiles --resolve=` like normal.", + "help": "If set, lockfile headers will say to run this command to regenerate the lockfile, rather than running `pants generate-lockfiles --resolve=` like normal.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--generate-lockfiles-custom-command"], @@ -81734,7 +81734,7 @@ ], "env_var": "PANTS_GENERATE_LOCKFILES_RESOLVE", "fromfile": false, - "help": "Only generate lockfiles for the specified resolve(s).\n\nResolves are the logical names for the different lockfiles used in your project. For your own code's dependencies, these come from backend-specific configuration such as `[python].resolves`. For tool lockfiles, resolve names are the options scope for that tool such as `black`, `pytest`, and `mypy-protobuf`.\n\nFor example, you can run `scie-pants-linux-x86_64 generate-lockfiles --resolve=black --resolve=pytest --resolve=data-science` to only generate lockfiles for those two tools and your resolve named `data-science`.\n\nIf you specify an invalid resolve name, like 'fake', Pants will output all possible values.\n\nIf not specified, Pants will generate lockfiles for all resolves.", + "help": "Only generate lockfiles for the specified resolve(s).\n\nResolves are the logical names for the different lockfiles used in your project. For your own code's dependencies, these come from backend-specific configuration such as `[python].resolves`. For tool lockfiles, resolve names are the options scope for that tool such as `black`, `pytest`, and `mypy-protobuf`.\n\nFor example, you can run `pants generate-lockfiles --resolve=black --resolve=pytest --resolve=data-science` to only generate lockfiles for those two tools and your resolve named `data-science`.\n\nIf you specify an invalid resolve name, like 'fake', Pants will output all possible values.\n\nIf not specified, Pants will generate lockfiles for all resolves.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--generate-lockfiles-resolve"], @@ -82122,7 +82122,7 @@ "display_args": ["--[no-]go-test-skip"], "env_var": "PANTS_GO_TEST_SKIP", "fromfile": false, - "help": "If true, don't use Go test binary when running `scie-pants-linux-x86_64 test`.", + "help": "If true, don't use Go test binary when running `pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--go-test-skip", "--no-go-test-skip"], @@ -82451,7 +82451,7 @@ "display_args": ["--[no-]gofmt-skip"], "env_var": "PANTS_GOFMT_SKIP", "fromfile": false, - "help": "If true, don't use gofmt when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use gofmt when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--gofmt-skip", "--no-gofmt-skip"], @@ -83238,7 +83238,7 @@ "display_args": ["--google-java-format-lockfile="], "env_var": "PANTS_GOOGLE_JAVA_FORMAT_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.19.0rc1/src/python/pants/backend/java/lint/google_java_format/google_java_format.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=google-java-format`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.19.0rc1/src/python/pants/backend/java/lint/google_java_format/google_java_format.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=google-java-format`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--google-java-format-lockfile"], @@ -83308,7 +83308,7 @@ "display_args": ["--[no-]google-java-format-skip"], "env_var": "PANTS_GOOGLE_JAVA_FORMAT_SKIP", "fromfile": false, - "help": "If true, don't use Google Java Format when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Google Java Format when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -83854,7 +83854,7 @@ "display_args": ["--[no-]hadolint-skip"], "env_var": "PANTS_HADOLINT_SKIP", "fromfile": false, - "help": "If true, don't use Hadolint when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Hadolint when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--hadolint-skip", "--no-hadolint-skip"], @@ -84916,7 +84916,7 @@ "display_args": ["--[no-]helm-unittest-skip"], "env_var": "PANTS_HELM_UNITTEST_SKIP", "fromfile": false, - "help": "If true, don't use helmunittestsubsystem when running `scie-pants-linux-x86_64 test`.", + "help": "If true, don't use helmunittestsubsystem when running `pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -85396,7 +85396,7 @@ "display_args": ["--[no-]isort-skip"], "env_var": "PANTS_ISORT_SKIP", "fromfile": false, - "help": "If true, don't use isort when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use isort when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--isort-skip", "--no-isort-skip"], @@ -85538,7 +85538,7 @@ "display_args": ["--jarjar-lockfile="], "env_var": "PANTS_JARJAR_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.19.0rc1/src/python/pants/jvm/shading/jarjar.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=jarjar`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.19.0rc1/src/python/pants/jvm/shading/jarjar.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=jarjar`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--jarjar-lockfile"], @@ -85958,7 +85958,7 @@ "display_args": ["--junit-lockfile="], "env_var": "PANTS_JUNIT_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.19.0rc1/src/python/pants/jvm/test/junit.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=junit`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.19.0rc1/src/python/pants/jvm/test/junit.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=junit`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--junit-lockfile"], @@ -86062,7 +86062,7 @@ "display_args": ["--[no-]junit-skip"], "env_var": "PANTS_JUNIT_SKIP", "fromfile": false, - "help": "If true, don't use JUnit when running `scie-pants-linux-x86_64 test`.", + "help": "If true, don't use JUnit when running `pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--junit-skip", "--no-junit-skip"], @@ -86715,7 +86715,7 @@ "display_args": ["--ktlint-lockfile="], "env_var": "PANTS_KTLINT_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.19.0rc1/src/python/pants/backend/kotlin/lint/ktlint/ktlint.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=ktlint`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.19.0rc1/src/python/pants/backend/kotlin/lint/ktlint/ktlint.lock for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=ktlint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--ktlint-lockfile"], @@ -86783,7 +86783,7 @@ "display_args": ["--[no-]ktlint-skip"], "env_var": "PANTS_KTLINT_SKIP", "fromfile": false, - "help": "If true, don't use Ktlint when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Ktlint when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--ktlint-skip", "--no-ktlint-skip"], @@ -86894,7 +86894,7 @@ "display_args": ["--[no-]lint-skip-formatters"], "env_var": "PANTS_LINT_SKIP_FORMATTERS", "fromfile": false, - "help": "If true, skip running all formatters in check-only mode.\n\nFYI: when running `scie-pants-linux-x86_64 fmt lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `lint` where possible.", + "help": "If true, skip running all formatters in check-only mode.\n\nFYI: when running `pants fmt lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `lint` where possible.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -86933,7 +86933,7 @@ "display_args": ["--[no-]lint-skip-fixers"], "env_var": "PANTS_LINT_SKIP_FIXERS", "fromfile": false, - "help": "If true, skip running all fixers in check-only mode.\n\nFYI: when running `scie-pants-linux-x86_64 fix lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fix` when running `lint` where possible.", + "help": "If true, skip running all fixers in check-only mode.\n\nFYI: when running `pants fix lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fix` when running `lint` where possible.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -87345,7 +87345,7 @@ "display_args": ["--[no-]mypy-skip"], "env_var": "PANTS_MYPY_SKIP", "fromfile": false, - "help": "If true, don't use MyPy when running `scie-pants-linux-x86_64 check`.", + "help": "If true, don't use MyPy when running `pants check`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--mypy-skip", "--no-mypy-skip"], @@ -87688,7 +87688,7 @@ ], "env_var": "PANTS_NODEJS_RESOLVES", "fromfile": false, - "help": "A mapping of names to lockfile paths used in your project.\n\nSpecifying a resolve name is optional. If unspecified, the default resolve name is calculated by taking the path from the source root to the directory containing the lockfile and replacing '/' with '.' in that path.\n\nExample: An npm lockfile located at `src/js/package/package-lock.json' will result in a resolve named `js.package`, assuming src/ is a source root.\n\nRun `scie-pants-linux-x86_64 generate-lockfiles` to generate the lockfile(s).", + "help": "A mapping of names to lockfile paths used in your project.\n\nSpecifying a resolve name is optional. If unspecified, the default resolve name is calculated by taking the path from the source root to the directory containing the lockfile and replacing '/' with '.' in that path.\n\nExample: An npm lockfile located at `src/js/package/package-lock.json' will result in a resolve named `js.package`, assuming src/ is a source root.\n\nRun `pants generate-lockfiles` to generate the lockfile(s).", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--nodejs-resolves"], @@ -88106,7 +88106,7 @@ "display_args": ["--[no-]openapi-format-skip"], "env_var": "PANTS_OPENAPI_FORMAT_SKIP", "fromfile": false, - "help": "If true, don't use openapi-format when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use openapi-format when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -88803,7 +88803,7 @@ "display_args": ["--[no-]preamble-skip"], "env_var": "PANTS_PREAMBLE_SKIP", "fromfile": false, - "help": "If true, don't use preamble when running `scie-pants-linux-x86_64 fmt`.", + "help": "If true, don't use preamble when running `pants fmt`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--preamble-skip", "--no-preamble-skip"], @@ -88959,7 +88959,7 @@ "display_args": ["--protobuf-java-grpc-lockfile="], "env_var": "PANTS_PROTOBUF_JAVA_GRPC_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.19.0rc1/src/python/pants/backend/codegen/protobuf/java/grpc-java.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=protobuf-java-grpc`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.19.0rc1/src/python/pants/backend/codegen/protobuf/java/grpc-java.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=protobuf-java-grpc`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--protobuf-java-grpc-lockfile"], @@ -89663,7 +89663,7 @@ "display_args": ["--[no-]pydocstyle-skip"], "env_var": "PANTS_PYDOCSTYLE_SKIP", "fromfile": false, - "help": "If true, don't use Pydocstyle when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Pydocstyle when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pydocstyle-skip", "--no-pydocstyle-skip"], @@ -89967,7 +89967,7 @@ "display_args": ["--[no-]pylint-skip"], "env_var": "PANTS_PYLINT_SKIP", "fromfile": false, - "help": "If true, don't use Pylint when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Pylint when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pylint-skip", "--no-pylint-skip"], @@ -90573,7 +90573,7 @@ "display_args": ["--[no-]pytest-skip"], "env_var": "PANTS_PYTEST_SKIP", "fromfile": false, - "help": "If true, don't use Pytest when running `scie-pants-linux-x86_64 test`.", + "help": "If true, don't use Pytest when running `pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pytest-skip", "--no-pytest-skip"], @@ -90749,7 +90749,7 @@ ], "env_var": "PANTS_PYTHON_RESOLVES", "fromfile": false, - "help": "A mapping of logical names to lockfile paths used in your project.\n\nMany organizations only need a single resolve for their whole project, which is a good default and often the simplest thing to do. However, you may need multiple resolves, such as if you use two conflicting versions of a requirement in your repository.\n\nIf you only need a single resolve, run `scie-pants-linux-x86_64 generate-lockfiles` to generate the lockfile.\n\nIf you need multiple resolves:\n\n 1. Via this option, define multiple resolve names and their lockfile paths. The names should be meaningful to your repository, such as `data-science` or `pants-plugins`.\n 2. Set the default with `[python].default_resolve`.\n 3. Update your `python_requirement` targets with the `resolve` field to declare which resolve they should be available in. They default to `[python].default_resolve`, so you only need to update targets that you want in non-default resolves. (Often you'll set this via the `python_requirements` or `poetry_requirements` target generators)\n 4. Run `scie-pants-linux-x86_64 generate-lockfiles` to generate the lockfiles. If the results aren't what you'd expect, adjust the prior step.\n 5. Update any targets like `python_source` / `python_sources`, `python_test` / `python_tests`, and `pex_binary` which need to set a non-default resolve with the `resolve` field.\n\nIf a target can work with multiple resolves, you can either use the `parametrize` mechanism or manually create a distinct target per resolve. See https://www.pantsbuild.org/v2.19/docs/targets for information about `parametrize`.\n\nFor example:\n\n python_sources(\n resolve=parametrize(\"data-science\", \"web-app\"),\n )\n\nYou can name the lockfile paths what you would like; Pants does not expect a certain file extension or location.\n\nOnly applies if `[python].enable_resolves` is true.", + "help": "A mapping of logical names to lockfile paths used in your project.\n\nMany organizations only need a single resolve for their whole project, which is a good default and often the simplest thing to do. However, you may need multiple resolves, such as if you use two conflicting versions of a requirement in your repository.\n\nIf you only need a single resolve, run `pants generate-lockfiles` to generate the lockfile.\n\nIf you need multiple resolves:\n\n 1. Via this option, define multiple resolve names and their lockfile paths. The names should be meaningful to your repository, such as `data-science` or `pants-plugins`.\n 2. Set the default with `[python].default_resolve`.\n 3. Update your `python_requirement` targets with the `resolve` field to declare which resolve they should be available in. They default to `[python].default_resolve`, so you only need to update targets that you want in non-default resolves. (Often you'll set this via the `python_requirements` or `poetry_requirements` target generators)\n 4. Run `pants generate-lockfiles` to generate the lockfiles. If the results aren't what you'd expect, adjust the prior step.\n 5. Update any targets like `python_source` / `python_sources`, `python_test` / `python_tests`, and `pex_binary` which need to set a non-default resolve with the `resolve` field.\n\nIf a target can work with multiple resolves, you can either use the `parametrize` mechanism or manually create a distinct target per resolve. See https://www.pantsbuild.org/v2.19/docs/targets for information about `parametrize`.\n\nFor example:\n\n python_sources(\n resolve=parametrize(\"data-science\", \"web-app\"),\n )\n\nYou can name the lockfile paths what you would like; Pants does not expect a certain file extension or location.\n\nOnly applies if `[python].enable_resolves` is true.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--python-resolves"], @@ -91491,7 +91491,7 @@ "env_var": "PANTS_PYTHON_REQUIREMENT_CONSTRAINTS", "fromfile": false, "help": "When resolving third-party requirements for your own code (vs. tools you run), use this constraints file to determine which versions to use.\n\nMutually exclusive with `[python].enable_resolves`, which we generally recommend as an improvement over constraints file.\n\nSee https://pip.pypa.io/en/stable/user_guide/#constraints-files for more information on the format of constraint files and how constraints are applied in Pex and pip.\n\nThis only applies when resolving user requirements, rather than tools you run like Black and Pytest. To constrain tools, set `[tool].lockfile`, e.g. `[black].lockfile`.", - "removal_hint": "We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.\n\nTo migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `scie-pants-linux-x86_64 generate-lockfiles`.", + "removal_hint": "We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.\n\nTo migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `pants generate-lockfiles`.", "removal_version": "3.0.0.dev0", "scoped_cmd_line_args": ["--python-requirement-constraints"], "target_field_name": null, @@ -91519,7 +91519,7 @@ "env_var": "PANTS_PYTHON_RESOLVE_ALL_CONSTRAINTS", "fromfile": false, "help": "(Only relevant when using `[python].requirement_constraints.`) If enabled, when resolving requirements, Pants will first resolve your entire constraints file as a single global resolve. Then, if the code uses a subset of your constraints file, Pants will extract the relevant requirements from that global resolve so that only what's actually needed gets used. If disabled, Pants will not use a global resolve and will resolve each subset of your requirements independently.\n\nUsually this option should be enabled because it can result in far fewer resolves.", - "removal_hint": "We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.\n\nTo migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `scie-pants-linux-x86_64 generate-lockfiles`.", + "removal_hint": "We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.\n\nTo migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `pants generate-lockfiles`.", "removal_version": "3.0.0.dev0", "scoped_cmd_line_args": [ "--python-resolve-all-constraints", @@ -91949,7 +91949,7 @@ "display_args": ["--python-infer-init-files="], "env_var": "PANTS_PYTHON_INFER_INIT_FILES", "fromfile": false, - "help": "Infer a target's dependencies on any `__init__.py` files in the packages it is located in (recursively upward in the directory structure).\n\nEven if this is set to `never` or `content_only`, Pants will still always include any ancestor `__init__.py` files in the sandbox. Only, they will not be \"proper\" dependencies, e.g. they will not show up in `scie-pants-linux-x86_64 dependencies` and their own dependencies will not be used.\n\nBy default, Pants only adds a \"proper\" dependency if there is content in the `__init__.py` file. This makes sure that dependencies are added when likely necessary to build, while also avoiding adding unnecessary dependencies. While accurate, those unnecessary dependencies can complicate setting metadata like the `interpreter_constraints` and `resolve` fields.", + "help": "Infer a target's dependencies on any `__init__.py` files in the packages it is located in (recursively upward in the directory structure).\n\nEven if this is set to `never` or `content_only`, Pants will still always include any ancestor `__init__.py` files in the sandbox. Only, they will not be \"proper\" dependencies, e.g. they will not show up in `pants dependencies` and their own dependencies will not be used.\n\nBy default, Pants only adds a \"proper\" dependency if there is content in the `__init__.py` file. This makes sure that dependencies are added when likely necessary to build, while also avoiding adding unnecessary dependencies. While accurate, those unnecessary dependencies can complicate setting metadata like the `interpreter_constraints` and `resolve` fields.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--python-infer-init-files"], @@ -92161,7 +92161,7 @@ "display_args": ["--[no-]python-infer-use-rust-parser"], "env_var": "PANTS_PYTHON_INFER_USE_RUST_PARSER", "fromfile": false, - "help": "Use the new Rust-based, multithreaded, in-process dependency parser.\n\nPants 2.17 introduced a new paradigm to dependency parsing for Python by leveraging a Rust-based parser that's called in the same process as Pants itself, instead of farming out to one-python-process-per-file.\n\nAs a result of the switch, cold-cache performance improved by a factor of about 12x, while hot-cache had no difference. Additionally, Pants can now infer dependencies from Python scripts with syntax errors.\n\nAfter leaving this defaulted to disabled for a release cycle, Pants 2.18 started defaulting to enabling this.\n\nIf you think the new behaviour is causing problems, it is recommended that you run `scie-pants-linux-x86_64 peek :: > before.json` and then `scie-pants-linux-x86_64 --python-infer-use-rust-parser=False peek :: > after.json` and compare the two results.\n\nIf you think there is a bug and need to disable it, please file an issue: https://github.com/pantsbuild/pants/issues/new/choose.", + "help": "Use the new Rust-based, multithreaded, in-process dependency parser.\n\nPants 2.17 introduced a new paradigm to dependency parsing for Python by leveraging a Rust-based parser that's called in the same process as Pants itself, instead of farming out to one-python-process-per-file.\n\nAs a result of the switch, cold-cache performance improved by a factor of about 12x, while hot-cache had no difference. Additionally, Pants can now infer dependencies from Python scripts with syntax errors.\n\nAfter leaving this defaulted to disabled for a release cycle, Pants 2.18 started defaulting to enabling this.\n\nIf you think the new behaviour is causing problems, it is recommended that you run `pants peek :: > before.json` and then `pants --python-infer-use-rust-parser=False peek :: > after.json` and compare the two results.\n\nIf you think there is a bug and need to disable it, please file an issue: https://github.com/pantsbuild/pants/issues/new/choose.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -92774,7 +92774,7 @@ "display_args": ["--[no-]pytype-skip"], "env_var": "PANTS_PYTYPE_SKIP", "fromfile": false, - "help": "If true, don't use Pytype when running `scie-pants-linux-x86_64 check`.", + "help": "If true, don't use Pytype when running `pants check`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pytype-skip", "--no-pytype-skip"], @@ -93039,7 +93039,7 @@ "display_args": ["--[no-]pyupgrade-skip"], "env_var": "PANTS_PYUPGRADE_SKIP", "fromfile": false, - "help": "If true, don't use pyupgrade when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use pyupgrade when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pyupgrade-skip", "--no-pyupgrade-skip"], @@ -93118,7 +93118,7 @@ "display_args": ["--[no-]regex-lint-skip"], "env_var": "PANTS_REGEX_LINT_SKIP", "fromfile": false, - "help": "If true, don't use regex-lint when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use regex-lint when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--regex-lint-skip", "--no-regex-lint-skip"], @@ -93638,7 +93638,7 @@ "display_args": ["--[no-]ruff-skip"], "env_var": "PANTS_RUFF_SKIP", "fromfile": false, - "help": "If true, don't use Ruff when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Ruff when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--ruff-skip", "--no-ruff-skip"], @@ -94191,7 +94191,7 @@ "display_args": ["--scalafmt-lockfile="], "env_var": "PANTS_SCALAFMT_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.19.0rc1/src/python/pants/backend/scala/lint/scalafmt/scalafmt.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalafmt`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.19.0rc1/src/python/pants/backend/scala/lint/scalafmt/scalafmt.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=scalafmt`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalafmt-lockfile"], @@ -94261,7 +94261,7 @@ "display_args": ["--[no-]scalafmt-skip"], "env_var": "PANTS_SCALAFMT_SKIP", "fromfile": false, - "help": "If true, don't use scalafmt when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use scalafmt when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalafmt-skip", "--no-scalafmt-skip"], @@ -94370,7 +94370,7 @@ "display_args": ["--scalapb-lockfile="], "env_var": "PANTS_SCALAPB_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.19.0rc1/src/python/pants/backend/codegen/protobuf/scala/scalapbc.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalapb`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.19.0rc1/src/python/pants/backend/codegen/protobuf/scala/scalapbc.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=scalapb`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalapb-lockfile"], @@ -94547,7 +94547,7 @@ "display_args": ["--scalatest-lockfile="], "env_var": "PANTS_SCALATEST_LOCKFILE", "fromfile": false, - "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.19.0rc1/src/python/pants/backend/scala/subsystems/scalatest.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalatest`.", + "help": "Path to a lockfile used for installing the tool.\n\nSet to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.19.0rc1/src/python/pants/backend/scala/subsystems/scalatest.default.lockfile.txt for the default lockfile contents.\n\nTo use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=scalatest`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalatest-lockfile"], @@ -94653,7 +94653,7 @@ "display_args": ["--[no-]scalatest-skip"], "env_var": "PANTS_SCALATEST_SKIP", "fromfile": false, - "help": "If true, don't use Scalatest when running `scie-pants-linux-x86_64 test`.", + "help": "If true, don't use Scalatest when running `pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalatest-skip", "--no-scalatest-skip"], @@ -95162,7 +95162,7 @@ "display_args": ["--[no-]semgrep-skip"], "env_var": "PANTS_SEMGREP_SKIP", "fromfile": false, - "help": "If true, don't use Semgrep when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Semgrep when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--semgrep-skip", "--no-semgrep-skip"], @@ -95658,7 +95658,7 @@ "display_args": ["--[no-]shell-test-skip"], "env_var": "PANTS_SHELL_TEST_SKIP", "fromfile": false, - "help": "If true, don't use Test with shell scripts when running `scie-pants-linux-x86_64 test`.", + "help": "If true, don't use Test with shell scripts when running `pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--shell-test-skip", "--no-shell-test-skip"], @@ -95933,7 +95933,7 @@ "display_args": ["--[no-]shellcheck-skip"], "env_var": "PANTS_SHELLCHECK_SKIP", "fromfile": false, - "help": "If true, don't use Shellcheck when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Shellcheck when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--shellcheck-skip", "--no-shellcheck-skip"], @@ -96251,7 +96251,7 @@ "display_args": ["--[no-]shfmt-skip"], "env_var": "PANTS_SHFMT_SKIP", "fromfile": false, - "help": "If true, don't use shfmt when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use shfmt when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--shfmt-skip", "--no-shfmt-skip"], @@ -96505,7 +96505,7 @@ "display_args": ["--[no-]shunit2-skip"], "env_var": "PANTS_SHUNIT2_SKIP", "fromfile": false, - "help": "If true, don't use shunit2 when running `scie-pants-linux-x86_64 test`.", + "help": "If true, don't use shunit2 when running `pants test`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--shunit2-skip", "--no-shunit2-skip"], @@ -96712,7 +96712,7 @@ "display_args": ["--[no-]spectral-skip"], "env_var": "PANTS_SPECTRAL_SKIP", "fromfile": false, - "help": "If true, don't use Spectral when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Spectral when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--spectral-skip", "--no-spectral-skip"], @@ -97227,7 +97227,7 @@ "display_args": ["--[no-]terraform-fmt-skip"], "env_var": "PANTS_TERRAFORM_FMT_SKIP", "fromfile": false, - "help": "If true, don't use `terraform fmt` when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use `terraform fmt` when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -97389,7 +97389,7 @@ "display_args": ["--[no-]terraform-validate-skip"], "env_var": "PANTS_TERRAFORM_VALIDATE_SKIP", "fromfile": false, - "help": "If true, don't use `terraform validate` when running `scie-pants-linux-x86_64 check`.", + "help": "If true, don't use `terraform validate` when running `pants check`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -98284,7 +98284,7 @@ "display_args": ["--[no-]twine-skip"], "env_var": "PANTS_TWINE_SKIP", "fromfile": false, - "help": "If true, don't use Twine when running `scie-pants-linux-x86_64 publish`.", + "help": "If true, don't use Twine when running `pants publish`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--twine-skip", "--no-twine-skip"], @@ -98900,7 +98900,7 @@ "display_args": ["--[no-]yamllint-skip"], "env_var": "PANTS_YAMLLINT_SKIP", "fromfile": false, - "help": "If true, don't use Yamllint when running `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use Yamllint when running `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--yamllint-skip", "--no-yamllint-skip"], @@ -99169,7 +99169,7 @@ "display_args": ["--[no-]yapf-skip"], "env_var": "PANTS_YAPF_SKIP", "fromfile": false, - "help": "If true, don't use yapf when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`.", + "help": "If true, don't use yapf when running `pants fmt` and `pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--yapf-skip", "--no-yapf-skip"], diff --git a/versioned_docs/version-2.19/reference/subsystems/add-trailing-comma.mdx b/versioned_docs/version-2.19/reference/subsystems/add-trailing-comma.mdx index 028c26962..60a22889a 100644 --- a/versioned_docs/version-2.19/reference/subsystems/add-trailing-comma.mdx +++ b/versioned_docs/version-2.19/reference/subsystems/add-trailing-comma.mdx @@ -25,7 +25,7 @@ Config section: `[add-trailing-comma]` default_repr={`False`} > -If true, don't use add-trailing-comma when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use add-trailing-comma when running `pants fmt` and `pants lint`. diff --git a/versioned_docs/version-2.19/reference/subsystems/autoflake.mdx b/versioned_docs/version-2.19/reference/subsystems/autoflake.mdx index b23f25859..09b652507 100644 --- a/versioned_docs/version-2.19/reference/subsystems/autoflake.mdx +++ b/versioned_docs/version-2.19/reference/subsystems/autoflake.mdx @@ -25,7 +25,7 @@ Config section: `[autoflake]` default_repr={`False`} > -If true, don't use Autoflake when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use Autoflake when running `pants fmt` and `pants lint`. diff --git a/versioned_docs/version-2.19/reference/subsystems/bandit.mdx b/versioned_docs/version-2.19/reference/subsystems/bandit.mdx index 5778952f2..73cf3b1c7 100644 --- a/versioned_docs/version-2.19/reference/subsystems/bandit.mdx +++ b/versioned_docs/version-2.19/reference/subsystems/bandit.mdx @@ -25,7 +25,7 @@ Config section: `[bandit]` default_repr={`False`} > -If true, don't use Bandit when running `scie-pants-linux-x86_64 lint`. +If true, don't use Bandit when running `pants lint`. diff --git a/versioned_docs/version-2.19/reference/subsystems/black.mdx b/versioned_docs/version-2.19/reference/subsystems/black.mdx index 88911c026..f5f5d4a64 100644 --- a/versioned_docs/version-2.19/reference/subsystems/black.mdx +++ b/versioned_docs/version-2.19/reference/subsystems/black.mdx @@ -25,7 +25,7 @@ Config section: `[black]` default_repr={`False`} > -If true, don't use Black when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use Black when running `pants fmt` and `pants lint`. diff --git a/versioned_docs/version-2.19/reference/subsystems/buf.mdx b/versioned_docs/version-2.19/reference/subsystems/buf.mdx index 77c974eb0..67a53f3e7 100644 --- a/versioned_docs/version-2.19/reference/subsystems/buf.mdx +++ b/versioned_docs/version-2.19/reference/subsystems/buf.mdx @@ -25,7 +25,7 @@ Config section: `[buf]` default_repr={`False`} > -If true, don't use Buf when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use Buf when running `pants fmt` and `pants lint`. @@ -37,7 +37,7 @@ If true, don't use Buf when running `scie-pants-linux-x86_64 fmt` and `scie default_repr={`False`} > -If true, don't use Buf when running `scie-pants-linux-x86_64 lint`. +If true, don't use Buf when running `pants lint`. diff --git a/versioned_docs/version-2.19/reference/subsystems/build-deprecations-fixer.mdx b/versioned_docs/version-2.19/reference/subsystems/build-deprecations-fixer.mdx index 7f54c6e7f..663dbb00f 100644 --- a/versioned_docs/version-2.19/reference/subsystems/build-deprecations-fixer.mdx +++ b/versioned_docs/version-2.19/reference/subsystems/build-deprecations-fixer.mdx @@ -30,7 +30,7 @@ Config section: `[build-deprecations-fixer]` -If true, don't use BUILD Deprecations Fixer when running `scie-pants-linux-x86_64 fix`. +If true, don't use BUILD Deprecations Fixer when running `pants fix`. diff --git a/versioned_docs/version-2.19/reference/subsystems/buildifier.mdx b/versioned_docs/version-2.19/reference/subsystems/buildifier.mdx index 02a6ad711..9b2c2b77e 100644 --- a/versioned_docs/version-2.19/reference/subsystems/buildifier.mdx +++ b/versioned_docs/version-2.19/reference/subsystems/buildifier.mdx @@ -32,7 +32,7 @@ Config section: `[buildifier]` default_repr={`False`} > -If true, don't use Buildifier when running `scie-pants-linux-x86_64 fmt`. +If true, don't use Buildifier when running `pants fmt`. diff --git a/versioned_docs/version-2.19/reference/subsystems/cli.mdx b/versioned_docs/version-2.19/reference/subsystems/cli.mdx index c73472624..e471cf70f 100644 --- a/versioned_docs/version-2.19/reference/subsystems/cli.mdx +++ b/versioned_docs/version-2.19/reference/subsystems/cli.mdx @@ -35,7 +35,7 @@ green = "fmt lint check" all-changed = "--changed-since=HEAD --changed-dependents=transitive" ``` -This would allow you to run `scie-pants-linux-x86_64 green all-changed`, which is shorthand for `scie-pants-linux-x86_64 fmt lint check --changed-since=HEAD --changed-dependents=transitive`. +This would allow you to run `pants green all-changed`, which is shorthand for `pants fmt lint check --changed-since=HEAD --changed-dependents=transitive`. Notice: this option must be placed in a config file (e.g. `pants.toml` or `pantsrc`) to have any effect. diff --git a/versioned_docs/version-2.19/reference/subsystems/docformatter.mdx b/versioned_docs/version-2.19/reference/subsystems/docformatter.mdx index fd47891e1..073f20b15 100644 --- a/versioned_docs/version-2.19/reference/subsystems/docformatter.mdx +++ b/versioned_docs/version-2.19/reference/subsystems/docformatter.mdx @@ -25,7 +25,7 @@ Config section: `[docformatter]` default_repr={`False`} > -If true, don't use docformatter when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use docformatter when running `pants fmt` and `pants lint`. diff --git a/versioned_docs/version-2.19/reference/subsystems/docker.mdx b/versioned_docs/version-2.19/reference/subsystems/docker.mdx index 481ccffbb..8a3d63bdc 100644 --- a/versioned_docs/version-2.19/reference/subsystems/docker.mdx +++ b/versioned_docs/version-2.19/reference/subsystems/docker.mdx @@ -214,7 +214,7 @@ Additional arguments to use for `docker run` invocations. Example: ``` -$ scie-pants-linux-x86_64 run --docker-run-args="-p 127.0.0.1:80:8080/tcp --name demo" src/example:image -- [image entrypoint args] +$ pants run --docker-run-args="-p 127.0.0.1:80:8080/tcp --name demo" src/example:image -- [image entrypoint args] ``` To provide the top-level options to the `docker` client, use `[docker].env_vars` to configure the [Environment variables](https://docs.docker.com/engine/reference/commandline/cli/#environment-variables) as appropriate. diff --git a/versioned_docs/version-2.19/reference/subsystems/flake8.mdx b/versioned_docs/version-2.19/reference/subsystems/flake8.mdx index 04ad56f8f..a4ccde107 100644 --- a/versioned_docs/version-2.19/reference/subsystems/flake8.mdx +++ b/versioned_docs/version-2.19/reference/subsystems/flake8.mdx @@ -25,7 +25,7 @@ Config section: `[flake8]` default_repr={`False`} > -If true, don't use Flake8 when running `scie-pants-linux-x86_64 lint`. +If true, don't use Flake8 when running `pants lint`. diff --git a/versioned_docs/version-2.19/reference/subsystems/go-test.mdx b/versioned_docs/version-2.19/reference/subsystems/go-test.mdx index f3fd9afb4..125a6e1b5 100644 --- a/versioned_docs/version-2.19/reference/subsystems/go-test.mdx +++ b/versioned_docs/version-2.19/reference/subsystems/go-test.mdx @@ -88,7 +88,7 @@ This option is similar to the `go test -coverpkg` option, but without support cu default_repr={`False`} > -If true, don't use Go test binary when running `scie-pants-linux-x86_64 test`. +If true, don't use Go test binary when running `pants test`. diff --git a/versioned_docs/version-2.19/reference/subsystems/gofmt.mdx b/versioned_docs/version-2.19/reference/subsystems/gofmt.mdx index 0e737213e..b4fad02eb 100644 --- a/versioned_docs/version-2.19/reference/subsystems/gofmt.mdx +++ b/versioned_docs/version-2.19/reference/subsystems/gofmt.mdx @@ -25,7 +25,7 @@ Config section: `[gofmt]` default_repr={`False`} > -If true, don't use gofmt when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use gofmt when running `pants fmt` and `pants lint`. diff --git a/versioned_docs/version-2.19/reference/subsystems/google-java-format.mdx b/versioned_docs/version-2.19/reference/subsystems/google-java-format.mdx index a64bf6f41..628134ce1 100644 --- a/versioned_docs/version-2.19/reference/subsystems/google-java-format.mdx +++ b/versioned_docs/version-2.19/reference/subsystems/google-java-format.mdx @@ -25,7 +25,7 @@ Config section: `[google-java-format]` default_repr={`False`} > -If true, don't use Google Java Format when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use Google Java Format when running `pants fmt` and `pants lint`. @@ -79,7 +79,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.19.0rc1/src/python/pants/backend/java/lint/google_java_format/google_java_format.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=google-java-format`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=google-java-format`. diff --git a/versioned_docs/version-2.19/reference/subsystems/hadolint.mdx b/versioned_docs/version-2.19/reference/subsystems/hadolint.mdx index 4ff6f0350..f33a09795 100644 --- a/versioned_docs/version-2.19/reference/subsystems/hadolint.mdx +++ b/versioned_docs/version-2.19/reference/subsystems/hadolint.mdx @@ -25,7 +25,7 @@ Config section: `[hadolint]` default_repr={`False`} > -If true, don't use Hadolint when running `scie-pants-linux-x86_64 lint`. +If true, don't use Hadolint when running `pants lint`. diff --git a/versioned_docs/version-2.19/reference/subsystems/helm-unittest.mdx b/versioned_docs/version-2.19/reference/subsystems/helm-unittest.mdx index 87b8b718e..27a6d8e70 100644 --- a/versioned_docs/version-2.19/reference/subsystems/helm-unittest.mdx +++ b/versioned_docs/version-2.19/reference/subsystems/helm-unittest.mdx @@ -50,7 +50,7 @@ Output type used for the test report. default_repr={`False`} > -If true, don't use helmunittestsubsystem when running `scie-pants-linux-x86_64 test`. +If true, don't use helmunittestsubsystem when running `pants test`. diff --git a/versioned_docs/version-2.19/reference/subsystems/isort.mdx b/versioned_docs/version-2.19/reference/subsystems/isort.mdx index 595e63787..bed5eea3e 100644 --- a/versioned_docs/version-2.19/reference/subsystems/isort.mdx +++ b/versioned_docs/version-2.19/reference/subsystems/isort.mdx @@ -25,7 +25,7 @@ Config section: `[isort]` default_repr={`False`} > -If true, don't use isort when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use isort when running `pants fmt` and `pants lint`. diff --git a/versioned_docs/version-2.19/reference/subsystems/jarjar.mdx b/versioned_docs/version-2.19/reference/subsystems/jarjar.mdx index 0dd80a2f6..f0d087c36 100644 --- a/versioned_docs/version-2.19/reference/subsystems/jarjar.mdx +++ b/versioned_docs/version-2.19/reference/subsystems/jarjar.mdx @@ -80,7 +80,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.19.0rc1/src/python/pants/jvm/shading/jarjar.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=jarjar`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=jarjar`. diff --git a/versioned_docs/version-2.19/reference/subsystems/junit.mdx b/versioned_docs/version-2.19/reference/subsystems/junit.mdx index edfe638ea..e5b19f34f 100644 --- a/versioned_docs/version-2.19/reference/subsystems/junit.mdx +++ b/versioned_docs/version-2.19/reference/subsystems/junit.mdx @@ -37,7 +37,7 @@ Arguments to pass directly to JUnit, e.g. `--junit-args='--disable-ansi-colors'` default_repr={`False`} > -If true, don't use JUnit when running `scie-pants-linux-x86_64 test`. +If true, don't use JUnit when running `pants test`. @@ -79,7 +79,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.19.0rc1/src/python/pants/jvm/test/junit.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=junit`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=junit`. diff --git a/versioned_docs/version-2.19/reference/subsystems/ktlint.mdx b/versioned_docs/version-2.19/reference/subsystems/ktlint.mdx index e40d7479f..ea83b5d63 100644 --- a/versioned_docs/version-2.19/reference/subsystems/ktlint.mdx +++ b/versioned_docs/version-2.19/reference/subsystems/ktlint.mdx @@ -25,7 +25,7 @@ Config section: `[ktlint]` default_repr={`False`} > -If true, don't use Ktlint when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use Ktlint when running `pants fmt` and `pants lint`. @@ -67,7 +67,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.19.0rc1/src/python/pants/backend/kotlin/lint/ktlint/ktlint.lock for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=ktlint`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=ktlint`. diff --git a/versioned_docs/version-2.19/reference/subsystems/mypy.mdx b/versioned_docs/version-2.19/reference/subsystems/mypy.mdx index 351ae7caf..5c7568a1d 100644 --- a/versioned_docs/version-2.19/reference/subsystems/mypy.mdx +++ b/versioned_docs/version-2.19/reference/subsystems/mypy.mdx @@ -25,7 +25,7 @@ Config section: `[mypy]` default_repr={`False`} > -If true, don't use MyPy when running `scie-pants-linux-x86_64 check`. +If true, don't use MyPy when running `pants check`. diff --git a/versioned_docs/version-2.19/reference/subsystems/nodejs.mdx b/versioned_docs/version-2.19/reference/subsystems/nodejs.mdx index f3177d48d..76f2fa08d 100644 --- a/versioned_docs/version-2.19/reference/subsystems/nodejs.mdx +++ b/versioned_docs/version-2.19/reference/subsystems/nodejs.mdx @@ -136,7 +136,7 @@ Specifying a resolve name is optional. If unspecified, the default resolve name Example: An npm lockfile located at `src/js/package/package-lock.json' will result in a resolve named `js.package`, assuming src/ is a source root. -Run `scie-pants-linux-x86_64 generate-lockfiles` to generate the lockfile(s). +Run `pants generate-lockfiles` to generate the lockfile(s). diff --git a/versioned_docs/version-2.19/reference/subsystems/openapi-format.mdx b/versioned_docs/version-2.19/reference/subsystems/openapi-format.mdx index c06a7671e..391e62527 100644 --- a/versioned_docs/version-2.19/reference/subsystems/openapi-format.mdx +++ b/versioned_docs/version-2.19/reference/subsystems/openapi-format.mdx @@ -25,7 +25,7 @@ Config section: `[openapi-format]` default_repr={`False`} > -If true, don't use openapi-format when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use openapi-format when running `pants fmt` and `pants lint`. diff --git a/versioned_docs/version-2.19/reference/subsystems/preamble.mdx b/versioned_docs/version-2.19/reference/subsystems/preamble.mdx index 8577e4ba8..27fb5eb3f 100644 --- a/versioned_docs/version-2.19/reference/subsystems/preamble.mdx +++ b/versioned_docs/version-2.19/reference/subsystems/preamble.mdx @@ -29,7 +29,7 @@ Config section: `[preamble]` default_repr={`False`} > -If true, don't use preamble when running `scie-pants-linux-x86_64 fmt`. +If true, don't use preamble when running `pants fmt`. diff --git a/versioned_docs/version-2.19/reference/subsystems/protobuf-java-grpc.mdx b/versioned_docs/version-2.19/reference/subsystems/protobuf-java-grpc.mdx index bdf959370..8f0d3c323 100644 --- a/versioned_docs/version-2.19/reference/subsystems/protobuf-java-grpc.mdx +++ b/versioned_docs/version-2.19/reference/subsystems/protobuf-java-grpc.mdx @@ -57,7 +57,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.19.0rc1/src/python/pants/backend/codegen/protobuf/java/grpc-java.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=protobuf-java-grpc`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=protobuf-java-grpc`. diff --git a/versioned_docs/version-2.19/reference/subsystems/pydocstyle.mdx b/versioned_docs/version-2.19/reference/subsystems/pydocstyle.mdx index dae7a5d28..415d9cbc2 100644 --- a/versioned_docs/version-2.19/reference/subsystems/pydocstyle.mdx +++ b/versioned_docs/version-2.19/reference/subsystems/pydocstyle.mdx @@ -25,7 +25,7 @@ Config section: `[pydocstyle]` default_repr={`False`} > -If true, don't use Pydocstyle when running `scie-pants-linux-x86_64 lint`. +If true, don't use Pydocstyle when running `pants lint`. diff --git a/versioned_docs/version-2.19/reference/subsystems/pylint.mdx b/versioned_docs/version-2.19/reference/subsystems/pylint.mdx index 43d332c23..620299c10 100644 --- a/versioned_docs/version-2.19/reference/subsystems/pylint.mdx +++ b/versioned_docs/version-2.19/reference/subsystems/pylint.mdx @@ -25,7 +25,7 @@ Config section: `[pylint]` default_repr={`False`} > -If true, don't use Pylint when running `scie-pants-linux-x86_64 lint`. +If true, don't use Pylint when running `pants lint`. diff --git a/versioned_docs/version-2.19/reference/subsystems/pytest.mdx b/versioned_docs/version-2.19/reference/subsystems/pytest.mdx index 557946b0f..02d2e990f 100644 --- a/versioned_docs/version-2.19/reference/subsystems/pytest.mdx +++ b/versioned_docs/version-2.19/reference/subsystems/pytest.mdx @@ -51,7 +51,7 @@ NOTE: Enabling `pytest-xdist` can cause high-level scoped fixtures (for example default_repr={`False`} > -If true, don't use Pytest when running `scie-pants-linux-x86_64 test`. +If true, don't use Pytest when running `pants test`. diff --git a/versioned_docs/version-2.19/reference/subsystems/python-infer.mdx b/versioned_docs/version-2.19/reference/subsystems/python-infer.mdx index a26783884..21d901feb 100644 --- a/versioned_docs/version-2.19/reference/subsystems/python-infer.mdx +++ b/versioned_docs/version-2.19/reference/subsystems/python-infer.mdx @@ -94,7 +94,7 @@ If `--assets` is True, treat valid-looking strings with at least this many forwa Infer a target's dependencies on any `__init__.py` files in the packages it is located in (recursively upward in the directory structure). -Even if this is set to `never` or `content_only`, Pants will still always include any ancestor `__init__.py` files in the sandbox. Only, they will not be "proper" dependencies, e.g. they will not show up in `scie-pants-linux-x86_64 dependencies` and their own dependencies will not be used. +Even if this is set to `never` or `content_only`, Pants will still always include any ancestor `__init__.py` files in the sandbox. Only, they will not be "proper" dependencies, e.g. they will not show up in `pants dependencies` and their own dependencies will not be used. By default, Pants only adds a "proper" dependency if there is content in the `__init__.py` file. This makes sure that dependencies are added when likely necessary to build, while also avoiding adding unnecessary dependencies. While accurate, those unnecessary dependencies can complicate setting metadata like the `interpreter_constraints` and `resolve` fields. @@ -199,7 +199,7 @@ As a result of the switch, cold-cache performance improved by a factor of about After leaving this defaulted to disabled for a release cycle, Pants 2.18 started defaulting to enabling this. -If you think the new behaviour is causing problems, it is recommended that you run `scie-pants-linux-x86_64 peek :: > before.json` and then `scie-pants-linux-x86_64 --python-infer-use-rust-parser=False peek :: > after.json` and compare the two results. +If you think the new behaviour is causing problems, it is recommended that you run `pants peek :: > before.json` and then `pants --python-infer-use-rust-parser=False peek :: > after.json` and compare the two results. If you think there is a bug and need to disable it, please file an issue: https://github.com/pantsbuild/pants/issues/new/choose. diff --git a/versioned_docs/version-2.19/reference/subsystems/python.mdx b/versioned_docs/version-2.19/reference/subsystems/python.mdx index 118327894..c7d892f53 100644 --- a/versioned_docs/version-2.19/reference/subsystems/python.mdx +++ b/versioned_docs/version-2.19/reference/subsystems/python.mdx @@ -107,14 +107,14 @@ A mapping of logical names to lockfile paths used in your project. Many organizations only need a single resolve for their whole project, which is a good default and often the simplest thing to do. However, you may need multiple resolves, such as if you use two conflicting versions of a requirement in your repository. -If you only need a single resolve, run `scie-pants-linux-x86_64 generate-lockfiles` to generate the lockfile. +If you only need a single resolve, run `pants generate-lockfiles` to generate the lockfile. If you need multiple resolves: 1. Via this option, define multiple resolve names and their lockfile paths. The names should be meaningful to your repository, such as `data-science` or `pants-plugins`. 2. Set the default with `[python].default_resolve`. 3. Update your `python_requirement` targets with the `resolve` field to declare which resolve they should be available in. They default to `[python].default_resolve`, so you only need to update targets that you want in non-default resolves. (Often you'll set this via the `python_requirements` or `poetry_requirements` target generators) -4. Run `scie-pants-linux-x86_64 generate-lockfiles` to generate the lockfiles. If the results aren't what you'd expect, adjust the prior step. +4. Run `pants generate-lockfiles` to generate the lockfiles. If the results aren't what you'd expect, adjust the prior step. 5. Update any targets like `python_source` / `python_sources`, `python_test` / `python_tests`, and `pex_binary` which need to set a non-default resolve with the `resolve` field. If a target can work with multiple resolves, you can either use the `parametrize` mechanism or manually create a distinct target per resolve. See https://www.pantsbuild.org/v2.19/docs/targets for information about `parametrize`. @@ -417,7 +417,7 @@ If another targets address is in conflict with the created lockfile target, it w env_repr='PANTS_PYTHON_REQUIREMENT_CONSTRAINTS' default_repr={`None`} removal_version='3.0.0.dev0' - removal_hint={'We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.

To migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `scie-pants-linux-x86_64 generate-lockfiles`.'} + removal_hint={'We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.

To migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `pants generate-lockfiles`.'} > When resolving third-party requirements for your own code (vs. tools you run), use this constraints file to determine which versions to use. @@ -437,7 +437,7 @@ This only applies when resolving user requirements, rather than tools you run li env_repr='PANTS_PYTHON_RESOLVE_ALL_CONSTRAINTS' default_repr={`True`} removal_version='3.0.0.dev0' - removal_hint={'We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.

To migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `scie-pants-linux-x86_64 generate-lockfiles`.'} + removal_hint={'We encourage instead migrating to `[python].enable_resolves` and `[python].resolves`, which is an improvement over this option. The `[python].resolves` feature ensures that your lockfiles are fully comprehensive, i.e. include all transitive dependencies; uses hashes for better supply chain security; and supports advanced features like VCS and local requirements, along with options `[python].resolves_to_only_binary`.

To migrate, stop setting `[python].requirement_constraints` and `[python].resolve_all_constraints`, and instead set `[python].enable_resolves` to `true`. Then, run `pants generate-lockfiles`.'} > (Only relevant when using `[python].requirement_constraints.`) If enabled, when resolving requirements, Pants will first resolve your entire constraints file as a single global resolve. Then, if the code uses a subset of your constraints file, Pants will extract the relevant requirements from that global resolve so that only what's actually needed gets used. If disabled, Pants will not use a global resolve and will resolve each subset of your requirements independently. diff --git a/versioned_docs/version-2.19/reference/subsystems/pytype.mdx b/versioned_docs/version-2.19/reference/subsystems/pytype.mdx index 581fa08eb..677e0454c 100644 --- a/versioned_docs/version-2.19/reference/subsystems/pytype.mdx +++ b/versioned_docs/version-2.19/reference/subsystems/pytype.mdx @@ -25,7 +25,7 @@ Config section: `[pytype]` default_repr={`False`} > -If true, don't use Pytype when running `scie-pants-linux-x86_64 check`. +If true, don't use Pytype when running `pants check`. diff --git a/versioned_docs/version-2.19/reference/subsystems/pyupgrade.mdx b/versioned_docs/version-2.19/reference/subsystems/pyupgrade.mdx index aeaa98a19..523051507 100644 --- a/versioned_docs/version-2.19/reference/subsystems/pyupgrade.mdx +++ b/versioned_docs/version-2.19/reference/subsystems/pyupgrade.mdx @@ -25,7 +25,7 @@ Config section: `[pyupgrade]` default_repr={`False`} > -If true, don't use pyupgrade when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use pyupgrade when running `pants fmt` and `pants lint`. diff --git a/versioned_docs/version-2.19/reference/subsystems/regex-lint.mdx b/versioned_docs/version-2.19/reference/subsystems/regex-lint.mdx index a919e6ff4..20d8d1542 100644 --- a/versioned_docs/version-2.19/reference/subsystems/regex-lint.mdx +++ b/versioned_docs/version-2.19/reference/subsystems/regex-lint.mdx @@ -29,7 +29,7 @@ Config section: `[regex-lint]` default_repr={`False`} > -If true, don't use regex-lint when running `scie-pants-linux-x86_64 lint`. +If true, don't use regex-lint when running `pants lint`. diff --git a/versioned_docs/version-2.19/reference/subsystems/ruff.mdx b/versioned_docs/version-2.19/reference/subsystems/ruff.mdx index 28d8fee73..71037f9d8 100644 --- a/versioned_docs/version-2.19/reference/subsystems/ruff.mdx +++ b/versioned_docs/version-2.19/reference/subsystems/ruff.mdx @@ -25,7 +25,7 @@ Config section: `[ruff]` default_repr={`False`} > -If true, don't use Ruff when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use Ruff when running `pants fmt` and `pants lint`. diff --git a/versioned_docs/version-2.19/reference/subsystems/scalafmt.mdx b/versioned_docs/version-2.19/reference/subsystems/scalafmt.mdx index c4fe75bb7..e2d1bc1bd 100644 --- a/versioned_docs/version-2.19/reference/subsystems/scalafmt.mdx +++ b/versioned_docs/version-2.19/reference/subsystems/scalafmt.mdx @@ -25,7 +25,7 @@ Config section: `[scalafmt]` default_repr={`False`} > -If true, don't use scalafmt when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use scalafmt when running `pants fmt` and `pants lint`. @@ -67,7 +67,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.19.0rc1/src/python/pants/backend/scala/lint/scalafmt/scalafmt.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalafmt`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=scalafmt`. diff --git a/versioned_docs/version-2.19/reference/subsystems/scalapb.mdx b/versioned_docs/version-2.19/reference/subsystems/scalapb.mdx index a5aff7009..1951a9a3e 100644 --- a/versioned_docs/version-2.19/reference/subsystems/scalapb.mdx +++ b/versioned_docs/version-2.19/reference/subsystems/scalapb.mdx @@ -69,7 +69,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.19.0rc1/src/python/pants/backend/codegen/protobuf/scala/scalapbc.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalapb`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=scalapb`. diff --git a/versioned_docs/version-2.19/reference/subsystems/scalatest.mdx b/versioned_docs/version-2.19/reference/subsystems/scalatest.mdx index 5a794385f..933ba8771 100644 --- a/versioned_docs/version-2.19/reference/subsystems/scalatest.mdx +++ b/versioned_docs/version-2.19/reference/subsystems/scalatest.mdx @@ -39,7 +39,7 @@ See https://www.scalatest.org/user_guide/using_the_runner for supported argument default_repr={`False`} > -If true, don't use Scalatest when running `scie-pants-linux-x86_64 test`. +If true, don't use Scalatest when running `pants test`. @@ -81,7 +81,7 @@ Path to a lockfile used for installing the tool. Set to the string `` to use a lockfile provided by Pants, so long as you have not changed the `--version` option. See https://github.com/pantsbuild/pants/blob/release_2.19.0rc1/src/python/pants/backend/scala/subsystems/scalatest.default.lockfile.txt for the default lockfile contents. -To use a custom lockfile, set this option to a file path relative to the build root, then run `scie-pants-linux-x86_64 jvm-generate-lockfiles --resolve=scalatest`. +To use a custom lockfile, set this option to a file path relative to the build root, then run `pants jvm-generate-lockfiles --resolve=scalatest`. diff --git a/versioned_docs/version-2.19/reference/subsystems/semgrep.mdx b/versioned_docs/version-2.19/reference/subsystems/semgrep.mdx index b8242ca4c..8dec94a02 100644 --- a/versioned_docs/version-2.19/reference/subsystems/semgrep.mdx +++ b/versioned_docs/version-2.19/reference/subsystems/semgrep.mdx @@ -41,7 +41,7 @@ This includes --quiet by default to reduce the volume of output. default_repr={`False`} > -If true, don't use Semgrep when running `scie-pants-linux-x86_64 lint`. +If true, don't use Semgrep when running `pants lint`. diff --git a/versioned_docs/version-2.19/reference/subsystems/shell-test.mdx b/versioned_docs/version-2.19/reference/subsystems/shell-test.mdx index 3c748d702..1a371c907 100644 --- a/versioned_docs/version-2.19/reference/subsystems/shell-test.mdx +++ b/versioned_docs/version-2.19/reference/subsystems/shell-test.mdx @@ -25,7 +25,7 @@ Config section: `[shell-test]` default_repr={`False`} > -If true, don't use Test with shell scripts when running `scie-pants-linux-x86_64 test`. +If true, don't use Test with shell scripts when running `pants test`. diff --git a/versioned_docs/version-2.19/reference/subsystems/shellcheck.mdx b/versioned_docs/version-2.19/reference/subsystems/shellcheck.mdx index c211a95b8..bff16b0ee 100644 --- a/versioned_docs/version-2.19/reference/subsystems/shellcheck.mdx +++ b/versioned_docs/version-2.19/reference/subsystems/shellcheck.mdx @@ -25,7 +25,7 @@ Config section: `[shellcheck]` default_repr={`False`} > -If true, don't use Shellcheck when running `scie-pants-linux-x86_64 lint`. +If true, don't use Shellcheck when running `pants lint`. diff --git a/versioned_docs/version-2.19/reference/subsystems/shfmt.mdx b/versioned_docs/version-2.19/reference/subsystems/shfmt.mdx index 248a33fc3..0505e5a19 100644 --- a/versioned_docs/version-2.19/reference/subsystems/shfmt.mdx +++ b/versioned_docs/version-2.19/reference/subsystems/shfmt.mdx @@ -25,7 +25,7 @@ Config section: `[shfmt]` default_repr={`False`} > -If true, don't use shfmt when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use shfmt when running `pants fmt` and `pants lint`. diff --git a/versioned_docs/version-2.19/reference/subsystems/shunit2.mdx b/versioned_docs/version-2.19/reference/subsystems/shunit2.mdx index 8abbec50a..ec281e121 100644 --- a/versioned_docs/version-2.19/reference/subsystems/shunit2.mdx +++ b/versioned_docs/version-2.19/reference/subsystems/shunit2.mdx @@ -25,7 +25,7 @@ Config section: `[shunit2]` default_repr={`False`} > -If true, don't use shunit2 when running `scie-pants-linux-x86_64 test`. +If true, don't use shunit2 when running `pants test`. diff --git a/versioned_docs/version-2.19/reference/subsystems/spectral.mdx b/versioned_docs/version-2.19/reference/subsystems/spectral.mdx index 2f9588306..a5ab244bd 100644 --- a/versioned_docs/version-2.19/reference/subsystems/spectral.mdx +++ b/versioned_docs/version-2.19/reference/subsystems/spectral.mdx @@ -25,7 +25,7 @@ Config section: `[spectral]` default_repr={`False`} > -If true, don't use Spectral when running `scie-pants-linux-x86_64 lint`. +If true, don't use Spectral when running `pants lint`. diff --git a/versioned_docs/version-2.19/reference/subsystems/terraform-fmt.mdx b/versioned_docs/version-2.19/reference/subsystems/terraform-fmt.mdx index 968e542ad..c675ed16b 100644 --- a/versioned_docs/version-2.19/reference/subsystems/terraform-fmt.mdx +++ b/versioned_docs/version-2.19/reference/subsystems/terraform-fmt.mdx @@ -25,7 +25,7 @@ Config section: `[terraform-fmt]` default_repr={`False`} > -If true, don't use `terraform fmt` when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use `terraform fmt` when running `pants fmt` and `pants lint`. diff --git a/versioned_docs/version-2.19/reference/subsystems/terraform-validate.mdx b/versioned_docs/version-2.19/reference/subsystems/terraform-validate.mdx index a84bf5b6c..e7686bc2f 100644 --- a/versioned_docs/version-2.19/reference/subsystems/terraform-validate.mdx +++ b/versioned_docs/version-2.19/reference/subsystems/terraform-validate.mdx @@ -25,7 +25,7 @@ Config section: `[terraform-validate]` default_repr={`False`} > -If true, don't use `terraform validate` when running `scie-pants-linux-x86_64 check`. +If true, don't use `terraform validate` when running `pants check`. diff --git a/versioned_docs/version-2.19/reference/subsystems/twine.mdx b/versioned_docs/version-2.19/reference/subsystems/twine.mdx index 5f3b625ff..3cb9d71a5 100644 --- a/versioned_docs/version-2.19/reference/subsystems/twine.mdx +++ b/versioned_docs/version-2.19/reference/subsystems/twine.mdx @@ -25,7 +25,7 @@ Config section: `[twine]` default_repr={`False`} > -If true, don't use Twine when running `scie-pants-linux-x86_64 publish`. +If true, don't use Twine when running `pants publish`. diff --git a/versioned_docs/version-2.19/reference/subsystems/yamllint.mdx b/versioned_docs/version-2.19/reference/subsystems/yamllint.mdx index 88afe19cc..9c55f2b99 100644 --- a/versioned_docs/version-2.19/reference/subsystems/yamllint.mdx +++ b/versioned_docs/version-2.19/reference/subsystems/yamllint.mdx @@ -61,7 +61,7 @@ Arguments to pass directly to Yamllint, e.g. `--yamllint-args='-d relaxed'`. default_repr={`False`} > -If true, don't use Yamllint when running `scie-pants-linux-x86_64 lint`. +If true, don't use Yamllint when running `pants lint`. diff --git a/versioned_docs/version-2.19/reference/subsystems/yapf.mdx b/versioned_docs/version-2.19/reference/subsystems/yapf.mdx index 8d3ad634e..80ce3cf22 100644 --- a/versioned_docs/version-2.19/reference/subsystems/yapf.mdx +++ b/versioned_docs/version-2.19/reference/subsystems/yapf.mdx @@ -25,7 +25,7 @@ Config section: `[yapf]` default_repr={`False`} > -If true, don't use yapf when running `scie-pants-linux-x86_64 fmt` and `scie-pants-linux-x86_64 lint`. +If true, don't use yapf when running `pants fmt` and `pants lint`. diff --git a/versioned_docs/version-2.19/reference/targets/adhoc_tool.mdx b/versioned_docs/version-2.19/reference/targets/adhoc_tool.mdx index 4378a4583..985e36caa 100644 --- a/versioned_docs/version-2.19/reference/targets/adhoc_tool.mdx +++ b/versioned_docs/version-2.19/reference/targets/adhoc_tool.mdx @@ -38,7 +38,7 @@ Backend: `pants.backend.experimental.adhoc` @@ -51,7 +51,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.19/reference/targets/archive.mdx b/versioned_docs/version-2.19/reference/targets/archive.mdx index c0c9b9ef7..b3f69629d 100644 --- a/versioned_docs/version-2.19/reference/targets/archive.mdx +++ b/versioned_docs/version-2.19/reference/targets/archive.mdx @@ -24,7 +24,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -52,7 +52,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. @@ -65,11 +65,11 @@ Warning: setting this value risks naming collisions with other package targets y default_repr={`None`} > -Addresses to any targets that can be built with `scie-pants-linux-x86_64 package`, e.g. `["project:app"]`. +Addresses to any targets that can be built with `pants package`, e.g. `["project:app"]`. -Pants will build the assets as if you had run `scie-pants-linux-x86_64 package`. It will include the results in your archive using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). +Pants will build the assets as if you had run `pants package`. It will include the results in your archive using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). -You can include anything that can be built by `scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_awslambda`, or even another `archive`. +You can include anything that can be built by `pants package`, e.g. a `pex_binary`, `python_awslambda`, or even another `archive`. diff --git a/versioned_docs/version-2.19/reference/targets/deploy_jar.mdx b/versioned_docs/version-2.19/reference/targets/deploy_jar.mdx index 9a0c71d59..6079abf19 100644 --- a/versioned_docs/version-2.19/reference/targets/deploy_jar.mdx +++ b/versioned_docs/version-2.19/reference/targets/deploy_jar.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.experimental.java` @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -65,7 +65,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. @@ -80,9 +80,9 @@ Warning: setting this value risks naming collisions with other package targets y Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.19/reference/targets/docker_environment.mdx b/versioned_docs/version-2.19/reference/targets/docker_environment.mdx index fb5d66866..8374a72e4 100644 --- a/versioned_docs/version-2.19/reference/targets/docker_environment.mdx +++ b/versioned_docs/version-2.19/reference/targets/docker_environment.mdx @@ -30,7 +30,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.19/reference/targets/docker_image.mdx b/versioned_docs/version-2.19/reference/targets/docker_image.mdx index 0ebb4a64f..ac26fe27c 100644 --- a/versioned_docs/version-2.19/reference/targets/docker_image.mdx +++ b/versioned_docs/version-2.19/reference/targets/docker_image.mdx @@ -39,7 +39,7 @@ Backend: `pants.backend.docker` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -52,7 +52,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -78,9 +78,9 @@ Use `[docker].build_args` to set default build args for all images. Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -291,7 +291,7 @@ See [Docker documentation](https://docs.docker.com/develop/develop-images/build_ default_repr={`False`} > -If true, do not push this image to registries when running `scie-pants-linux-x86_64 publish`. +If true, do not push this image to registries when running `pants publish`. @@ -450,7 +450,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. diff --git a/versioned_docs/version-2.19/reference/targets/experimental_test_shell_command.mdx b/versioned_docs/version-2.19/reference/targets/experimental_test_shell_command.mdx index d9cbf0eed..58eccc73a 100644 --- a/versioned_docs/version-2.19/reference/targets/experimental_test_shell_command.mdx +++ b/versioned_docs/version-2.19/reference/targets/experimental_test_shell_command.mdx @@ -39,7 +39,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -52,7 +52,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.19/reference/targets/experimental_wrap_as_go_package_sources.mdx b/versioned_docs/version-2.19/reference/targets/experimental_wrap_as_go_package_sources.mdx index 76db3f1ba..0630639a4 100644 --- a/versioned_docs/version-2.19/reference/targets/experimental_wrap_as_go_package_sources.mdx +++ b/versioned_docs/version-2.19/reference/targets/experimental_wrap_as_go_package_sources.mdx @@ -30,7 +30,7 @@ Backend: `pants.backend.experimental.go` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.19/reference/targets/experimental_wrap_as_java_sources.mdx b/versioned_docs/version-2.19/reference/targets/experimental_wrap_as_java_sources.mdx index 940029f9b..ff3e04681 100644 --- a/versioned_docs/version-2.19/reference/targets/experimental_wrap_as_java_sources.mdx +++ b/versioned_docs/version-2.19/reference/targets/experimental_wrap_as_java_sources.mdx @@ -30,7 +30,7 @@ Backend: `pants.backend.experimental.java` @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.19/reference/targets/experimental_wrap_as_kotlin_sources.mdx b/versioned_docs/version-2.19/reference/targets/experimental_wrap_as_kotlin_sources.mdx index 003b6ad9a..bae3428a7 100644 --- a/versioned_docs/version-2.19/reference/targets/experimental_wrap_as_kotlin_sources.mdx +++ b/versioned_docs/version-2.19/reference/targets/experimental_wrap_as_kotlin_sources.mdx @@ -30,7 +30,7 @@ Backend: `pants.backend.experimental.kotlin` @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.19/reference/targets/experimental_wrap_as_python_sources.mdx b/versioned_docs/version-2.19/reference/targets/experimental_wrap_as_python_sources.mdx index a341b498b..5751ec09f 100644 --- a/versioned_docs/version-2.19/reference/targets/experimental_wrap_as_python_sources.mdx +++ b/versioned_docs/version-2.19/reference/targets/experimental_wrap_as_python_sources.mdx @@ -30,7 +30,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.19/reference/targets/experimental_wrap_as_resources.mdx b/versioned_docs/version-2.19/reference/targets/experimental_wrap_as_resources.mdx index bdb4704b5..7f60252a5 100644 --- a/versioned_docs/version-2.19/reference/targets/experimental_wrap_as_resources.mdx +++ b/versioned_docs/version-2.19/reference/targets/experimental_wrap_as_resources.mdx @@ -30,7 +30,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.19/reference/targets/experimental_wrap_as_scala_sources.mdx b/versioned_docs/version-2.19/reference/targets/experimental_wrap_as_scala_sources.mdx index df94d3733..5548c481b 100644 --- a/versioned_docs/version-2.19/reference/targets/experimental_wrap_as_scala_sources.mdx +++ b/versioned_docs/version-2.19/reference/targets/experimental_wrap_as_scala_sources.mdx @@ -30,7 +30,7 @@ Backend: `pants.backend.experimental.scala` @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.19/reference/targets/file.mdx b/versioned_docs/version-2.19/reference/targets/file.mdx index 9e3792db7..520d6cc1e 100644 --- a/versioned_docs/version-2.19/reference/targets/file.mdx +++ b/versioned_docs/version-2.19/reference/targets/file.mdx @@ -26,7 +26,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -52,9 +52,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.19/reference/targets/files.mdx b/versioned_docs/version-2.19/reference/targets/files.mdx index 27e45f9c2..7adba2e0d 100644 --- a/versioned_docs/version-2.19/reference/targets/files.mdx +++ b/versioned_docs/version-2.19/reference/targets/files.mdx @@ -24,7 +24,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -94,9 +94,9 @@ You can specify the same file name in multiple keys, so long as you don't o Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.19/reference/targets/go_binary.mdx b/versioned_docs/version-2.19/reference/targets/go_binary.mdx index 55a27e2dd..e1a85a7a6 100644 --- a/versioned_docs/version-2.19/reference/targets/go_binary.mdx +++ b/versioned_docs/version-2.19/reference/targets/go_binary.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.go` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -52,7 +52,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. diff --git a/versioned_docs/version-2.19/reference/targets/go_mod.mdx b/versioned_docs/version-2.19/reference/targets/go_mod.mdx index ea3d4e8ad..a0cfd6173 100644 --- a/versioned_docs/version-2.19/reference/targets/go_mod.mdx +++ b/versioned_docs/version-2.19/reference/targets/go_mod.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.go` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.19/reference/targets/go_package.mdx b/versioned_docs/version-2.19/reference/targets/go_package.mdx index 9f9cad058..ff9f04e71 100644 --- a/versioned_docs/version-2.19/reference/targets/go_package.mdx +++ b/versioned_docs/version-2.19/reference/targets/go_package.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.experimental.go` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -52,9 +52,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.19/reference/targets/go_third_party_package.mdx b/versioned_docs/version-2.19/reference/targets/go_third_party_package.mdx index bb4270e12..df9c6ca79 100644 --- a/versioned_docs/version-2.19/reference/targets/go_third_party_package.mdx +++ b/versioned_docs/version-2.19/reference/targets/go_third_party_package.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.go` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -54,9 +54,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.19/reference/targets/helm_artifact.mdx b/versioned_docs/version-2.19/reference/targets/helm_artifact.mdx index 0c94682be..df2c66974 100644 --- a/versioned_docs/version-2.19/reference/targets/helm_artifact.mdx +++ b/versioned_docs/version-2.19/reference/targets/helm_artifact.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.helm` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.19/reference/targets/helm_chart.mdx b/versioned_docs/version-2.19/reference/targets/helm_chart.mdx index edf37f824..8cc1c1c87 100644 --- a/versioned_docs/version-2.19/reference/targets/helm_chart.mdx +++ b/versioned_docs/version-2.19/reference/targets/helm_chart.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.helm` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -76,9 +76,9 @@ Example: `sources=['values.yaml', 'templates/*.yaml', '!values_ignore.yaml']` Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -99,7 +99,7 @@ If undefined, this will use the path to the BUILD file, For example, `src/charts Regardless of whether you use the default or set this field, the path will end with Helms's file format of `-.tgz`, where `chart_name` and `chart_version` are the values extracted from the Chart.yaml file. So, using the default for this field, the target `src/charts/mychart:tgt_name` might have a final path like `src.charts.mychart/tgt_name/mychart-0.1.0.tgz`. -When running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. @@ -183,7 +183,7 @@ The above example shows two valid `registry` options: using an alias to a config default_repr={`False`} > -If set to true, do not push this Helm chart to registries when running `scie-pants-linux-x86_64 publish`. +If set to true, do not push this Helm chart to registries when running `pants publish`. @@ -194,7 +194,7 @@ If set to true, do not push this Helm chart to registries when running `scie-pan default_repr={`False`} > -If set to true, do not run any linting in this Helm chart when running `scie-pants-linux-x86_64 lint`. +If set to true, do not run any linting in this Helm chart when running `pants lint`. diff --git a/versioned_docs/version-2.19/reference/targets/helm_deployment.mdx b/versioned_docs/version-2.19/reference/targets/helm_deployment.mdx index b52599536..0e1c2d730 100644 --- a/versioned_docs/version-2.19/reference/targets/helm_deployment.mdx +++ b/versioned_docs/version-2.19/reference/targets/helm_deployment.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.helm` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -72,9 +72,9 @@ Name of the release used in the deployment. If not set, the target name will be Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.19/reference/targets/helm_unittest_test.mdx b/versioned_docs/version-2.19/reference/targets/helm_unittest_test.mdx index 5ce37dea5..1db29c116 100644 --- a/versioned_docs/version-2.19/reference/targets/helm_unittest_test.mdx +++ b/versioned_docs/version-2.19/reference/targets/helm_unittest_test.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.helm` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -63,9 +63,9 @@ Path is relative to the BUILD file's directory, e.g. `source='example.ext'` Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.19/reference/targets/helm_unittest_tests.mdx b/versioned_docs/version-2.19/reference/targets/helm_unittest_tests.mdx index 71eb624de..d159e932a 100644 --- a/versioned_docs/version-2.19/reference/targets/helm_unittest_tests.mdx +++ b/versioned_docs/version-2.19/reference/targets/helm_unittest_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.helm` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -65,9 +65,9 @@ Example: `sources=['*_test.yaml', '!ignore_test.yaml']` Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.19/reference/targets/java_source.mdx b/versioned_docs/version-2.19/reference/targets/java_source.mdx index e69eb9c4e..20b29ab6e 100644 --- a/versioned_docs/version-2.19/reference/targets/java_source.mdx +++ b/versioned_docs/version-2.19/reference/targets/java_source.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.java` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.19/reference/targets/java_sources.mdx b/versioned_docs/version-2.19/reference/targets/java_sources.mdx index c8eeaa1d7..5583288a8 100644 --- a/versioned_docs/version-2.19/reference/targets/java_sources.mdx +++ b/versioned_docs/version-2.19/reference/targets/java_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.java` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -77,9 +77,9 @@ If true, don't run Google Java Format on this target's code. Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.19/reference/targets/junit_test.mdx b/versioned_docs/version-2.19/reference/targets/junit_test.mdx index 3540489b8..13a642920 100644 --- a/versioned_docs/version-2.19/reference/targets/junit_test.mdx +++ b/versioned_docs/version-2.19/reference/targets/junit_test.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.java` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -91,9 +91,9 @@ This will be merged with and override values from `[test].extra_env_vars`. Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.19/reference/targets/junit_tests.mdx b/versioned_docs/version-2.19/reference/targets/junit_tests.mdx index 1297bbda4..d2e0af5b6 100644 --- a/versioned_docs/version-2.19/reference/targets/junit_tests.mdx +++ b/versioned_docs/version-2.19/reference/targets/junit_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.java` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -93,9 +93,9 @@ This will be merged with and override values from `[test].extra_env_vars`. Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.19/reference/targets/jvm_artifact.mdx b/versioned_docs/version-2.19/reference/targets/jvm_artifact.mdx index 64979af07..2f006d9e3 100644 --- a/versioned_docs/version-2.19/reference/targets/jvm_artifact.mdx +++ b/versioned_docs/version-2.19/reference/targets/jvm_artifact.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.java` @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.19/reference/targets/jvm_war.mdx b/versioned_docs/version-2.19/reference/targets/jvm_war.mdx index 9a19e4fbe..7a97c280e 100644 --- a/versioned_docs/version-2.19/reference/targets/jvm_war.mdx +++ b/versioned_docs/version-2.19/reference/targets/jvm_war.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.java` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -74,9 +74,9 @@ A list of addresses to `resources` and `files` targets with content to place in Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -126,7 +126,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. diff --git a/versioned_docs/version-2.19/reference/targets/kotlin_junit_test.mdx b/versioned_docs/version-2.19/reference/targets/kotlin_junit_test.mdx index 43ea1ba3c..01abd78c4 100644 --- a/versioned_docs/version-2.19/reference/targets/kotlin_junit_test.mdx +++ b/versioned_docs/version-2.19/reference/targets/kotlin_junit_test.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.kotlin` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.19/reference/targets/kotlin_junit_tests.mdx b/versioned_docs/version-2.19/reference/targets/kotlin_junit_tests.mdx index 2edb434fd..7577c07d9 100644 --- a/versioned_docs/version-2.19/reference/targets/kotlin_junit_tests.mdx +++ b/versioned_docs/version-2.19/reference/targets/kotlin_junit_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.kotlin` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -65,9 +65,9 @@ Example: `sources=['*Test.kt', '!TestIgnore.kt']` Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.19/reference/targets/kotlin_source.mdx b/versioned_docs/version-2.19/reference/targets/kotlin_source.mdx index ca5002adc..a942941ce 100644 --- a/versioned_docs/version-2.19/reference/targets/kotlin_source.mdx +++ b/versioned_docs/version-2.19/reference/targets/kotlin_source.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.kotlin` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.19/reference/targets/kotlin_sources.mdx b/versioned_docs/version-2.19/reference/targets/kotlin_sources.mdx index 191aac8a9..d94e69f13 100644 --- a/versioned_docs/version-2.19/reference/targets/kotlin_sources.mdx +++ b/versioned_docs/version-2.19/reference/targets/kotlin_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.kotlin` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -77,9 +77,9 @@ If true, don't run Ktlint on this target's code. Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.19/reference/targets/kotlinc_plugin.mdx b/versioned_docs/version-2.19/reference/targets/kotlinc_plugin.mdx index c8ad9eb36..828754fa0 100644 --- a/versioned_docs/version-2.19/reference/targets/kotlinc_plugin.mdx +++ b/versioned_docs/version-2.19/reference/targets/kotlinc_plugin.mdx @@ -34,7 +34,7 @@ Backend: `pants.backend.experimental.kotlin` @@ -47,7 +47,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.19/reference/targets/local_environment.mdx b/versioned_docs/version-2.19/reference/targets/local_environment.mdx index a4a67881d..2a155a1a1 100644 --- a/versioned_docs/version-2.19/reference/targets/local_environment.mdx +++ b/versioned_docs/version-2.19/reference/targets/local_environment.mdx @@ -30,7 +30,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.19/reference/targets/openapi_document.mdx b/versioned_docs/version-2.19/reference/targets/openapi_document.mdx index 6643a4f58..7efe68f16 100644 --- a/versioned_docs/version-2.19/reference/targets/openapi_document.mdx +++ b/versioned_docs/version-2.19/reference/targets/openapi_document.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.openapi` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.19/reference/targets/openapi_documents.mdx b/versioned_docs/version-2.19/reference/targets/openapi_documents.mdx index 2cfe5358f..6e657e47d 100644 --- a/versioned_docs/version-2.19/reference/targets/openapi_documents.mdx +++ b/versioned_docs/version-2.19/reference/targets/openapi_documents.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.openapi` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -77,9 +77,9 @@ If true, don't run `spectral lint` on this target's code. Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.19/reference/targets/openapi_source.mdx b/versioned_docs/version-2.19/reference/targets/openapi_source.mdx index 6c1299039..df6f62889 100644 --- a/versioned_docs/version-2.19/reference/targets/openapi_source.mdx +++ b/versioned_docs/version-2.19/reference/targets/openapi_source.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.openapi` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.19/reference/targets/openapi_sources.mdx b/versioned_docs/version-2.19/reference/targets/openapi_sources.mdx index 49a00b8aa..0c79e573f 100644 --- a/versioned_docs/version-2.19/reference/targets/openapi_sources.mdx +++ b/versioned_docs/version-2.19/reference/targets/openapi_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.openapi` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -77,9 +77,9 @@ If true, don't run `openapi-format` on this target's code. Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.19/reference/targets/pants_requirements.mdx b/versioned_docs/version-2.19/reference/targets/pants_requirements.mdx index eb02a1dd1..6cfec2b84 100644 --- a/versioned_docs/version-2.19/reference/targets/pants_requirements.mdx +++ b/versioned_docs/version-2.19/reference/targets/pants_requirements.mdx @@ -30,7 +30,7 @@ Backend: `pants.backend.plugin_development` @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.19/reference/targets/pex_binaries.mdx b/versioned_docs/version-2.19/reference/targets/pex_binaries.mdx index 3b507328f..7faf9c0ef 100644 --- a/versioned_docs/version-2.19/reference/targets/pex_binaries.mdx +++ b/versioned_docs/version-2.19/reference/targets/pex_binaries.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -147,9 +147,9 @@ All dependencies must share the same value for their `resolve` field. Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.19/reference/targets/pex_binary.mdx b/versioned_docs/version-2.19/reference/targets/pex_binary.mdx index 281aba15d..7459139db 100644 --- a/versioned_docs/version-2.19/reference/targets/pex_binary.mdx +++ b/versioned_docs/version-2.19/reference/targets/pex_binary.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -101,9 +101,9 @@ All dependencies must share the same value for their `resolve` field. Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -376,7 +376,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. diff --git a/versioned_docs/version-2.19/reference/targets/pipenv_requirements.mdx b/versioned_docs/version-2.19/reference/targets/pipenv_requirements.mdx index e06585179..f67f613c7 100644 --- a/versioned_docs/version-2.19/reference/targets/pipenv_requirements.mdx +++ b/versioned_docs/version-2.19/reference/targets/pipenv_requirements.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.19/reference/targets/poetry_requirements.mdx b/versioned_docs/version-2.19/reference/targets/poetry_requirements.mdx index 82136c634..6edf88e02 100644 --- a/versioned_docs/version-2.19/reference/targets/poetry_requirements.mdx +++ b/versioned_docs/version-2.19/reference/targets/poetry_requirements.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.19/reference/targets/protobuf_source.mdx b/versioned_docs/version-2.19/reference/targets/protobuf_source.mdx index 93d7dca66..1ba0a4298 100644 --- a/versioned_docs/version-2.19/reference/targets/protobuf_source.mdx +++ b/versioned_docs/version-2.19/reference/targets/protobuf_source.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.codegen.protobuf.python Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -54,9 +54,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.19/reference/targets/protobuf_sources.mdx b/versioned_docs/version-2.19/reference/targets/protobuf_sources.mdx index 10a2d50fc..8054bad9b 100644 --- a/versioned_docs/version-2.19/reference/targets/protobuf_sources.mdx +++ b/versioned_docs/version-2.19/reference/targets/protobuf_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.codegen.protobuf.python Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -218,9 +218,9 @@ Whether to generate gRPC code or not. Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.19/reference/targets/pyoxidizer_binary.mdx b/versioned_docs/version-2.19/reference/targets/pyoxidizer_binary.mdx index 4dd3ffaf3..fe7f2ae9f 100644 --- a/versioned_docs/version-2.19/reference/targets/pyoxidizer_binary.mdx +++ b/versioned_docs/version-2.19/reference/targets/pyoxidizer_binary.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.python.pac Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -58,7 +58,7 @@ If undefined, this will use the path to the BUILD file, followed by the target n Regardless of whether you use the default or set this field, the path will end with PyOxidizer's file format of `/{debug,release}/install/`, where `platform` is a Rust platform triplet like `aarch-64-apple-darwin` and `binary_name` is the value of the `binary_name` field. So, using the default for this field, the target `src/python/project:bin` might have a final path like `src.python.project/bin/aarch-64-apple-darwin/release/bin`. -When running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. diff --git a/versioned_docs/version-2.19/reference/targets/python_aws_lambda_function.mdx b/versioned_docs/version-2.19/reference/targets/python_aws_lambda_function.mdx index 750a304e6..2b7002fc4 100644 --- a/versioned_docs/version-2.19/reference/targets/python_aws_lambda_function.mdx +++ b/versioned_docs/version-2.19/reference/targets/python_aws_lambda_function.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.awslambda.python` @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -54,7 +54,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. @@ -144,9 +144,9 @@ You can specify multiple valid environments by using `parametrize`. If `__local_ Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.19/reference/targets/python_aws_lambda_layer.mdx b/versioned_docs/version-2.19/reference/targets/python_aws_lambda_layer.mdx index fa9314172..11019185d 100644 --- a/versioned_docs/version-2.19/reference/targets/python_aws_lambda_layer.mdx +++ b/versioned_docs/version-2.19/reference/targets/python_aws_lambda_layer.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.awslambda.python` @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -54,7 +54,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. @@ -155,9 +155,9 @@ Whether to resolve first party sources and include them in the AWS Lambda artifa Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.19/reference/targets/python_distribution.mdx b/versioned_docs/version-2.19/reference/targets/python_distribution.mdx index 1a9f8005b..b229af861 100644 --- a/versioned_docs/version-2.19/reference/targets/python_distribution.mdx +++ b/versioned_docs/version-2.19/reference/targets/python_distribution.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -71,9 +71,9 @@ See https://www.pantsbuild.org/v2.19/docs/python-interpreter-compatibility for h Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -108,7 +108,7 @@ Note that Pants will assume that any value that either starts with `:` or has `/ Pants will attempt to infer dependencies, which you can confirm by running: ``` -scie-pants-linux-x86_64 dependencies +pants dependencies ``` diff --git a/versioned_docs/version-2.19/reference/targets/python_google_cloud_function.mdx b/versioned_docs/version-2.19/reference/targets/python_google_cloud_function.mdx index b7896e5ba..d9ac50ca4 100644 --- a/versioned_docs/version-2.19/reference/targets/python_google_cloud_function.mdx +++ b/versioned_docs/version-2.19/reference/targets/python_google_cloud_function.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.google_cloud_function.p Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -54,7 +54,7 @@ Where the built asset should be located. If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app` would be `src.python.project/app.ext`. -When running `scie-pants-linux-x86_64 package`, this path will be prefixed by `--distdir` (e.g. `dist/`). +When running `pants package`, this path will be prefixed by `--distdir` (e.g. `dist/`). Warning: setting this value risks naming collisions with other package targets you may have. @@ -69,9 +69,9 @@ Warning: setting this value risks naming collisions with other package targets y Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.19/reference/targets/python_requirement.mdx b/versioned_docs/version-2.19/reference/targets/python_requirement.mdx index f1a47e663..206c393b7 100644 --- a/versioned_docs/version-2.19/reference/targets/python_requirement.mdx +++ b/versioned_docs/version-2.19/reference/targets/python_requirement.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -69,9 +69,9 @@ If the requirement depends on some other requirement to work, such as needing `s Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.19/reference/targets/python_requirements.mdx b/versioned_docs/version-2.19/reference/targets/python_requirements.mdx index 621be0c31..b4078a301 100644 --- a/versioned_docs/version-2.19/reference/targets/python_requirements.mdx +++ b/versioned_docs/version-2.19/reference/targets/python_requirements.mdx @@ -30,7 +30,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.19/reference/targets/python_source.mdx b/versioned_docs/version-2.19/reference/targets/python_source.mdx index 4e09b8a3d..a82d50c83 100644 --- a/versioned_docs/version-2.19/reference/targets/python_source.mdx +++ b/versioned_docs/version-2.19/reference/targets/python_source.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -69,9 +69,9 @@ See https://www.pantsbuild.org/v2.19/docs/python-interpreter-compatibility for h Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.19/reference/targets/python_sources.mdx b/versioned_docs/version-2.19/reference/targets/python_sources.mdx index 40b1a8bd6..120e8f6b0 100644 --- a/versioned_docs/version-2.19/reference/targets/python_sources.mdx +++ b/versioned_docs/version-2.19/reference/targets/python_sources.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -300,9 +300,9 @@ The latter mode is similar to creating, activating, and using a virtual environm Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.19/reference/targets/python_test.mdx b/versioned_docs/version-2.19/reference/targets/python_test.mdx index 4a958e968..c990b871d 100644 --- a/versioned_docs/version-2.19/reference/targets/python_test.mdx +++ b/versioned_docs/version-2.19/reference/targets/python_test.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -54,9 +54,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -161,11 +161,11 @@ When tests with the same `batch_compatibility_tag` have incompatibilities in som default_repr={`None`} > -Addresses to targets that can be built with the `scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run. +Addresses to targets that can be built with the `pants package` goal and whose resulting artifacts should be included in the test run. -Pants will build the artifacts as if you had run `scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). +Pants will build the artifacts as if you had run `pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). -You can include anything that can be built by `scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_aws_lambda_function`, or an `archive`. +You can include anything that can be built by `pants package`, e.g. a `pex_binary`, `python_aws_lambda_function`, or an `archive`. diff --git a/versioned_docs/version-2.19/reference/targets/python_test_utils.mdx b/versioned_docs/version-2.19/reference/targets/python_test_utils.mdx index fa71460c9..9aaf21127 100644 --- a/versioned_docs/version-2.19/reference/targets/python_test_utils.mdx +++ b/versioned_docs/version-2.19/reference/targets/python_test_utils.mdx @@ -26,7 +26,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -300,9 +300,9 @@ The latter mode is similar to creating, activating, and using a virtual environm Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.19/reference/targets/python_tests.mdx b/versioned_docs/version-2.19/reference/targets/python_tests.mdx index 0db724f34..a4c705cad 100644 --- a/versioned_docs/version-2.19/reference/targets/python_tests.mdx +++ b/versioned_docs/version-2.19/reference/targets/python_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.python` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -282,9 +282,9 @@ If true, don't run Pylint on this target's code. Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -389,11 +389,11 @@ When tests with the same `batch_compatibility_tag` have incompatibilities in som default_repr={`None`} > -Addresses to targets that can be built with the `scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run. +Addresses to targets that can be built with the `pants package` goal and whose resulting artifacts should be included in the test run. -Pants will build the artifacts as if you had run `scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). +Pants will build the artifacts as if you had run `pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). -You can include anything that can be built by `scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_aws_lambda_function`, or an `archive`. +You can include anything that can be built by `pants package`, e.g. a `pex_binary`, `python_aws_lambda_function`, or an `archive`. diff --git a/versioned_docs/version-2.19/reference/targets/relocated_files.mdx b/versioned_docs/version-2.19/reference/targets/relocated_files.mdx index 62f3ec4e4..346339e69 100644 --- a/versioned_docs/version-2.19/reference/targets/relocated_files.mdx +++ b/versioned_docs/version-2.19/reference/targets/relocated_files.mdx @@ -61,7 +61,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -74,7 +74,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.19/reference/targets/remote_environment.mdx b/versioned_docs/version-2.19/reference/targets/remote_environment.mdx index 6842b88b3..d7538a03a 100644 --- a/versioned_docs/version-2.19/reference/targets/remote_environment.mdx +++ b/versioned_docs/version-2.19/reference/targets/remote_environment.mdx @@ -32,7 +32,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -45,7 +45,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.19/reference/targets/resource.mdx b/versioned_docs/version-2.19/reference/targets/resource.mdx index 47b9bbeb1..36a9496d3 100644 --- a/versioned_docs/version-2.19/reference/targets/resource.mdx +++ b/versioned_docs/version-2.19/reference/targets/resource.mdx @@ -26,7 +26,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -52,9 +52,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.19/reference/targets/resources.mdx b/versioned_docs/version-2.19/reference/targets/resources.mdx index cbbb0e604..e8959bfd3 100644 --- a/versioned_docs/version-2.19/reference/targets/resources.mdx +++ b/versioned_docs/version-2.19/reference/targets/resources.mdx @@ -24,7 +24,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -94,9 +94,9 @@ You can specify the same file name in multiple keys, so long as you don't o Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.19/reference/targets/run_shell_command.mdx b/versioned_docs/version-2.19/reference/targets/run_shell_command.mdx index 96824cfac..bf8dfe79c 100644 --- a/versioned_docs/version-2.19/reference/targets/run_shell_command.mdx +++ b/versioned_docs/version-2.19/reference/targets/run_shell_command.mdx @@ -37,7 +37,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -50,7 +50,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.19/reference/targets/scala_artifact.mdx b/versioned_docs/version-2.19/reference/targets/scala_artifact.mdx index bc564627c..5cdfb927d 100644 --- a/versioned_docs/version-2.19/reference/targets/scala_artifact.mdx +++ b/versioned_docs/version-2.19/reference/targets/scala_artifact.mdx @@ -30,7 +30,7 @@ Backend: `pants.backend.experimental.scala` @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.19/reference/targets/scala_junit_test.mdx b/versioned_docs/version-2.19/reference/targets/scala_junit_test.mdx index 3202f645a..be3e33c5f 100644 --- a/versioned_docs/version-2.19/reference/targets/scala_junit_test.mdx +++ b/versioned_docs/version-2.19/reference/targets/scala_junit_test.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.scala` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.19/reference/targets/scala_junit_tests.mdx b/versioned_docs/version-2.19/reference/targets/scala_junit_tests.mdx index 9666040ae..aae7de49f 100644 --- a/versioned_docs/version-2.19/reference/targets/scala_junit_tests.mdx +++ b/versioned_docs/version-2.19/reference/targets/scala_junit_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.scala` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -107,9 +107,9 @@ If unset, will default to `[test].timeout_default`; if that option is also unset Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.19/reference/targets/scala_source.mdx b/versioned_docs/version-2.19/reference/targets/scala_source.mdx index 783a75f49..58500c2b7 100644 --- a/versioned_docs/version-2.19/reference/targets/scala_source.mdx +++ b/versioned_docs/version-2.19/reference/targets/scala_source.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.scala` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.19/reference/targets/scala_sources.mdx b/versioned_docs/version-2.19/reference/targets/scala_sources.mdx index c1484e86a..679cb9a0d 100644 --- a/versioned_docs/version-2.19/reference/targets/scala_sources.mdx +++ b/versioned_docs/version-2.19/reference/targets/scala_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.scala` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -106,9 +106,9 @@ If true, don't run `scalafmt` on this target's code. Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.19/reference/targets/scalac_plugin.mdx b/versioned_docs/version-2.19/reference/targets/scalac_plugin.mdx index 2e9c51213..5debfdf3a 100644 --- a/versioned_docs/version-2.19/reference/targets/scalac_plugin.mdx +++ b/versioned_docs/version-2.19/reference/targets/scalac_plugin.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.scala` @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.19/reference/targets/scalatest_test.mdx b/versioned_docs/version-2.19/reference/targets/scalatest_test.mdx index af52cf9fc..29df9882e 100644 --- a/versioned_docs/version-2.19/reference/targets/scalatest_test.mdx +++ b/versioned_docs/version-2.19/reference/targets/scalatest_test.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.scala` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.19/reference/targets/scalatest_tests.mdx b/versioned_docs/version-2.19/reference/targets/scalatest_tests.mdx index 7adad0933..b6431cc32 100644 --- a/versioned_docs/version-2.19/reference/targets/scalatest_tests.mdx +++ b/versioned_docs/version-2.19/reference/targets/scalatest_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.scala` @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -94,9 +94,9 @@ You can specify the same file name in multiple keys, so long as you don't o Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.19/reference/targets/shell_command.mdx b/versioned_docs/version-2.19/reference/targets/shell_command.mdx index 56ea4bee6..1e096b900 100644 --- a/versioned_docs/version-2.19/reference/targets/shell_command.mdx +++ b/versioned_docs/version-2.19/reference/targets/shell_command.mdx @@ -42,7 +42,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -55,7 +55,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.19/reference/targets/shell_source.mdx b/versioned_docs/version-2.19/reference/targets/shell_source.mdx index fafc4dbbc..b1e575575 100644 --- a/versioned_docs/version-2.19/reference/targets/shell_source.mdx +++ b/versioned_docs/version-2.19/reference/targets/shell_source.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.19/reference/targets/shell_sources.mdx b/versioned_docs/version-2.19/reference/targets/shell_sources.mdx index d594364f2..1ea3a68c3 100644 --- a/versioned_docs/version-2.19/reference/targets/shell_sources.mdx +++ b/versioned_docs/version-2.19/reference/targets/shell_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -118,9 +118,9 @@ If true, don't run Shellcheck on this target's code. Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.19/reference/targets/shunit2_test.mdx b/versioned_docs/version-2.19/reference/targets/shunit2_test.mdx index e40e424de..6f8d18103 100644 --- a/versioned_docs/version-2.19/reference/targets/shunit2_test.mdx +++ b/versioned_docs/version-2.19/reference/targets/shunit2_test.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -67,9 +67,9 @@ Path is relative to the BUILD file's directory, e.g. `source='example.ext'` Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -119,11 +119,11 @@ Which shell to run the tests with. If unspecified, Pants will look for a shebang default_repr={`None`} > -Addresses to targets that can be built with the `scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run. +Addresses to targets that can be built with the `pants package` goal and whose resulting artifacts should be included in the test run. -Pants will build the artifacts as if you had run `scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). +Pants will build the artifacts as if you had run `pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). -You can include anything that can be built by `scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_aws_lambda_function`, or an `archive`. +You can include anything that can be built by `pants package`, e.g. a `pex_binary`, `python_aws_lambda_function`, or an `archive`. diff --git a/versioned_docs/version-2.19/reference/targets/shunit2_tests.mdx b/versioned_docs/version-2.19/reference/targets/shunit2_tests.mdx index fa7a68bf5..2bd9dd440 100644 --- a/versioned_docs/version-2.19/reference/targets/shunit2_tests.mdx +++ b/versioned_docs/version-2.19/reference/targets/shunit2_tests.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.shell` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -118,9 +118,9 @@ If true, don't run Shellcheck on this target's code. Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. @@ -170,11 +170,11 @@ Which shell to run the tests with. If unspecified, Pants will look for a shebang default_repr={`None`} > -Addresses to targets that can be built with the `scie-pants-linux-x86_64 package` goal and whose resulting artifacts should be included in the test run. +Addresses to targets that can be built with the `pants package` goal and whose resulting artifacts should be included in the test run. -Pants will build the artifacts as if you had run `scie-pants-linux-x86_64 package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). +Pants will build the artifacts as if you had run `pants package`. It will include the results in your test's chroot, using the same name they would normally have, but without the `--distdir` prefix (e.g. `dist/`). -You can include anything that can be built by `scie-pants-linux-x86_64 package`, e.g. a `pex_binary`, `python_aws_lambda_function`, or an `archive`. +You can include anything that can be built by `pants package`, e.g. a `pex_binary`, `python_aws_lambda_function`, or an `archive`. diff --git a/versioned_docs/version-2.19/reference/targets/system_binary.mdx b/versioned_docs/version-2.19/reference/targets/system_binary.mdx index 9920f16b2..d7bd775a0 100644 --- a/versioned_docs/version-2.19/reference/targets/system_binary.mdx +++ b/versioned_docs/version-2.19/reference/targets/system_binary.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.adhoc` @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.19/reference/targets/target.mdx b/versioned_docs/version-2.19/reference/targets/target.mdx index ed687333c..160c4aee9 100644 --- a/versioned_docs/version-2.19/reference/targets/target.mdx +++ b/versioned_docs/version-2.19/reference/targets/target.mdx @@ -26,7 +26,7 @@ Backend: `pants.core` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -39,7 +39,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -52,9 +52,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.19/reference/targets/terraform_deployment.mdx b/versioned_docs/version-2.19/reference/targets/terraform_deployment.mdx index 7aff5425f..b40be8aab 100644 --- a/versioned_docs/version-2.19/reference/targets/terraform_deployment.mdx +++ b/versioned_docs/version-2.19/reference/targets/terraform_deployment.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.experimental.terraform` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -50,9 +50,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.19/reference/targets/terraform_module.mdx b/versioned_docs/version-2.19/reference/targets/terraform_module.mdx index 0a889f657..5fa726199 100644 --- a/versioned_docs/version-2.19/reference/targets/terraform_module.mdx +++ b/versioned_docs/version-2.19/reference/targets/terraform_module.mdx @@ -28,7 +28,7 @@ Backend: `pants.backend.experimental.terraform` Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -41,7 +41,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -54,9 +54,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.19/reference/targets/thrift_source.mdx b/versioned_docs/version-2.19/reference/targets/thrift_source.mdx index 18a309b1b..56b3e4cba 100644 --- a/versioned_docs/version-2.19/reference/targets/thrift_source.mdx +++ b/versioned_docs/version-2.19/reference/targets/thrift_source.mdx @@ -27,7 +27,7 @@ Backend: `pants.backend.codegen.thrift.apache.p Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -40,7 +40,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -53,9 +53,9 @@ Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descr Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.19/reference/targets/thrift_sources.mdx b/versioned_docs/version-2.19/reference/targets/thrift_sources.mdx index 755e516b0..b8b76e4bc 100644 --- a/versioned_docs/version-2.19/reference/targets/thrift_sources.mdx +++ b/versioned_docs/version-2.19/reference/targets/thrift_sources.mdx @@ -24,7 +24,7 @@ Backend: `pants.backend.codegen.thrift.apache.p Arbitrary strings to describe a target. -For example, you may tag some test targets with 'integration_test' so that you could run `scie-pants-linux-x86_64 --tag='integration_test' test ::` to only run on targets with that tag. +For example, you may tag some test targets with 'integration_test' so that you could run `pants --tag='integration_test' test ::` to only run on targets with that tag. @@ -37,7 +37,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. @@ -109,9 +109,9 @@ All dependencies must share the same value for their `resolve` field. Addresses to other targets that this target depends on, e.g. `['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django']`. -This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `scie-pants-linux-x86_64 dependencies` or `scie-pants-linux-x86_64 peek` on this target to get the final result. +This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `pants dependencies` or `pants peek` on this target to get the final result. -See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `scie-pants-linux-x86_64 list ::` to find all addresses in your project, or `scie-pants-linux-x86_64 list dir` to find all addresses defined in that directory. +See https://www.pantsbuild.org/v2.19/docs/targets for more about how addresses are formed, including for generated targets. You can also run `pants list ::` to find all addresses in your project, or `pants list dir` to find all addresses defined in that directory. If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt` instead of `helloworld/subdir:tgt`. For generated first-party addresses, use `./` for the file path, e.g. `./main.py:tgt`; for all other generated targets, use `:tgt#generated_name`. diff --git a/versioned_docs/version-2.19/reference/targets/vcs_version.mdx b/versioned_docs/version-2.19/reference/targets/vcs_version.mdx index 12f2d89a5..9b58dc7e0 100644 --- a/versioned_docs/version-2.19/reference/targets/vcs_version.mdx +++ b/versioned_docs/version-2.19/reference/targets/vcs_version.mdx @@ -30,7 +30,7 @@ Backend: `pants.backend.experimental.python` @@ -43,7 +43,7 @@ For example, you may tag some test targets with 'integration_test' so A human-readable description of the target. -Use `scie-pants-linux-x86_64 list --documented ::` to see all targets with descriptions. +Use `pants list --documented ::` to see all targets with descriptions. diff --git a/versioned_docs/version-2.2/reference/help-all.json b/versioned_docs/version-2.2/reference/help-all.json index 125729734..d61ef47f4 100644 --- a/versioned_docs/version-2.2/reference/help-all.json +++ b/versioned_docs/version-2.2/reference/help-all.json @@ -1256,7 +1256,7 @@ { "details": "from env var PANTS_BIN_NAME", "rank": "ENVIRONMENT", - "value": "/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64" + "value": "/home/josh/work/scie-pants/dist/pants" } ] } @@ -3692,7 +3692,7 @@ "deprecation_active": false, "display_args": ["--[no-]bandit-skip"], "env_var": "PANTS_BANDIT_SKIP", - "help": "Don't use Bandit when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`", + "help": "Don't use Bandit when running `/home/josh/work/scie-pants/dist/pants lint`", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--bandit-skip", "--no-bandit-skip"], @@ -3913,7 +3913,7 @@ "deprecation_active": false, "display_args": ["--[no-]black-skip"], "env_var": "PANTS_BLACK_SKIP", - "help": "Don't use Black when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`", + "help": "Don't use Black when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--black-skip", "--no-black-skip"], @@ -4758,7 +4758,7 @@ "deprecation_active": false, "display_args": ["--[no-]docformatter-skip"], "env_var": "PANTS_DOCFORMATTER_SKIP", - "help": "Don't use docformatter when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use docformatter when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -5449,7 +5449,7 @@ "deprecation_active": false, "display_args": ["--[no-]flake8-skip"], "env_var": "PANTS_FLAKE8_SKIP", - "help": "Don't use Flake8 when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`", + "help": "Don't use Flake8 when running `/home/josh/work/scie-pants/dist/pants lint`", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--flake8-skip", "--no-flake8-skip"], @@ -6005,7 +6005,7 @@ "deprecation_active": false, "display_args": ["--[no-]isort-skip"], "env_var": "PANTS_ISORT_SKIP", - "help": "Don't use isort when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use isort when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--isort-skip", "--no-isort-skip"], @@ -6591,7 +6591,7 @@ "deprecation_active": false, "display_args": ["--[no-]mypy-skip"], "env_var": "PANTS_MYPY_SKIP", - "help": "Don't use MyPy when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use MyPy when running `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--mypy-skip", "--no-mypy-skip"], @@ -7220,7 +7220,7 @@ "deprecation_active": false, "display_args": ["--[no-]pylint-skip"], "env_var": "PANTS_PYLINT_SKIP", - "help": "Don't use Pylint when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`", + "help": "Don't use Pylint when running `/home/josh/work/scie-pants/dist/pants lint`", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pylint-skip", "--no-pylint-skip"], diff --git a/versioned_docs/version-2.2/reference/subsystems/bandit.mdx b/versioned_docs/version-2.2/reference/subsystems/bandit.mdx index fbb4af88d..40364a77f 100644 --- a/versioned_docs/version-2.2/reference/subsystems/bandit.mdx +++ b/versioned_docs/version-2.2/reference/subsystems/bandit.mdx @@ -25,7 +25,7 @@ Config section: `[bandit]` default_repr={`False`} > -Don't use Bandit when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint` +Don't use Bandit when running `/home/josh/work/scie-pants/dist/pants lint` diff --git a/versioned_docs/version-2.2/reference/subsystems/black.mdx b/versioned_docs/version-2.2/reference/subsystems/black.mdx index bdb6e49ca..f3659d7f2 100644 --- a/versioned_docs/version-2.2/reference/subsystems/black.mdx +++ b/versioned_docs/version-2.2/reference/subsystems/black.mdx @@ -25,7 +25,7 @@ Config section: `[black]` default_repr={`False`} > -Don't use Black when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint` +Don't use Black when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint` diff --git a/versioned_docs/version-2.2/reference/subsystems/docformatter.mdx b/versioned_docs/version-2.2/reference/subsystems/docformatter.mdx index a574b3120..4d72644b3 100644 --- a/versioned_docs/version-2.2/reference/subsystems/docformatter.mdx +++ b/versioned_docs/version-2.2/reference/subsystems/docformatter.mdx @@ -25,7 +25,7 @@ Config section: `[docformatter]` default_repr={`False`} > -Don't use docformatter when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use docformatter when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.2/reference/subsystems/flake8.mdx b/versioned_docs/version-2.2/reference/subsystems/flake8.mdx index 6951545d7..f35874316 100644 --- a/versioned_docs/version-2.2/reference/subsystems/flake8.mdx +++ b/versioned_docs/version-2.2/reference/subsystems/flake8.mdx @@ -25,7 +25,7 @@ Config section: `[flake8]` default_repr={`False`} > -Don't use Flake8 when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint` +Don't use Flake8 when running `/home/josh/work/scie-pants/dist/pants lint` diff --git a/versioned_docs/version-2.2/reference/subsystems/isort.mdx b/versioned_docs/version-2.2/reference/subsystems/isort.mdx index ea684feda..d17d20853 100644 --- a/versioned_docs/version-2.2/reference/subsystems/isort.mdx +++ b/versioned_docs/version-2.2/reference/subsystems/isort.mdx @@ -25,7 +25,7 @@ Config section: `[isort]` default_repr={`False`} > -Don't use isort when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use isort when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.2/reference/subsystems/mypy.mdx b/versioned_docs/version-2.2/reference/subsystems/mypy.mdx index 2c91623de..cc2775aab 100644 --- a/versioned_docs/version-2.2/reference/subsystems/mypy.mdx +++ b/versioned_docs/version-2.2/reference/subsystems/mypy.mdx @@ -25,7 +25,7 @@ Config section: `[mypy]` default_repr={`False`} > -Don't use MyPy when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use MyPy when running `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.2/reference/subsystems/pylint.mdx b/versioned_docs/version-2.2/reference/subsystems/pylint.mdx index d3f517b9a..89a17f597 100644 --- a/versioned_docs/version-2.2/reference/subsystems/pylint.mdx +++ b/versioned_docs/version-2.2/reference/subsystems/pylint.mdx @@ -25,7 +25,7 @@ Config section: `[pylint]` default_repr={`False`} > -Don't use Pylint when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint` +Don't use Pylint when running `/home/josh/work/scie-pants/dist/pants lint` diff --git a/versioned_docs/version-2.3/reference/help-all.json b/versioned_docs/version-2.3/reference/help-all.json index 3a0a08fb6..708ac9d23 100644 --- a/versioned_docs/version-2.3/reference/help-all.json +++ b/versioned_docs/version-2.3/reference/help-all.json @@ -1245,7 +1245,7 @@ { "details": "from env var PANTS_BIN_NAME", "rank": "ENVIRONMENT", - "value": "/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64" + "value": "/home/josh/work/scie-pants/dist/pants" } ] } @@ -3777,7 +3777,7 @@ "deprecation_active": false, "display_args": ["--[no-]bandit-skip"], "env_var": "PANTS_BANDIT_SKIP", - "help": "Don't use Bandit when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`", + "help": "Don't use Bandit when running `/home/josh/work/scie-pants/dist/pants lint`", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--bandit-skip", "--no-bandit-skip"], @@ -3998,7 +3998,7 @@ "deprecation_active": false, "display_args": ["--[no-]black-skip"], "env_var": "PANTS_BLACK_SKIP", - "help": "Don't use Black when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`", + "help": "Don't use Black when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--black-skip", "--no-black-skip"], @@ -4843,7 +4843,7 @@ "deprecation_active": false, "display_args": ["--[no-]docformatter-skip"], "env_var": "PANTS_DOCFORMATTER_SKIP", - "help": "Don't use docformatter when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use docformatter when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -5534,7 +5534,7 @@ "deprecation_active": false, "display_args": ["--[no-]flake8-skip"], "env_var": "PANTS_FLAKE8_SKIP", - "help": "Don't use Flake8 when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`", + "help": "Don't use Flake8 when running `/home/josh/work/scie-pants/dist/pants lint`", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--flake8-skip", "--no-flake8-skip"], @@ -6090,7 +6090,7 @@ "deprecation_active": false, "display_args": ["--[no-]isort-skip"], "env_var": "PANTS_ISORT_SKIP", - "help": "Don't use isort when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use isort when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--isort-skip", "--no-isort-skip"], @@ -6676,7 +6676,7 @@ "deprecation_active": false, "display_args": ["--[no-]mypy-skip"], "env_var": "PANTS_MYPY_SKIP", - "help": "Don't use MyPy when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use MyPy when running `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--mypy-skip", "--no-mypy-skip"], @@ -7305,7 +7305,7 @@ "deprecation_active": false, "display_args": ["--[no-]pylint-skip"], "env_var": "PANTS_PYLINT_SKIP", - "help": "Don't use Pylint when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`", + "help": "Don't use Pylint when running `/home/josh/work/scie-pants/dist/pants lint`", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pylint-skip", "--no-pylint-skip"], diff --git a/versioned_docs/version-2.3/reference/subsystems/bandit.mdx b/versioned_docs/version-2.3/reference/subsystems/bandit.mdx index fbb4af88d..40364a77f 100644 --- a/versioned_docs/version-2.3/reference/subsystems/bandit.mdx +++ b/versioned_docs/version-2.3/reference/subsystems/bandit.mdx @@ -25,7 +25,7 @@ Config section: `[bandit]` default_repr={`False`} > -Don't use Bandit when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint` +Don't use Bandit when running `/home/josh/work/scie-pants/dist/pants lint` diff --git a/versioned_docs/version-2.3/reference/subsystems/black.mdx b/versioned_docs/version-2.3/reference/subsystems/black.mdx index bdb6e49ca..f3659d7f2 100644 --- a/versioned_docs/version-2.3/reference/subsystems/black.mdx +++ b/versioned_docs/version-2.3/reference/subsystems/black.mdx @@ -25,7 +25,7 @@ Config section: `[black]` default_repr={`False`} > -Don't use Black when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint` +Don't use Black when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint` diff --git a/versioned_docs/version-2.3/reference/subsystems/docformatter.mdx b/versioned_docs/version-2.3/reference/subsystems/docformatter.mdx index d5a337c83..49ebe36bf 100644 --- a/versioned_docs/version-2.3/reference/subsystems/docformatter.mdx +++ b/versioned_docs/version-2.3/reference/subsystems/docformatter.mdx @@ -25,7 +25,7 @@ Config section: `[docformatter]` default_repr={`False`} > -Don't use docformatter when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use docformatter when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.3/reference/subsystems/flake8.mdx b/versioned_docs/version-2.3/reference/subsystems/flake8.mdx index 6951545d7..f35874316 100644 --- a/versioned_docs/version-2.3/reference/subsystems/flake8.mdx +++ b/versioned_docs/version-2.3/reference/subsystems/flake8.mdx @@ -25,7 +25,7 @@ Config section: `[flake8]` default_repr={`False`} > -Don't use Flake8 when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint` +Don't use Flake8 when running `/home/josh/work/scie-pants/dist/pants lint` diff --git a/versioned_docs/version-2.3/reference/subsystems/isort.mdx b/versioned_docs/version-2.3/reference/subsystems/isort.mdx index ea684feda..d17d20853 100644 --- a/versioned_docs/version-2.3/reference/subsystems/isort.mdx +++ b/versioned_docs/version-2.3/reference/subsystems/isort.mdx @@ -25,7 +25,7 @@ Config section: `[isort]` default_repr={`False`} > -Don't use isort when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use isort when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.3/reference/subsystems/mypy.mdx b/versioned_docs/version-2.3/reference/subsystems/mypy.mdx index 60e555909..d96ad1f24 100644 --- a/versioned_docs/version-2.3/reference/subsystems/mypy.mdx +++ b/versioned_docs/version-2.3/reference/subsystems/mypy.mdx @@ -25,7 +25,7 @@ Config section: `[mypy]` default_repr={`False`} > -Don't use MyPy when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use MyPy when running `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.3/reference/subsystems/pylint.mdx b/versioned_docs/version-2.3/reference/subsystems/pylint.mdx index d3ba496bd..9e3437e17 100644 --- a/versioned_docs/version-2.3/reference/subsystems/pylint.mdx +++ b/versioned_docs/version-2.3/reference/subsystems/pylint.mdx @@ -25,7 +25,7 @@ Config section: `[pylint]` default_repr={`False`} > -Don't use Pylint when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint` +Don't use Pylint when running `/home/josh/work/scie-pants/dist/pants lint` diff --git a/versioned_docs/version-2.4/reference/help-all.json b/versioned_docs/version-2.4/reference/help-all.json index 548b390cb..68833cc94 100644 --- a/versioned_docs/version-2.4/reference/help-all.json +++ b/versioned_docs/version-2.4/reference/help-all.json @@ -1259,7 +1259,7 @@ { "details": "from env var PANTS_BIN_NAME", "rank": "ENVIRONMENT", - "value": "/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64" + "value": "/home/josh/work/scie-pants/dist/pants" } ] } @@ -3843,7 +3843,7 @@ "deprecation_active": false, "display_args": ["--[no-]bandit-skip"], "env_var": "PANTS_BANDIT_SKIP", - "help": "Don't use Bandit when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`", + "help": "Don't use Bandit when running `/home/josh/work/scie-pants/dist/pants lint`", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--bandit-skip", "--no-bandit-skip"], @@ -4090,7 +4090,7 @@ "deprecation_active": false, "display_args": ["--[no-]black-skip"], "env_var": "PANTS_BLACK_SKIP", - "help": "Don't use Black when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`", + "help": "Don't use Black when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--black-skip", "--no-black-skip"], @@ -4987,7 +4987,7 @@ "deprecation_active": false, "display_args": ["--[no-]docformatter-skip"], "env_var": "PANTS_DOCFORMATTER_SKIP", - "help": "Don't use docformatter when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use docformatter when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -5704,7 +5704,7 @@ "deprecation_active": false, "display_args": ["--[no-]flake8-skip"], "env_var": "PANTS_FLAKE8_SKIP", - "help": "Don't use Flake8 when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`", + "help": "Don't use Flake8 when running `/home/josh/work/scie-pants/dist/pants lint`", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--flake8-skip", "--no-flake8-skip"], @@ -6312,7 +6312,7 @@ "deprecation_active": false, "display_args": ["--[no-]isort-skip"], "env_var": "PANTS_ISORT_SKIP", - "help": "Don't use isort when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use isort when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--isort-skip", "--no-isort-skip"], @@ -6950,7 +6950,7 @@ "deprecation_active": false, "display_args": ["--[no-]mypy-skip"], "env_var": "PANTS_MYPY_SKIP", - "help": "Don't use MyPy when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use MyPy when running `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--mypy-skip", "--no-mypy-skip"], @@ -7605,7 +7605,7 @@ "deprecation_active": false, "display_args": ["--[no-]pylint-skip"], "env_var": "PANTS_PYLINT_SKIP", - "help": "Don't use Pylint when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`", + "help": "Don't use Pylint when running `/home/josh/work/scie-pants/dist/pants lint`", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pylint-skip", "--no-pylint-skip"], diff --git a/versioned_docs/version-2.4/reference/subsystems/bandit.mdx b/versioned_docs/version-2.4/reference/subsystems/bandit.mdx index d46825557..2ea881309 100644 --- a/versioned_docs/version-2.4/reference/subsystems/bandit.mdx +++ b/versioned_docs/version-2.4/reference/subsystems/bandit.mdx @@ -25,7 +25,7 @@ Config section: `[bandit]` default_repr={`False`} > -Don't use Bandit when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint` +Don't use Bandit when running `/home/josh/work/scie-pants/dist/pants lint` diff --git a/versioned_docs/version-2.4/reference/subsystems/black.mdx b/versioned_docs/version-2.4/reference/subsystems/black.mdx index 82938a3e4..1e4a4bc09 100644 --- a/versioned_docs/version-2.4/reference/subsystems/black.mdx +++ b/versioned_docs/version-2.4/reference/subsystems/black.mdx @@ -25,7 +25,7 @@ Config section: `[black]` default_repr={`False`} > -Don't use Black when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint` +Don't use Black when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint` diff --git a/versioned_docs/version-2.4/reference/subsystems/docformatter.mdx b/versioned_docs/version-2.4/reference/subsystems/docformatter.mdx index 68a4dbf5b..dfacda168 100644 --- a/versioned_docs/version-2.4/reference/subsystems/docformatter.mdx +++ b/versioned_docs/version-2.4/reference/subsystems/docformatter.mdx @@ -25,7 +25,7 @@ Config section: `[docformatter]` default_repr={`False`} > -Don't use docformatter when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use docformatter when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.4/reference/subsystems/flake8.mdx b/versioned_docs/version-2.4/reference/subsystems/flake8.mdx index 6e43be812..443cf378e 100644 --- a/versioned_docs/version-2.4/reference/subsystems/flake8.mdx +++ b/versioned_docs/version-2.4/reference/subsystems/flake8.mdx @@ -25,7 +25,7 @@ Config section: `[flake8]` default_repr={`False`} > -Don't use Flake8 when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint` +Don't use Flake8 when running `/home/josh/work/scie-pants/dist/pants lint` diff --git a/versioned_docs/version-2.4/reference/subsystems/isort.mdx b/versioned_docs/version-2.4/reference/subsystems/isort.mdx index 95b56a53a..9423c7360 100644 --- a/versioned_docs/version-2.4/reference/subsystems/isort.mdx +++ b/versioned_docs/version-2.4/reference/subsystems/isort.mdx @@ -25,7 +25,7 @@ Config section: `[isort]` default_repr={`False`} > -Don't use isort when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use isort when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.4/reference/subsystems/mypy.mdx b/versioned_docs/version-2.4/reference/subsystems/mypy.mdx index 3c6231052..09b9ce1ea 100644 --- a/versioned_docs/version-2.4/reference/subsystems/mypy.mdx +++ b/versioned_docs/version-2.4/reference/subsystems/mypy.mdx @@ -25,7 +25,7 @@ Config section: `[mypy]` default_repr={`False`} > -Don't use MyPy when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use MyPy when running `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.4/reference/subsystems/pylint.mdx b/versioned_docs/version-2.4/reference/subsystems/pylint.mdx index 3edeb2562..0b87e25c0 100644 --- a/versioned_docs/version-2.4/reference/subsystems/pylint.mdx +++ b/versioned_docs/version-2.4/reference/subsystems/pylint.mdx @@ -25,7 +25,7 @@ Config section: `[pylint]` default_repr={`False`} > -Don't use Pylint when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint` +Don't use Pylint when running `/home/josh/work/scie-pants/dist/pants lint` diff --git a/versioned_docs/version-2.5/reference/help-all.json b/versioned_docs/version-2.5/reference/help-all.json index 5ad62474c..0b2f3b71b 100644 --- a/versioned_docs/version-2.5/reference/help-all.json +++ b/versioned_docs/version-2.5/reference/help-all.json @@ -1514,7 +1514,7 @@ { "details": "from env var PANTS_BIN_NAME", "rank": "ENVIRONMENT", - "value": "/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64" + "value": "/home/josh/work/scie-pants/dist/pants" } ] } @@ -4026,7 +4026,7 @@ "deprecation_active": false, "display_args": ["--[no-]bandit-skip"], "env_var": "PANTS_BANDIT_SKIP", - "help": "Don't use Bandit when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`", + "help": "Don't use Bandit when running `/home/josh/work/scie-pants/dist/pants lint`", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--bandit-skip", "--no-bandit-skip"], @@ -4310,7 +4310,7 @@ "deprecation_active": false, "display_args": ["--[no-]black-skip"], "env_var": "PANTS_BLACK_SKIP", - "help": "Don't use Black when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`", + "help": "Don't use Black when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--black-skip", "--no-black-skip"], @@ -5278,7 +5278,7 @@ "deprecation_active": false, "display_args": ["--[no-]docformatter-skip"], "env_var": "PANTS_DOCFORMATTER_SKIP", - "help": "Don't use docformatter when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use docformatter when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -6032,7 +6032,7 @@ "deprecation_active": false, "display_args": ["--[no-]flake8-skip"], "env_var": "PANTS_FLAKE8_SKIP", - "help": "Don't use Flake8 when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`", + "help": "Don't use Flake8 when running `/home/josh/work/scie-pants/dist/pants lint`", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--flake8-skip", "--no-flake8-skip"], @@ -6677,7 +6677,7 @@ "deprecation_active": false, "display_args": ["--[no-]isort-skip"], "env_var": "PANTS_ISORT_SKIP", - "help": "Don't use isort when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use isort when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--isort-skip", "--no-isort-skip"], @@ -7352,7 +7352,7 @@ "deprecation_active": false, "display_args": ["--[no-]mypy-skip"], "env_var": "PANTS_MYPY_SKIP", - "help": "Don't use MyPy when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 typecheck`.", + "help": "Don't use MyPy when running `/home/josh/work/scie-pants/dist/pants typecheck`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--mypy-skip", "--no-mypy-skip"], @@ -8044,7 +8044,7 @@ "deprecation_active": false, "display_args": ["--[no-]pylint-skip"], "env_var": "PANTS_PYLINT_SKIP", - "help": "Don't use Pylint when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`", + "help": "Don't use Pylint when running `/home/josh/work/scie-pants/dist/pants lint`", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pylint-skip", "--no-pylint-skip"], diff --git a/versioned_docs/version-2.5/reference/subsystems/bandit.mdx b/versioned_docs/version-2.5/reference/subsystems/bandit.mdx index 1b5856d09..e2ef7d940 100644 --- a/versioned_docs/version-2.5/reference/subsystems/bandit.mdx +++ b/versioned_docs/version-2.5/reference/subsystems/bandit.mdx @@ -25,7 +25,7 @@ Config section: `[bandit]` default_repr={`False`} > -Don't use Bandit when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint` +Don't use Bandit when running `/home/josh/work/scie-pants/dist/pants lint` diff --git a/versioned_docs/version-2.5/reference/subsystems/black.mdx b/versioned_docs/version-2.5/reference/subsystems/black.mdx index aff712797..1e10e774c 100644 --- a/versioned_docs/version-2.5/reference/subsystems/black.mdx +++ b/versioned_docs/version-2.5/reference/subsystems/black.mdx @@ -25,7 +25,7 @@ Config section: `[black]` default_repr={`False`} > -Don't use Black when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint` +Don't use Black when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint` diff --git a/versioned_docs/version-2.5/reference/subsystems/docformatter.mdx b/versioned_docs/version-2.5/reference/subsystems/docformatter.mdx index 3e2021ca9..1afb83b40 100644 --- a/versioned_docs/version-2.5/reference/subsystems/docformatter.mdx +++ b/versioned_docs/version-2.5/reference/subsystems/docformatter.mdx @@ -25,7 +25,7 @@ Config section: `[docformatter]` default_repr={`False`} > -Don't use docformatter when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use docformatter when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.5/reference/subsystems/flake8.mdx b/versioned_docs/version-2.5/reference/subsystems/flake8.mdx index 4563b2f0b..ab580d21c 100644 --- a/versioned_docs/version-2.5/reference/subsystems/flake8.mdx +++ b/versioned_docs/version-2.5/reference/subsystems/flake8.mdx @@ -25,7 +25,7 @@ Config section: `[flake8]` default_repr={`False`} > -Don't use Flake8 when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint` +Don't use Flake8 when running `/home/josh/work/scie-pants/dist/pants lint` diff --git a/versioned_docs/version-2.5/reference/subsystems/isort.mdx b/versioned_docs/version-2.5/reference/subsystems/isort.mdx index b1acddd27..9eafefd9d 100644 --- a/versioned_docs/version-2.5/reference/subsystems/isort.mdx +++ b/versioned_docs/version-2.5/reference/subsystems/isort.mdx @@ -25,7 +25,7 @@ Config section: `[isort]` default_repr={`False`} > -Don't use isort when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use isort when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.5/reference/subsystems/mypy.mdx b/versioned_docs/version-2.5/reference/subsystems/mypy.mdx index 619a93574..8d25b2260 100644 --- a/versioned_docs/version-2.5/reference/subsystems/mypy.mdx +++ b/versioned_docs/version-2.5/reference/subsystems/mypy.mdx @@ -25,7 +25,7 @@ Config section: `[mypy]` default_repr={`False`} > -Don't use MyPy when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 typecheck`. +Don't use MyPy when running `/home/josh/work/scie-pants/dist/pants typecheck`. diff --git a/versioned_docs/version-2.5/reference/subsystems/pylint.mdx b/versioned_docs/version-2.5/reference/subsystems/pylint.mdx index cf67484d0..a6c4158a3 100644 --- a/versioned_docs/version-2.5/reference/subsystems/pylint.mdx +++ b/versioned_docs/version-2.5/reference/subsystems/pylint.mdx @@ -25,7 +25,7 @@ Config section: `[pylint]` default_repr={`False`} > -Don't use Pylint when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint` +Don't use Pylint when running `/home/josh/work/scie-pants/dist/pants lint` diff --git a/versioned_docs/version-2.6/reference/help-all.json b/versioned_docs/version-2.6/reference/help-all.json index 42637b8b4..354e89d28 100644 --- a/versioned_docs/version-2.6/reference/help-all.json +++ b/versioned_docs/version-2.6/reference/help-all.json @@ -1528,7 +1528,7 @@ { "details": "from env var PANTS_BIN_NAME", "rank": "ENVIRONMENT", - "value": "/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64" + "value": "/home/josh/work/scie-pants/dist/pants" } ] } @@ -4059,7 +4059,7 @@ "deprecation_active": false, "display_args": ["--[no-]bandit-skip"], "env_var": "PANTS_BANDIT_SKIP", - "help": "Don't use Bandit when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`", + "help": "Don't use Bandit when running `/home/josh/work/scie-pants/dist/pants lint`", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--bandit-skip", "--no-bandit-skip"], @@ -4343,7 +4343,7 @@ "deprecation_active": false, "display_args": ["--[no-]black-skip"], "env_var": "PANTS_BLACK_SKIP", - "help": "Don't use Black when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`", + "help": "Don't use Black when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--black-skip", "--no-black-skip"], @@ -5311,7 +5311,7 @@ "deprecation_active": false, "display_args": ["--[no-]docformatter-skip"], "env_var": "PANTS_DOCFORMATTER_SKIP", - "help": "Don't use docformatter when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use docformatter when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -6065,7 +6065,7 @@ "deprecation_active": false, "display_args": ["--[no-]flake8-skip"], "env_var": "PANTS_FLAKE8_SKIP", - "help": "Don't use Flake8 when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`", + "help": "Don't use Flake8 when running `/home/josh/work/scie-pants/dist/pants lint`", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--flake8-skip", "--no-flake8-skip"], @@ -6710,7 +6710,7 @@ "deprecation_active": false, "display_args": ["--[no-]isort-skip"], "env_var": "PANTS_ISORT_SKIP", - "help": "Don't use isort when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use isort when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--isort-skip", "--no-isort-skip"], @@ -7386,7 +7386,7 @@ "deprecation_active": false, "display_args": ["--[no-]mypy-skip"], "env_var": "PANTS_MYPY_SKIP", - "help": "Don't use MyPy when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 typecheck`.", + "help": "Don't use MyPy when running `/home/josh/work/scie-pants/dist/pants typecheck`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--mypy-skip", "--no-mypy-skip"], @@ -8078,7 +8078,7 @@ "deprecation_active": false, "display_args": ["--[no-]pylint-skip"], "env_var": "PANTS_PYLINT_SKIP", - "help": "Don't use Pylint when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`", + "help": "Don't use Pylint when running `/home/josh/work/scie-pants/dist/pants lint`", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pylint-skip", "--no-pylint-skip"], diff --git a/versioned_docs/version-2.6/reference/subsystems/bandit.mdx b/versioned_docs/version-2.6/reference/subsystems/bandit.mdx index 0a23b747b..4bd876f69 100644 --- a/versioned_docs/version-2.6/reference/subsystems/bandit.mdx +++ b/versioned_docs/version-2.6/reference/subsystems/bandit.mdx @@ -25,7 +25,7 @@ Config section: `[bandit]` default_repr={`False`} > -Don't use Bandit when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint` +Don't use Bandit when running `/home/josh/work/scie-pants/dist/pants lint` diff --git a/versioned_docs/version-2.6/reference/subsystems/black.mdx b/versioned_docs/version-2.6/reference/subsystems/black.mdx index fe89e8330..68abbd0d5 100644 --- a/versioned_docs/version-2.6/reference/subsystems/black.mdx +++ b/versioned_docs/version-2.6/reference/subsystems/black.mdx @@ -25,7 +25,7 @@ Config section: `[black]` default_repr={`False`} > -Don't use Black when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint` +Don't use Black when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint` diff --git a/versioned_docs/version-2.6/reference/subsystems/docformatter.mdx b/versioned_docs/version-2.6/reference/subsystems/docformatter.mdx index 3e2021ca9..1afb83b40 100644 --- a/versioned_docs/version-2.6/reference/subsystems/docformatter.mdx +++ b/versioned_docs/version-2.6/reference/subsystems/docformatter.mdx @@ -25,7 +25,7 @@ Config section: `[docformatter]` default_repr={`False`} > -Don't use docformatter when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use docformatter when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.6/reference/subsystems/flake8.mdx b/versioned_docs/version-2.6/reference/subsystems/flake8.mdx index d7523812a..dc3acadee 100644 --- a/versioned_docs/version-2.6/reference/subsystems/flake8.mdx +++ b/versioned_docs/version-2.6/reference/subsystems/flake8.mdx @@ -25,7 +25,7 @@ Config section: `[flake8]` default_repr={`False`} > -Don't use Flake8 when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint` +Don't use Flake8 when running `/home/josh/work/scie-pants/dist/pants lint` diff --git a/versioned_docs/version-2.6/reference/subsystems/isort.mdx b/versioned_docs/version-2.6/reference/subsystems/isort.mdx index b1acddd27..9eafefd9d 100644 --- a/versioned_docs/version-2.6/reference/subsystems/isort.mdx +++ b/versioned_docs/version-2.6/reference/subsystems/isort.mdx @@ -25,7 +25,7 @@ Config section: `[isort]` default_repr={`False`} > -Don't use isort when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use isort when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.6/reference/subsystems/mypy.mdx b/versioned_docs/version-2.6/reference/subsystems/mypy.mdx index c550e99aa..5459ab5d9 100644 --- a/versioned_docs/version-2.6/reference/subsystems/mypy.mdx +++ b/versioned_docs/version-2.6/reference/subsystems/mypy.mdx @@ -25,7 +25,7 @@ Config section: `[mypy]` default_repr={`False`} > -Don't use MyPy when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 typecheck`. +Don't use MyPy when running `/home/josh/work/scie-pants/dist/pants typecheck`. diff --git a/versioned_docs/version-2.6/reference/subsystems/pylint.mdx b/versioned_docs/version-2.6/reference/subsystems/pylint.mdx index f8552de8c..467df74b8 100644 --- a/versioned_docs/version-2.6/reference/subsystems/pylint.mdx +++ b/versioned_docs/version-2.6/reference/subsystems/pylint.mdx @@ -25,7 +25,7 @@ Config section: `[pylint]` default_repr={`False`} > -Don't use Pylint when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint` +Don't use Pylint when running `/home/josh/work/scie-pants/dist/pants lint` diff --git a/versioned_docs/version-2.7/reference/help-all.json b/versioned_docs/version-2.7/reference/help-all.json index 9fcdcac20..4e4c05d81 100644 --- a/versioned_docs/version-2.7/reference/help-all.json +++ b/versioned_docs/version-2.7/reference/help-all.json @@ -1649,7 +1649,7 @@ { "details": "from env var PANTS_BIN_NAME", "rank": "ENVIRONMENT", - "value": "/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64" + "value": "/home/josh/work/scie-pants/dist/pants" } ] } @@ -4391,7 +4391,7 @@ "deprecation_active": false, "display_args": ["--[no-]bandit-skip"], "env_var": "PANTS_BANDIT_SKIP", - "help": "Don't use Bandit when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`", + "help": "Don't use Bandit when running `/home/josh/work/scie-pants/dist/pants lint`", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--bandit-skip", "--no-bandit-skip"], @@ -4706,7 +4706,7 @@ "deprecation_active": false, "display_args": ["--[no-]black-skip"], "env_var": "PANTS_BLACK_SKIP", - "help": "Don't use Black when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`", + "help": "Don't use Black when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--black-skip", "--no-black-skip"], @@ -5736,7 +5736,7 @@ "deprecation_active": false, "display_args": ["--[no-]docformatter-skip"], "env_var": "PANTS_DOCFORMATTER_SKIP", - "help": "Don't use docformatter when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use docformatter when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -6552,7 +6552,7 @@ "deprecation_active": false, "display_args": ["--[no-]flake8-skip"], "env_var": "PANTS_FLAKE8_SKIP", - "help": "Don't use Flake8 when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`", + "help": "Don't use Flake8 when running `/home/josh/work/scie-pants/dist/pants lint`", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--flake8-skip", "--no-flake8-skip"], @@ -7558,7 +7558,7 @@ "deprecation_active": false, "display_args": ["--[no-]isort-skip"], "env_var": "PANTS_ISORT_SKIP", - "help": "Don't use isort when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use isort when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--isort-skip", "--no-isort-skip"], @@ -8297,7 +8297,7 @@ "deprecation_active": false, "display_args": ["--[no-]mypy-skip"], "env_var": "PANTS_MYPY_SKIP", - "help": "Don't use MyPy when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 typecheck`.", + "help": "Don't use MyPy when running `/home/josh/work/scie-pants/dist/pants typecheck`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--mypy-skip", "--no-mypy-skip"], @@ -9403,7 +9403,7 @@ "deprecation_active": false, "display_args": ["--[no-]pylint-skip"], "env_var": "PANTS_PYLINT_SKIP", - "help": "Don't use Pylint when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`", + "help": "Don't use Pylint when running `/home/josh/work/scie-pants/dist/pants lint`", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pylint-skip", "--no-pylint-skip"], @@ -12707,7 +12707,7 @@ "deprecation_active": false, "display_args": ["--[no-]yapf-skip"], "env_var": "PANTS_YAPF_SKIP", - "help": "Don't use yapf when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use yapf when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--yapf-skip", "--no-yapf-skip"], diff --git a/versioned_docs/version-2.7/reference/subsystems/bandit.mdx b/versioned_docs/version-2.7/reference/subsystems/bandit.mdx index 7eed189f2..3b06730e9 100644 --- a/versioned_docs/version-2.7/reference/subsystems/bandit.mdx +++ b/versioned_docs/version-2.7/reference/subsystems/bandit.mdx @@ -25,7 +25,7 @@ Config section: `[bandit]` default_repr={`False`} > -Don't use Bandit when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint` +Don't use Bandit when running `/home/josh/work/scie-pants/dist/pants lint` diff --git a/versioned_docs/version-2.7/reference/subsystems/black.mdx b/versioned_docs/version-2.7/reference/subsystems/black.mdx index 6e8185f99..24b6b1ece 100644 --- a/versioned_docs/version-2.7/reference/subsystems/black.mdx +++ b/versioned_docs/version-2.7/reference/subsystems/black.mdx @@ -25,7 +25,7 @@ Config section: `[black]` default_repr={`False`} > -Don't use Black when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint` +Don't use Black when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint` diff --git a/versioned_docs/version-2.7/reference/subsystems/docformatter.mdx b/versioned_docs/version-2.7/reference/subsystems/docformatter.mdx index e2d6b1e08..c10b854c3 100644 --- a/versioned_docs/version-2.7/reference/subsystems/docformatter.mdx +++ b/versioned_docs/version-2.7/reference/subsystems/docformatter.mdx @@ -25,7 +25,7 @@ Config section: `[docformatter]` default_repr={`False`} > -Don't use docformatter when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use docformatter when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.7/reference/subsystems/flake8.mdx b/versioned_docs/version-2.7/reference/subsystems/flake8.mdx index 35d54357f..33820d5ba 100644 --- a/versioned_docs/version-2.7/reference/subsystems/flake8.mdx +++ b/versioned_docs/version-2.7/reference/subsystems/flake8.mdx @@ -25,7 +25,7 @@ Config section: `[flake8]` default_repr={`False`} > -Don't use Flake8 when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint` +Don't use Flake8 when running `/home/josh/work/scie-pants/dist/pants lint` diff --git a/versioned_docs/version-2.7/reference/subsystems/isort.mdx b/versioned_docs/version-2.7/reference/subsystems/isort.mdx index 7f9998f1e..1521c9c3b 100644 --- a/versioned_docs/version-2.7/reference/subsystems/isort.mdx +++ b/versioned_docs/version-2.7/reference/subsystems/isort.mdx @@ -25,7 +25,7 @@ Config section: `[isort]` default_repr={`False`} > -Don't use isort when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use isort when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.7/reference/subsystems/mypy.mdx b/versioned_docs/version-2.7/reference/subsystems/mypy.mdx index 3783e340b..b91f9d097 100644 --- a/versioned_docs/version-2.7/reference/subsystems/mypy.mdx +++ b/versioned_docs/version-2.7/reference/subsystems/mypy.mdx @@ -25,7 +25,7 @@ Config section: `[mypy]` default_repr={`False`} > -Don't use MyPy when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 typecheck`. +Don't use MyPy when running `/home/josh/work/scie-pants/dist/pants typecheck`. diff --git a/versioned_docs/version-2.7/reference/subsystems/pylint.mdx b/versioned_docs/version-2.7/reference/subsystems/pylint.mdx index 9a4f8f889..104b8b58d 100644 --- a/versioned_docs/version-2.7/reference/subsystems/pylint.mdx +++ b/versioned_docs/version-2.7/reference/subsystems/pylint.mdx @@ -25,7 +25,7 @@ Config section: `[pylint]` default_repr={`False`} > -Don't use Pylint when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint` +Don't use Pylint when running `/home/josh/work/scie-pants/dist/pants lint` diff --git a/versioned_docs/version-2.7/reference/subsystems/yapf.mdx b/versioned_docs/version-2.7/reference/subsystems/yapf.mdx index 00b7b77fe..0fb033d24 100644 --- a/versioned_docs/version-2.7/reference/subsystems/yapf.mdx +++ b/versioned_docs/version-2.7/reference/subsystems/yapf.mdx @@ -25,7 +25,7 @@ Config section: `[yapf]` default_repr={`False`} > -Don't use yapf when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use yapf when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.8/reference/help-all.json b/versioned_docs/version-2.8/reference/help-all.json index 3211d9f33..bfab8d316 100644 --- a/versioned_docs/version-2.8/reference/help-all.json +++ b/versioned_docs/version-2.8/reference/help-all.json @@ -2716,7 +2716,7 @@ { "details": "from env var PANTS_BIN_NAME", "rank": "ENVIRONMENT", - "value": "/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64" + "value": "/home/josh/work/scie-pants/dist/pants" } ] } @@ -5434,7 +5434,7 @@ "deprecation_active": false, "display_args": ["--[no-]autoflake-skip"], "env_var": "PANTS_AUTOFLAKE_SKIP", - "help": "Don't use Autoflake when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`", + "help": "Don't use Autoflake when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--autoflake-skip", "--no-autoflake-skip"], @@ -5681,7 +5681,7 @@ "deprecation_active": false, "display_args": ["--[no-]bandit-skip"], "env_var": "PANTS_BANDIT_SKIP", - "help": "Don't use Bandit when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`", + "help": "Don't use Bandit when running `/home/josh/work/scie-pants/dist/pants lint`", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--bandit-skip", "--no-bandit-skip"], @@ -5996,7 +5996,7 @@ "deprecation_active": false, "display_args": ["--[no-]black-skip"], "env_var": "PANTS_BLACK_SKIP", - "help": "Don't use Black when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`", + "help": "Don't use Black when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--black-skip", "--no-black-skip"], @@ -7334,7 +7334,7 @@ "deprecation_active": false, "display_args": ["--[no-]docformatter-skip"], "env_var": "PANTS_DOCFORMATTER_SKIP", - "help": "Don't use docformatter when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use docformatter when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -8420,7 +8420,7 @@ "deprecation_active": false, "display_args": ["--[no-]flake8-skip"], "env_var": "PANTS_FLAKE8_SKIP", - "help": "Don't use Flake8 when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`", + "help": "Don't use Flake8 when running `/home/josh/work/scie-pants/dist/pants lint`", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--flake8-skip", "--no-flake8-skip"], @@ -8642,7 +8642,7 @@ "deprecation_active": false, "display_args": ["--[no-]gofmt-skip"], "env_var": "PANTS_GOFMT_SKIP", - "help": "Don't use gofmt when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use gofmt when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--gofmt-skip", "--no-gofmt-skip"], @@ -9393,7 +9393,7 @@ "deprecation_active": false, "display_args": ["--[no-]isort-skip"], "env_var": "PANTS_ISORT_SKIP", - "help": "Don't use isort when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use isort when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--isort-skip", "--no-isort-skip"], @@ -10296,7 +10296,7 @@ "deprecation_active": false, "display_args": ["--[no-]mypy-skip"], "env_var": "PANTS_MYPY_SKIP", - "help": "Don't use MyPy when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 typecheck`.", + "help": "Don't use MyPy when running `/home/josh/work/scie-pants/dist/pants typecheck`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--mypy-skip", "--no-mypy-skip"], @@ -11442,7 +11442,7 @@ "deprecation_active": false, "display_args": ["--[no-]pylint-skip"], "env_var": "PANTS_PYLINT_SKIP", - "help": "Don't use Pylint when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`", + "help": "Don't use Pylint when running `/home/josh/work/scie-pants/dist/pants lint`", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pylint-skip", "--no-pylint-skip"], @@ -13466,7 +13466,7 @@ "deprecation_active": false, "display_args": ["--[no-]pyupgrade-skip"], "env_var": "PANTS_PYUPGRADE_SKIP", - "help": "Don't use pyupgrade when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use pyupgrade when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pyupgrade-skip", "--no-pyupgrade-skip"], @@ -16151,7 +16151,7 @@ "deprecation_active": false, "display_args": ["--[no-]yapf-skip"], "env_var": "PANTS_YAPF_SKIP", - "help": "Don't use yapf when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use yapf when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--yapf-skip", "--no-yapf-skip"], diff --git a/versioned_docs/version-2.8/reference/subsystems/autoflake.mdx b/versioned_docs/version-2.8/reference/subsystems/autoflake.mdx index 1fa9c6134..f1dfeaa19 100644 --- a/versioned_docs/version-2.8/reference/subsystems/autoflake.mdx +++ b/versioned_docs/version-2.8/reference/subsystems/autoflake.mdx @@ -25,7 +25,7 @@ Config section: `[autoflake]` default_repr={`False`} > -Don't use Autoflake when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint` +Don't use Autoflake when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint` diff --git a/versioned_docs/version-2.8/reference/subsystems/bandit.mdx b/versioned_docs/version-2.8/reference/subsystems/bandit.mdx index 0f6618f5e..3ffe0b970 100644 --- a/versioned_docs/version-2.8/reference/subsystems/bandit.mdx +++ b/versioned_docs/version-2.8/reference/subsystems/bandit.mdx @@ -25,7 +25,7 @@ Config section: `[bandit]` default_repr={`False`} > -Don't use Bandit when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint` +Don't use Bandit when running `/home/josh/work/scie-pants/dist/pants lint` diff --git a/versioned_docs/version-2.8/reference/subsystems/black.mdx b/versioned_docs/version-2.8/reference/subsystems/black.mdx index efee8d842..9daa3dfe6 100644 --- a/versioned_docs/version-2.8/reference/subsystems/black.mdx +++ b/versioned_docs/version-2.8/reference/subsystems/black.mdx @@ -25,7 +25,7 @@ Config section: `[black]` default_repr={`False`} > -Don't use Black when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint` +Don't use Black when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint` diff --git a/versioned_docs/version-2.8/reference/subsystems/docformatter.mdx b/versioned_docs/version-2.8/reference/subsystems/docformatter.mdx index 7f75e7585..733ce3204 100644 --- a/versioned_docs/version-2.8/reference/subsystems/docformatter.mdx +++ b/versioned_docs/version-2.8/reference/subsystems/docformatter.mdx @@ -25,7 +25,7 @@ Config section: `[docformatter]` default_repr={`False`} > -Don't use docformatter when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use docformatter when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.8/reference/subsystems/flake8.mdx b/versioned_docs/version-2.8/reference/subsystems/flake8.mdx index 07d5e0a85..aa286ded3 100644 --- a/versioned_docs/version-2.8/reference/subsystems/flake8.mdx +++ b/versioned_docs/version-2.8/reference/subsystems/flake8.mdx @@ -25,7 +25,7 @@ Config section: `[flake8]` default_repr={`False`} > -Don't use Flake8 when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint` +Don't use Flake8 when running `/home/josh/work/scie-pants/dist/pants lint` diff --git a/versioned_docs/version-2.8/reference/subsystems/gofmt.mdx b/versioned_docs/version-2.8/reference/subsystems/gofmt.mdx index c8bc1a80a..2f97e9620 100644 --- a/versioned_docs/version-2.8/reference/subsystems/gofmt.mdx +++ b/versioned_docs/version-2.8/reference/subsystems/gofmt.mdx @@ -25,7 +25,7 @@ Config section: `[gofmt]` default_repr={`False`} > -Don't use gofmt when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use gofmt when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.8/reference/subsystems/isort.mdx b/versioned_docs/version-2.8/reference/subsystems/isort.mdx index b85ed183a..97407a513 100644 --- a/versioned_docs/version-2.8/reference/subsystems/isort.mdx +++ b/versioned_docs/version-2.8/reference/subsystems/isort.mdx @@ -25,7 +25,7 @@ Config section: `[isort]` default_repr={`False`} > -Don't use isort when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use isort when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.8/reference/subsystems/mypy.mdx b/versioned_docs/version-2.8/reference/subsystems/mypy.mdx index a23091583..fe31cc540 100644 --- a/versioned_docs/version-2.8/reference/subsystems/mypy.mdx +++ b/versioned_docs/version-2.8/reference/subsystems/mypy.mdx @@ -25,7 +25,7 @@ Config section: `[mypy]` default_repr={`False`} > -Don't use MyPy when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 typecheck`. +Don't use MyPy when running `/home/josh/work/scie-pants/dist/pants typecheck`. diff --git a/versioned_docs/version-2.8/reference/subsystems/pylint.mdx b/versioned_docs/version-2.8/reference/subsystems/pylint.mdx index 0f6aeab64..af316da9b 100644 --- a/versioned_docs/version-2.8/reference/subsystems/pylint.mdx +++ b/versioned_docs/version-2.8/reference/subsystems/pylint.mdx @@ -25,7 +25,7 @@ Config section: `[pylint]` default_repr={`False`} > -Don't use Pylint when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint` +Don't use Pylint when running `/home/josh/work/scie-pants/dist/pants lint` diff --git a/versioned_docs/version-2.8/reference/subsystems/pyupgrade.mdx b/versioned_docs/version-2.8/reference/subsystems/pyupgrade.mdx index 794ac0ef5..338537cda 100644 --- a/versioned_docs/version-2.8/reference/subsystems/pyupgrade.mdx +++ b/versioned_docs/version-2.8/reference/subsystems/pyupgrade.mdx @@ -25,7 +25,7 @@ Config section: `[pyupgrade]` default_repr={`False`} > -Don't use pyupgrade when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use pyupgrade when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.8/reference/subsystems/yapf.mdx b/versioned_docs/version-2.8/reference/subsystems/yapf.mdx index 6f7535111..c0da7944c 100644 --- a/versioned_docs/version-2.8/reference/subsystems/yapf.mdx +++ b/versioned_docs/version-2.8/reference/subsystems/yapf.mdx @@ -25,7 +25,7 @@ Config section: `[yapf]` default_repr={`False`} > -Don't use yapf when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use yapf when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.9/reference/help-all.json b/versioned_docs/version-2.9/reference/help-all.json index fce570605..d32908e81 100644 --- a/versioned_docs/version-2.9/reference/help-all.json +++ b/versioned_docs/version-2.9/reference/help-all.json @@ -3303,7 +3303,7 @@ { "details": "from env var PANTS_BIN_NAME", "rank": "ENVIRONMENT", - "value": "/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64" + "value": "/home/josh/work/scie-pants/dist/pants" } ] } @@ -6086,7 +6086,7 @@ "deprecation_active": false, "display_args": ["--[no-]autoflake-skip"], "env_var": "PANTS_AUTOFLAKE_SKIP", - "help": "Don't use Autoflake when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`", + "help": "Don't use Autoflake when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--autoflake-skip", "--no-autoflake-skip"], @@ -6333,7 +6333,7 @@ "deprecation_active": false, "display_args": ["--[no-]bandit-skip"], "env_var": "PANTS_BANDIT_SKIP", - "help": "Don't use Bandit when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`", + "help": "Don't use Bandit when running `/home/josh/work/scie-pants/dist/pants lint`", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--bandit-skip", "--no-bandit-skip"], @@ -6648,7 +6648,7 @@ "deprecation_active": false, "display_args": ["--[no-]black-skip"], "env_var": "PANTS_BLACK_SKIP", - "help": "Don't use Black when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`", + "help": "Don't use Black when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--black-skip", "--no-black-skip"], @@ -7989,7 +7989,7 @@ "deprecation_active": false, "display_args": ["--[no-]docformatter-skip"], "env_var": "PANTS_DOCFORMATTER_SKIP", - "help": "Don't use docformatter when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use docformatter when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -9146,7 +9146,7 @@ "deprecation_active": false, "display_args": ["--[no-]flake8-skip"], "env_var": "PANTS_FLAKE8_SKIP", - "help": "Don't use Flake8 when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`", + "help": "Don't use Flake8 when running `/home/josh/work/scie-pants/dist/pants lint`", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--flake8-skip", "--no-flake8-skip"], @@ -9368,7 +9368,7 @@ "deprecation_active": false, "display_args": ["--[no-]gofmt-skip"], "env_var": "PANTS_GOFMT_SKIP", - "help": "Don't use gofmt when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use gofmt when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--gofmt-skip", "--no-gofmt-skip"], @@ -9615,7 +9615,7 @@ "deprecation_active": false, "display_args": ["--[no-]google-java-format-skip"], "env_var": "PANTS_GOOGLE_JAVA_FORMAT_SKIP", - "help": "Don't use Google Java Format when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`", + "help": "Don't use Google Java Format when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": [ @@ -10639,7 +10639,7 @@ "deprecation_active": false, "display_args": ["--[no-]isort-skip"], "env_var": "PANTS_ISORT_SKIP", - "help": "Don't use isort when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use isort when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--isort-skip", "--no-isort-skip"], @@ -11878,7 +11878,7 @@ "deprecation_active": false, "display_args": ["--[no-]mypy-skip"], "env_var": "PANTS_MYPY_SKIP", - "help": "Don't use MyPy when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 typecheck`.", + "help": "Don't use MyPy when running `/home/josh/work/scie-pants/dist/pants typecheck`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--mypy-skip", "--no-mypy-skip"], @@ -13156,7 +13156,7 @@ "deprecation_active": false, "display_args": ["--[no-]pylint-skip"], "env_var": "PANTS_PYLINT_SKIP", - "help": "Don't use Pylint when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`", + "help": "Don't use Pylint when running `/home/josh/work/scie-pants/dist/pants lint`", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pylint-skip", "--no-pylint-skip"], @@ -15339,7 +15339,7 @@ "deprecation_active": false, "display_args": ["--[no-]pyupgrade-skip"], "env_var": "PANTS_PYUPGRADE_SKIP", - "help": "Don't use pyupgrade when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use pyupgrade when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--pyupgrade-skip", "--no-pyupgrade-skip"], @@ -15995,7 +15995,7 @@ "deprecation_active": false, "display_args": ["--[no-]scalafmt-skip"], "env_var": "PANTS_SCALAFMT_SKIP", - "help": "Don't use `scalafmt` when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`", + "help": "Don't use `scalafmt` when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--scalafmt-skip", "--no-scalafmt-skip"], @@ -18606,7 +18606,7 @@ "deprecation_active": false, "display_args": ["--[no-]yapf-skip"], "env_var": "PANTS_YAPF_SKIP", - "help": "Don't use yapf when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`.", + "help": "Don't use yapf when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.", "removal_hint": null, "removal_version": null, "scoped_cmd_line_args": ["--yapf-skip", "--no-yapf-skip"], diff --git a/versioned_docs/version-2.9/reference/subsystems/autoflake.mdx b/versioned_docs/version-2.9/reference/subsystems/autoflake.mdx index 67ec0d126..493107dbd 100644 --- a/versioned_docs/version-2.9/reference/subsystems/autoflake.mdx +++ b/versioned_docs/version-2.9/reference/subsystems/autoflake.mdx @@ -25,7 +25,7 @@ Config section: `[autoflake]` default_repr={`False`} > -Don't use Autoflake when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint` +Don't use Autoflake when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint` diff --git a/versioned_docs/version-2.9/reference/subsystems/bandit.mdx b/versioned_docs/version-2.9/reference/subsystems/bandit.mdx index 273737563..3c9504399 100644 --- a/versioned_docs/version-2.9/reference/subsystems/bandit.mdx +++ b/versioned_docs/version-2.9/reference/subsystems/bandit.mdx @@ -25,7 +25,7 @@ Config section: `[bandit]` default_repr={`False`} > -Don't use Bandit when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint` +Don't use Bandit when running `/home/josh/work/scie-pants/dist/pants lint` diff --git a/versioned_docs/version-2.9/reference/subsystems/black.mdx b/versioned_docs/version-2.9/reference/subsystems/black.mdx index 0e18a787a..3858680d4 100644 --- a/versioned_docs/version-2.9/reference/subsystems/black.mdx +++ b/versioned_docs/version-2.9/reference/subsystems/black.mdx @@ -25,7 +25,7 @@ Config section: `[black]` default_repr={`False`} > -Don't use Black when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint` +Don't use Black when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint` diff --git a/versioned_docs/version-2.9/reference/subsystems/docformatter.mdx b/versioned_docs/version-2.9/reference/subsystems/docformatter.mdx index 7983095c3..909652284 100644 --- a/versioned_docs/version-2.9/reference/subsystems/docformatter.mdx +++ b/versioned_docs/version-2.9/reference/subsystems/docformatter.mdx @@ -25,7 +25,7 @@ Config section: `[docformatter]` default_repr={`False`} > -Don't use docformatter when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use docformatter when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.9/reference/subsystems/flake8.mdx b/versioned_docs/version-2.9/reference/subsystems/flake8.mdx index b8b57add6..ef43a8be7 100644 --- a/versioned_docs/version-2.9/reference/subsystems/flake8.mdx +++ b/versioned_docs/version-2.9/reference/subsystems/flake8.mdx @@ -25,7 +25,7 @@ Config section: `[flake8]` default_repr={`False`} > -Don't use Flake8 when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint` +Don't use Flake8 when running `/home/josh/work/scie-pants/dist/pants lint` diff --git a/versioned_docs/version-2.9/reference/subsystems/gofmt.mdx b/versioned_docs/version-2.9/reference/subsystems/gofmt.mdx index c8bc1a80a..2f97e9620 100644 --- a/versioned_docs/version-2.9/reference/subsystems/gofmt.mdx +++ b/versioned_docs/version-2.9/reference/subsystems/gofmt.mdx @@ -25,7 +25,7 @@ Config section: `[gofmt]` default_repr={`False`} > -Don't use gofmt when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use gofmt when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.9/reference/subsystems/google-java-format.mdx b/versioned_docs/version-2.9/reference/subsystems/google-java-format.mdx index 837694fc3..43ec34991 100644 --- a/versioned_docs/version-2.9/reference/subsystems/google-java-format.mdx +++ b/versioned_docs/version-2.9/reference/subsystems/google-java-format.mdx @@ -25,7 +25,7 @@ Config section: `[google-java-format]` default_repr={`False`} > -Don't use Google Java Format when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint` +Don't use Google Java Format when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint` diff --git a/versioned_docs/version-2.9/reference/subsystems/isort.mdx b/versioned_docs/version-2.9/reference/subsystems/isort.mdx index 33b5e66a1..12582c821 100644 --- a/versioned_docs/version-2.9/reference/subsystems/isort.mdx +++ b/versioned_docs/version-2.9/reference/subsystems/isort.mdx @@ -25,7 +25,7 @@ Config section: `[isort]` default_repr={`False`} > -Don't use isort when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use isort when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.9/reference/subsystems/mypy.mdx b/versioned_docs/version-2.9/reference/subsystems/mypy.mdx index 613116d0f..9cfdce602 100644 --- a/versioned_docs/version-2.9/reference/subsystems/mypy.mdx +++ b/versioned_docs/version-2.9/reference/subsystems/mypy.mdx @@ -25,7 +25,7 @@ Config section: `[mypy]` default_repr={`False`} > -Don't use MyPy when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 typecheck`. +Don't use MyPy when running `/home/josh/work/scie-pants/dist/pants typecheck`. diff --git a/versioned_docs/version-2.9/reference/subsystems/pylint.mdx b/versioned_docs/version-2.9/reference/subsystems/pylint.mdx index 846f4c692..05ff0994d 100644 --- a/versioned_docs/version-2.9/reference/subsystems/pylint.mdx +++ b/versioned_docs/version-2.9/reference/subsystems/pylint.mdx @@ -25,7 +25,7 @@ Config section: `[pylint]` default_repr={`False`} > -Don't use Pylint when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint` +Don't use Pylint when running `/home/josh/work/scie-pants/dist/pants lint` diff --git a/versioned_docs/version-2.9/reference/subsystems/pyupgrade.mdx b/versioned_docs/version-2.9/reference/subsystems/pyupgrade.mdx index 1e1dae3ea..64fef3ab5 100644 --- a/versioned_docs/version-2.9/reference/subsystems/pyupgrade.mdx +++ b/versioned_docs/version-2.9/reference/subsystems/pyupgrade.mdx @@ -25,7 +25,7 @@ Config section: `[pyupgrade]` default_repr={`False`} > -Don't use pyupgrade when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use pyupgrade when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`. diff --git a/versioned_docs/version-2.9/reference/subsystems/scalafmt.mdx b/versioned_docs/version-2.9/reference/subsystems/scalafmt.mdx index 8a38b5824..d01c19c58 100644 --- a/versioned_docs/version-2.9/reference/subsystems/scalafmt.mdx +++ b/versioned_docs/version-2.9/reference/subsystems/scalafmt.mdx @@ -25,7 +25,7 @@ Config section: `[scalafmt]` default_repr={`False`} > -Don't use `scalafmt` when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint` +Don't use `scalafmt` when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint` diff --git a/versioned_docs/version-2.9/reference/subsystems/yapf.mdx b/versioned_docs/version-2.9/reference/subsystems/yapf.mdx index eb120af42..d839c9c12 100644 --- a/versioned_docs/version-2.9/reference/subsystems/yapf.mdx +++ b/versioned_docs/version-2.9/reference/subsystems/yapf.mdx @@ -25,7 +25,7 @@ Config section: `[yapf]` default_repr={`False`} > -Don't use yapf when running `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 fmt` and `/home/josh/work/scie-pants/dist/scie-pants-linux-x86_64 lint`. +Don't use yapf when running `/home/josh/work/scie-pants/dist/pants fmt` and `/home/josh/work/scie-pants/dist/pants lint`.