-
Notifications
You must be signed in to change notification settings - Fork 623
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Immutables does not have a py35 Windows wheel built #939
Comments
I'm pretty sure |
I would suggest we also run tests for the core components on Windows and MacOS for at least the oldest and newest supported Python to catch some of these types of issues. rel: #910 |
Co-authored-by: Mayur Kale <mayurkale@google.com>
This issue was marked stale due to lack of activity. It will be closed in 30 days. |
Closed as inactive. Feel free to reopen if this issue needs resolving. |
Describe your environment Describe any aspect of your environment relevant to the problem, including your Python version, platform, version numbers of installed dependencies, information about your cloud hosting provider, etc. If you're reporting a problem with a specific version of a library in this repo, please check whether the problem has been fixed on master.
Python Version: 3.5
Version Number of OpenTelemetry: 0.10b0
OS Version: Windows 10
Steps to reproduce
Describe exactly how to reproduce the error. Include a code sample if applicable.
conda create -n py35 python=3.5
pip install opentelemetry-api
What is the expected behavior?
What did you expect to see?
Pip install
opentelemetry-api
should just work for Python3.5 on WindowsWhat is the actual behavior?
What did you see instead?
I removed some of the path information.
Additional context
Add any other context about the problem here.
This is because open telemetry depends on
aiocontextvars
which depends oncontextvars
which depends onimmutable
which doesn't have a python 3.5 Windows wheel. The reason is documented in their code.It looks like open-census only depends on contextvars for python >= 3.6 so it doesn't have this issue.
The text was updated successfully, but these errors were encountered: