Skip to content

Conversation

@reyang
Copy link
Member

@reyang reyang commented Aug 22, 2019

No description provided.

Copy link
Member

@a-feld a-feld left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎉

Copy link
Member

@Oberon00 Oberon00 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder: If the app does not already depend on contextvars does it do us any good to use contextvars instead of thread locals? Since the backport does not integrate with asyncio.

EDIT: If we drop 3.4 I'm totally for this but otherwise I see no benefit, since we still need to support TLS context anyway.

@a-feld
Copy link
Member

a-feld commented Aug 23, 2019

@Oberon00 That's a fair point, maybe it's better to make this an optional install (pip install opentelemetry[contextvars])

@reyang
Copy link
Member Author

reyang commented Aug 23, 2019

If it is optional install, then we don't need it.
Users could always install contextvars by themselves, and the opentelemetry.context package will automatically detect and switch to contextvars.

Closing the PR for now.

@reyang reyang closed this Aug 23, 2019
@Jamim
Copy link
Contributor

Jamim commented Aug 23, 2019

But what about this?

@reyang reyang deleted the contextvars branch August 30, 2019 00:28
srikanthccv pushed a commit to srikanthccv/opentelemetry-python that referenced this pull request Nov 1, 2020
* scope: remove reporting of empty codecov

* core: prefix codecov report
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants