set_context type hint incorrectly set to `Any`

[rossettistone]

From reading the Sentry docs (https://docs.sentry.io/platforms/python/enriching-events/context/) and the source code for set_context(key: str, value: Any), we tried the following in our codebase:

with push_scope() as scope:
    scope.set_context('source_key', 'foo')  # 'source_key' is a term in our application

Unfortunately, this led to an error in the UI with the reason "expected an object".

I may be misunderstanding something, but it seems that set_context should be annotated with value: Dict, and the docs updated accordingly. Is this correct?

[untitaker]

Do the docs actually need changing? the docs use a dict value.

[rossettistone]

The example in the docs does show a dict example, it's true. The first line of the docs seems like it might be inaccurate, though: "Custom contexts allow you to attach arbitrary data (strings, lists, dictionaries) to an event."

That line could be interpreted as meaning that strings, lists, and dicts can be passed as values within the top-level dict, which is accurate. To me, though, it's unclear at best that this was the intended meaning, particularly in light of the Any type hint.

I defer to you on what the right behavior and annotation are here. From my user perspective, though, the docs are confusing as is.

[untitaker]

You're totally right, I will update both (see referenced PRs)

[rossettistone]

Thanks very much! The changes look great.