-
Notifications
You must be signed in to change notification settings - Fork 80
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
Update project structure, switch to use setup.py #214
Conversation
}, | ||
python_requires=">=3.7", | ||
install_requires=[ | ||
"azure-monitor-opentelemetry-exporter>=1.0.0b10", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we're going to eliminate b8 and b9, maybe we should skip all the way to <=b11 to avoid the issue with logging moduel paths.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Incrementing the version can probably be done in a later pr. I don't want the change to be lost in these commits without context.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Was incrementing it from b8 to b10 intentional, then?
Change project directory structure to look more like what we use for azure-monitor-opentelemetry-exporter
Also adds custom config options to lint so they do not conflict with each other.