sentry-devenv 1.20.0__tar.gz → 1.21.0__tar.gz

{sentry_devenv-1.20.0 → sentry_devenv-1.21.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: sentry_devenv
-Version: 1.20.0
+Version: 1.21.0
 Summary: Utilities for setting up a Sentry development environment
 Author-email: Joshua Li <joshua.li@sentry.io>, Ian Woodard <ian.woodard@sentry.io>, Buck Evan <buck.evan@sentry.io>
 Classifier: Programming Language :: Python :: 3
@@ -47,7 +47,6 @@ To update this installation, run `devenv update`.
 
 This is intended for initial setup of a new machine.
 
-
 `devenv fetch [repository name]`
 
 Any repository on github in the form of `[org]/[reponame]`
@@ -71,7 +70,6 @@ In general, our library is designed to isolate, as much as possible, a repo's de
 For example, [gcloud](#gcloud) is installed to `[reporoot]/.devenv/bin/gcloud` (with the gcloud sdk at `[reporoot]/.devenv/bin/google-cloud-sdk`).
 An exception to this would be python virtualenvs, which was implemented before the idea of `[reporoot]/.devenv`.
 
-
 `devenv doctor`
 
 Use this to diagnose and fix common issues.
@@ -79,14 +77,25 @@ Use this to diagnose and fix common issues.
 Repo-specific checks and fixes can be defined in `[reporoot]/devenv/checks`.
 Otherwise we have "builtin" checks and fixes in `devenv.checks`.
 
+`devenv update`
+
+This updates the global devenv installation, and global tools.
+
+If you're upgrading from a particularly old devenv, it won't have `update` so you need to:
+`~/.local/share/sentry-devenv/venv/bin/pip install -U sentry-devenv`
+
 
 ## technical overview
 
 Everything devenv needs is in `~/.local/share/sentry-devenv`.
 
-- `~/.local/share/sentry-devenv/bin` contains `devenv` and `direnv`
-    - we currently rely on a minimal [`[reporoot]/.envrc`](#direnv) to add `[reporoot]/.devenv/bin` to PATH
-    - see [examples](#examples) for .envrc suggestions
+- `~/.local/share/sentry-devenv/bin` contains:
+    - `devenv` itself
+    - `direnv`
+      - we currently rely on direnv and a minimal [`[reporoot]/.envrc`](#direnv) to add `[reporoot]/.devenv/bin` to PATH
+      - see [examples](#examples) for .envrc suggestions
+    - global tools: `docker` (cli), `colima`
+
 
 ### runtime
 

{sentry_devenv-1.20.0 → sentry_devenv-1.21.0}/README.md

@@ -34,7 +34,6 @@ To update this installation, run `devenv update`.
 
 This is intended for initial setup of a new machine.
 
-
 `devenv fetch [repository name]`
 
 Any repository on github in the form of `[org]/[reponame]`
@@ -58,7 +57,6 @@ In general, our library is designed to isolate, as much as possible, a repo's de
 For example, [gcloud](#gcloud) is installed to `[reporoot]/.devenv/bin/gcloud` (with the gcloud sdk at `[reporoot]/.devenv/bin/google-cloud-sdk`).
 An exception to this would be python virtualenvs, which was implemented before the idea of `[reporoot]/.devenv`.
 
-
 `devenv doctor`
 
 Use this to diagnose and fix common issues.
@@ -66,14 +64,25 @@ Use this to diagnose and fix common issues.
 Repo-specific checks and fixes can be defined in `[reporoot]/devenv/checks`.
 Otherwise we have "builtin" checks and fixes in `devenv.checks`.
 
+`devenv update`
+
+This updates the global devenv installation, and global tools.
+
+If you're upgrading from a particularly old devenv, it won't have `update` so you need to:
+`~/.local/share/sentry-devenv/venv/bin/pip install -U sentry-devenv`
+
 
 ## technical overview
 
 Everything devenv needs is in `~/.local/share/sentry-devenv`.
 
-- `~/.local/share/sentry-devenv/bin` contains `devenv` and `direnv`
-    - we currently rely on a minimal [`[reporoot]/.envrc`](#direnv) to add `[reporoot]/.devenv/bin` to PATH
-    - see [examples](#examples) for .envrc suggestions
+- `~/.local/share/sentry-devenv/bin` contains:
+    - `devenv` itself
+    - `direnv`
+      - we currently rely on direnv and a minimal [`[reporoot]/.envrc`](#direnv) to add `[reporoot]/.devenv/bin` to PATH
+      - see [examples](#examples) for .envrc suggestions
+    - global tools: `docker` (cli), `colima`
+
 
 ### runtime
 

{sentry_devenv-1.20.0 → sentry_devenv-1.21.0}/devenv/main.py

@@ -103,7 +103,7 @@ def main() -> ExitCode:
         # https://sentry.sentry.io/settings/projects/sentry-dev-env/keys/
         dsn="https://9bdb053cb8274ea69231834d1edeec4c@o1.ingest.sentry.io/5723503",
         # enable performance monitoring
-        enable_tracing=True,
+        traces_sample_rate=1.0,
     )
 
     return devenv(sys.argv, f"{home}/.config/sentry-devenv/config.ini")

{sentry_devenv-1.20.0 → sentry_devenv-1.21.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "sentry_devenv"
-version = "1.20.0"
+version = "1.21.0"
 authors = [
   { name="Joshua Li", email="joshua.li@sentry.io" },
   { name="Ian Woodard", email="ian.woodard@sentry.io" },

{sentry_devenv-1.20.0 → sentry_devenv-1.21.0}/sentry_devenv.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: sentry_devenv
-Version: 1.20.0
+Version: 1.21.0
 Summary: Utilities for setting up a Sentry development environment
 Author-email: Joshua Li <joshua.li@sentry.io>, Ian Woodard <ian.woodard@sentry.io>, Buck Evan <buck.evan@sentry.io>
 Classifier: Programming Language :: Python :: 3
@@ -47,7 +47,6 @@ To update this installation, run `devenv update`.
 
 This is intended for initial setup of a new machine.
 
-
 `devenv fetch [repository name]`
 
 Any repository on github in the form of `[org]/[reponame]`
@@ -71,7 +70,6 @@ In general, our library is designed to isolate, as much as possible, a repo's de
 For example, [gcloud](#gcloud) is installed to `[reporoot]/.devenv/bin/gcloud` (with the gcloud sdk at `[reporoot]/.devenv/bin/google-cloud-sdk`).
 An exception to this would be python virtualenvs, which was implemented before the idea of `[reporoot]/.devenv`.
 
-
 `devenv doctor`
 
 Use this to diagnose and fix common issues.
@@ -79,14 +77,25 @@ Use this to diagnose and fix common issues.
 Repo-specific checks and fixes can be defined in `[reporoot]/devenv/checks`.
 Otherwise we have "builtin" checks and fixes in `devenv.checks`.
 
+`devenv update`
+
+This updates the global devenv installation, and global tools.
+
+If you're upgrading from a particularly old devenv, it won't have `update` so you need to:
+`~/.local/share/sentry-devenv/venv/bin/pip install -U sentry-devenv`
+
 
 ## technical overview
 
 Everything devenv needs is in `~/.local/share/sentry-devenv`.
 
-- `~/.local/share/sentry-devenv/bin` contains `devenv` and `direnv`
-    - we currently rely on a minimal [`[reporoot]/.envrc`](#direnv) to add `[reporoot]/.devenv/bin` to PATH
-    - see [examples](#examples) for .envrc suggestions
+- `~/.local/share/sentry-devenv/bin` contains:
+    - `devenv` itself
+    - `direnv`
+      - we currently rely on direnv and a minimal [`[reporoot]/.envrc`](#direnv) to add `[reporoot]/.devenv/bin` to PATH
+      - see [examples](#examples) for .envrc suggestions
+    - global tools: `docker` (cli), `colima`
+
 
 ### runtime