Upgrade to Pants 2.10 (#91)

Author: Eric-Arellano

.github/workflows/pants.yaml

@@ -49,7 +49,7 @@ jobs:
       run: ./pants tailor --check update-build-files --check
     - name: Lint and typecheck
       run: | 
-        ./pants lint typecheck ::
+        ./pants lint check ::
     - name: Test
       run: |
         ./pants test ::

BUILD

@@ -4,4 +4,4 @@
 # A macro that turns every entry in this directory's requirements.txt into a
 # `python_requirement_library` target. Refer to
 # https://www.pantsbuild.org/docs/python-third-party-dependencies.
-python_requirements()
+python_requirements(name="reqs")

README.md

@@ -26,7 +26,7 @@ Pants commands are called _goals_. You can get a list of goals with
 # Targets
 
 Targets are a way of setting metadata for some part of your code, such as timeouts for tests and 
-entry points for binaries. Targets have types like `python_binary`, `resources`, and 
+entry points for binaries. Targets have types like `python_source`, `resources`, and 
 `pex_binary`. They are defined in `BUILD` files.
 
 Pants goals can be invoked on targets or directly on source files (which is often more intuitive and convenient).
@@ -78,12 +78,6 @@ Targets are referenced on the command line using their address, of the form `pat
 ./pants lint helloworld/util:util
 ```
 
-You can omit the target name if it is the same as the immediately enclosing directory name, e.g.,
-
-```
-./pants lint helloworld/util
-```
-
 You can glob over all targets in a directory with a single trailing `:`, or over all targets in a directory
 and all its subdirectories with a double trailing `::`, e.g.,
 
@@ -103,11 +97,6 @@ those, rather than error. So you can safely do things like
 
 To run all tests.
 
-In some cases trying to run a goal on multiple files or targets will fail due to conflicts. For example, you cannot
-`./pants repl helloworld::` because that globs over both Python 2 and Python 3 code, so there is
-no way to select an interpreter compatible with both both to run the REPL on.
-
-
 # Example Goals
 
 Try these out in this repo!
@@ -123,13 +112,13 @@ Try these out in this repo!
 
 ```
 ./pants lint ::
-./pants fmt 'helloworld/**/*.py'
+./pants fmt helloworld/greet::
 ```
 
 ## Run MyPy
 
 ```
-./pants typecheck ::
+./pants check ::
 ```
 
 ## Run tests
@@ -157,7 +146,7 @@ Try these out in this repo!
 
 ```
 ./pants repl helloworld/greet  # The REPL will have all relevant code and dependencies on its sys.path.
-./pants repl --shell=ipython helloworld/greet
+./pants repl --shell=ipython helloworld/greet --no-pantsd  # To use IPython, you must disable Pantsd for now.
 ```
 
 ## Build a wheel / generate `setup.py`
@@ -168,11 +157,13 @@ This will build both a `.whl` bdist and a `.tar.gz` sdist.
 ./pants package helloworld/util:dist
 ```
 
-We can also remove the `setup_py_commands` field from `helloworld/util/BUILD` to have Pants instead generate a 
-`setup.py` file, with all the relevant code in a chroot.
-
 ## Count lines of code
 
 ```
 ./pants count-loc '**/*'
 ```
+## Create virtualenv for IDE integration
+
+```
+./pants export ::
+```

build-support/generate_constraints.sh

@@ -3,8 +3,8 @@
 
 # This target sets the metadata for all the Python non-test files in this directory.
 #
-# * Pants cannot infer dependencies on `resource` / `resources` targets, so we explicitly add the
-#   dep.
+# * Pants cannot yet infer dependencies on `resource` / `resources` targets, so we explicitly add
+#   the dep.
 python_sources(
     name="lib",
     dependencies=[":translations"],

constraints.txt

@@ -0,0 +1,27 @@
+# This lockfile was autogenerated by Pants. To regenerate, run:
+#
+#    ./pants generate-lockfiles --resolve=python-default
+#
+# --- BEGIN PANTS LOCKFILE METADATA: DO NOT EDIT OR REMOVE ---
+# {
+#   "version": 2,
+#   "valid_for_interpreter_constraints": [
+#     "CPython>=3.7"
+#   ],
+#   "generated_with_requirements": [
+#     "ansicolors==1.1.8",
+#     "setuptools<57,>=56.2.0",
+#     "types-setuptools<58,>=56.2.0"
+#   ]
+# }
+# --- END PANTS LOCKFILE METADATA ---
+
+ansicolors==1.1.8 \
+    --hash=sha256:00d2dde5a675579325902536738dd27e4fac1fd68f773fe36c21044eb559e187 \
+    --hash=sha256:99f94f5e3348a0bcd43c82e5fc4414013ccc19d70bd939ad71e0133ce9c372e0
+setuptools==56.2.0; python_version >= "3.6" \
+    --hash=sha256:bc30153eec47d82f20c6f5e1a13d4ee725c6deb7013a67557f89bfe5d25235c4 \
+    --hash=sha256:7bb5652625e94e73b9358b7ed8c6431b732e80cf31f4e0972294c64f0e5b849e
+types-setuptools==57.4.9 \
+    --hash=sha256:536ef74744f8e1e4be4fc719887f886e74e4cf3c792b4a06984320be4df450b5 \
+    --hash=sha256:948dc6863373750e2cd0b223a84f1fb608414cde5e55cf38ea657b93aeb411d2

helloworld/greet/BUILD

@@ -2,7 +2,7 @@
 # Licensed under the Apache License, Version 2.0 (see LICENSE).
 
 [GLOBAL]
-pants_version = "2.9.0"
+pants_version = "2.10.0rc0"
 backend_packages.add = [
   "pants.backend.python",
   "pants.backend.python.lint.docformatter",
@@ -12,6 +12,11 @@ backend_packages.add = [
   "pants.backend.python.typecheck.mypy",
 ]
 
+# This will become the default in 2.11, and is only explicitly set to not break
+# backwards-compatibility for existing users. If you are setting up Pants for
+# the first time, set this to false.
+use_deprecated_python_macros = false
+
 [anonymous-telemetry]
 enabled = true
 repo_id = "3B1D361B-E9F1-49A8-B761-03DCC41FD58E"
@@ -24,9 +29,14 @@ root_patterns = ["/"]
 # The default interpreter compatibility for code in this repo. Individual targets can override
 #  this with the `interpreter_constraints` field. See
 #  https://www.pantsbuild.org/docs/python-interpreter-compatibility.
+#
+# If you use Apple Silicon, set to a value like `>=3.9`.
 interpreter_constraints = [">=3.7"]
-# Use a constraints file. See https://www.pantsbuild.org/docs/python-third-party-dependencies.
-requirement_constraints = "constraints.txt"
+
+# Enable the "resolves" mechanism, which allows you to have multiple lockfiles and for Pants to
+# generate the lockfiles for you. See https://www.pantsbuild.org/docs/python-third-party-dependencies.
+enable_resolves = true
+resolves = { python-default = "lockfile.txt"}
 
 [python-bootstrap]
 # We search for interpreters on both on the $PATH and in the `$(pyenv root)/versions` folder.