open-telemetry / open-telemetry/opentelemetry-python
Define a way to indicate non-end-user available symbols and private class symbols
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.6k
- Forks
- 1k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 19
Description
It looks like the `_ExponentialBucketHistogramAggregation` is reading/setting these fields. Since it's already in `_internal`, I think we can should make these public properties to make it clear that these are being modified from outside of this class
Originally posted by @aabmass in https://github.com/open-telemetry/opentelemetry-python/pull/2964#discussion_r1049979361
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating _ExponentialBucketHistogramAggregation and the referenced fields in the _internal package. Clarify how the project should distinguish non-end-user symbols from private class symbols, then confirm the agreed mechanism is applied consistently to the affected symbols.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100