scie-pants 0.5.4

---

0.5.4

Support using pants from sources also from a projects subtree not only the project root.

scie-pants 0.5.3

---

0.5.3

This release fixes scie-pants caching of Pants installs. Previously a given version of Pants was
not fully cached and scie-pants would do un-necessary network requests when re-using the already
installed Pants version from a project directory different from the initial installation project
directory. Now a given version of Pants is fully cached per-user (really per SCIE_BASE, which
defaults to a cache directory under the user's HOME dir).

scie-pants 0.5.2

---

0.5.2

This release fixes scie-pants to interoperate with pants run --debug-adapter. Previously, if
there was no custom [debugpy] version configured, scie-pants would cause Pants to error by
passing the empty string as the debugpy version requirement string via PANTS_DEBUGPY_VERSION=.

scie-pants 0.5.1

---

0.5.1

This release silences Pip notifications about new Pip versions being available. The Pip used by
scie-pants is for a one-time install of a Pants in a venv and the version of Pip that ships with
the hermetic Python Build Standalone interpreters suffices for this purpose.

scie-pants 0.5.0

---

0.5.0

This release improves scie-pants operation with Pants help by ensuring the command line you used
to invoke Pants is accurately reflected in the help information Pants presents back to you.

scie-pants 0.4.2

---

0.4.2

This release fixes .pants.bootstrap handling to robustly mimic handling by the ./pants script.
The scie-pants binary now re-execs itself through a bash shell when .pants.bootstrap needs to
be sourced.

scie-pants 0.4.1

---

0.4.1

This release supports using a released Pants version in the Pants repo when a Pants version to use
is defined, treating it as any other project that use Pants as build system.

scie-pants 0.4.0

---

0.4.0

This release supports use of the scie-pants binary in the Pants repo being defaulted to
PANTS_SOURCE=. pants behavior; i.e.: If you run pants in the Pants repo, it will do what you
probably expect: not run Pants from a released version (since the Pants repo specifies none), not
prompt you to set pants_version (because that's almost surely not what you want), but run Pants
from the local repo sources.

scie-pants 0.3.2

---

0.3.2

This release fixes the Pants from sources feature added in 0.3.0 to forward command line arguments
to the Pants run from sources correctly. Previously the argument list passed was doubled.

scie-pants 0.3.0

---

0.3.0

This release adds support for running Pants from a local Pants clone. This is useful for testing out
unreleased Pants changes.

This feature used to be provided by a bespoke pants_from_sources script copied around to various
repositories; an example of which is here.

There are two ways to activate this mode:

1. Execute pants with the PANTS_SOURCE environment variable set as the path to the Pants repo
   whose Pants code you'd like to run against your repo.
2. Copy, hardlink or symlink your pants binary to pants_from_sources and execute that.

The first activation method is new. The second mode follows the bespoke ./pants_from_sources
conventions and assumes PANTS_SOURCE=../pants. You can override that by setting thePANTS_SOURCE
env var as in the first activation method.