Revert and move otel dev dependencies to root with disclaimer

Author: anuraaga

DEVELOPMENT.md

@@ -19,7 +19,7 @@
 2. Install dependencies:
 
    ```bash
-   uv sync --all-packages
+   uv sync
    ```
 
 ## Development Workflow

README.md

@@ -405,7 +405,7 @@ We rely on the conformance test suit (in
 Set up a virtual env:
 
 ```sh
-uv sync --all-packages
+uv sync
 ```
 
 Then, use `uv run just` to do development checks, or check out `uv run just --list` for other targets.

connectrpc-otel/pyproject.toml

@@ -63,10 +63,6 @@ dev = [
   # a transitive dependency, so we go ahead and leave it out.
   "connectrpc>=0.8.0",
 
-  "opentelemetry-instrumentation-asgi==0.61b0",
-  "opentelemetry-instrumentation-wsgi==0.61b0",
-  "opentelemetry-sdk==1.40.0",
-
   "connect-python-example",
   "pytest",
 ]

pyproject.toml

@@ -57,6 +57,17 @@ dev = [
   "uvicorn==0.42.0",
   "zstandard==0.25.0",
 
+  # dev dependencies only used in subprojects. Optimal structure would include these
+  # in the subproject itself, but then `uv sync` does not install them from the
+  # workspace root. We strategically keep them here instead so the entire workspace
+  # is ready for editing in an IDE with a simple sync command.
+  # If the below issue is resolved, we can move them back to subprojects and configure
+  # our default sync setting as --all-packages.
+  # https://github.com/astral-sh/uv/issues/5737
+  "opentelemetry-instrumentation-asgi==0.61b0",
+  "opentelemetry-instrumentation-wsgi==0.61b0",
+  "opentelemetry-sdk==1.40.0",
+
   # Versions locked in constraint-dependencies
   "pytest",
   "pytest-asyncio",