- Add support for the sampled flag for start_span and respect it when making sampling decisions.
- Rework sampling_context in traces_sampler to work with span attributes instead. Make sure we still have the same data accessible as now.

We could go one step further and change the format of sampling_context to just be the actual span attributes without any postprocessing into the current format. I kept the format in line with what we have now to make it easier to update.

See #3746
Closes #3739

This is a breaking change since we're removing custom_sampling_context. It'll break multiple integrations until we fix them (see #3746).

Remove explicit trace_id passing

…3779)

…correct in context manager regardless of source of span (#4439)

closes #3509

We don't use the `client` parameter in the `Scope`'s constructor,
perhaps we can remove it and simplify the API. It is still possible to
set the client with `Scope.set_client`.

BREAKING CHANGE: `sentry_sdk.Scope` no longer has a `client` parameter.

<!-- Describe your PR here -->

---

Thank you for contributing to `sentry-python`! Please add tests to
validate your changes, and lint your code using `tox -e linters`.

Running the test suite on your PR might require maintainer approval.

Currently, this test only asserts that the `traces_sampler` is called at
least once with the given arguments. However, we would expect it to be
called exactly once.

This PR changes the assertion to assert that the `traces_sampler` was
called exactly one time, and that that call included the given
arguments.

<!-- Describe your PR here -->

---

Thank you for contributing to `sentry-python`! Please add tests to
validate your changes, and lint your code using `tox -e linters`.

Running the test suite on your PR might require maintainer approval.

If a `TracerProvider` already exists, patch it. `TracerProvider` is a
singleton, so if we aren't the first ones setting it up, we need to use
the existing one.

In tests, reset `TracerProvider` after each test so that we start with a
clean slate and it gets set up anew on init.

- According to our [span
ops](https://develop.sentry.dev/sdk/telemetry/traces/span-operations/#database)
there is no op called just `db`, but we're emitting these from django,
clickhouse, asyncpg and pymongo. Changing to `db.query` instead.
- There was also a breadcrumb with type `db` that's also [officially not
a supported
type](https://develop.sentry.dev/sdk/data-model/event-payloads/breadcrumbs/#breadcrumb-types),
changed it to `query`.

This is intentionally just on `potel-base` since it's technically a
breaking change.

This reverts commit 84187ea.

…potel-base

It is not ready yet and i do not want to push dog fooding back again.

extracted from
https://github.com/getsentry/sentry-python/pull/4487/files with lots of
manual fixes

* migrate old style `# type: bla` to inline types
* most importantly use
[`__future__.annotations`](https://peps.python.org/pep-0563/#enabling-the-future-behavior-in-python-3-7)
so that we can simply use forward annotations without wrapping them in
strings like we did before, this simplifies things substantially
* also guard only things that shouldn't be imported under
`TYPE_CHECKING`, in the future it seems we should avoid using
`TYPE_CHECKING` completely
* #4510
* #4522
* #4529
* #4530
* #4532
* #4533
* #4534

closes #2585

Ensure tag values are strings before serializing an event or a
transaction to an `Event` dictionary.

Fixes #4391

Co-authored-by: Cursor Agent <cursoragent@cursor.com>
Co-authored-by: Ivana Kellyer <ivana.kellyer@sentry.io>

We currently use an `if self._ctx_token` check to determine if a span
has a `_ctx_token`. However, this check is incorrect, since `_ctx_token`
is only sometimes set. Furthermore, when `_ctx_token` is set, we should
always have a `_ctx_token`.

Therefore, using `hasattr` is what we want.

<!-- Describe your PR here -->

---

Thank you for contributing to `sentry-python`! Please add tests to
validate your changes, and lint your code using `tox -e linters`.

Running the test suite on your PR might require maintainer approval.