What problem do you want to solve?
I've recently investigated #3895 which potentially spans both the opentelemetry-python-contrib and the opentelemetry-python repositories. Both of these repositories have great configuration to set up uv workspaces for everything that is contained within the respective repository, but there is no documentation on how to setup a shared environment for both repositories to troubleshoot or develop across the boundary between the contrib and non-contrib repo.
Describe the solution you'd like
I'd like to add documentation and potentially configuration to this repository on how to setup local workspaces that include local versions of both opentelemetry-python-contrib and opentelemetry-python, instead of having separate workspaces that, in case of the opentelemetry-python-contrib repo, always install opentelemetry-python as a packaged dependency instead of utilizing a locally cloned version.
Describe alternatives you've considered
No response
Additional Context
No response
Would you like to implement a fix?
Yes
Tip
React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.
What problem do you want to solve?
I've recently investigated #3895 which potentially spans both the
opentelemetry-python-contriband theopentelemetry-pythonrepositories. Both of these repositories have great configuration to set upuvworkspaces for everything that is contained within the respective repository, but there is no documentation on how to setup a shared environment for both repositories to troubleshoot or develop across the boundary between thecontriband non-contribrepo.Describe the solution you'd like
I'd like to add documentation and potentially configuration to this repository on how to setup local workspaces that include local versions of both
opentelemetry-python-contribandopentelemetry-python, instead of having separate workspaces that, in case of theopentelemetry-python-contribrepo, always installopentelemetry-pythonas a packaged dependency instead of utilizing a locally cloned version.Describe alternatives you've considered
No response
Additional Context
No response
Would you like to implement a fix?
Yes
Tip
React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding
+1orme too, to help us triage it. Learn more here.