Some instrumentation are tagged as a pre-release
which poses as barrier of entry
#1218
Labels
pre-release
which poses as barrier of entry
#1218
Describe your environment
python 3.9
pipenv
Steps to reproduce
When trying to use some of the instrumentation packages (e.g. opentelemetry-instrumentation-psycopg2) only a pre-release tagged versions are published. This imposes an entry barrier to any pipenv using project because pipenv doesn't allow for per-package pre-release versions which in turn complicates project setup and dependency management configurations.
What is the expected behavior?
A NON-pre-release tagged x.y.z versioned packages to be released to avoid hitting package manager related issues and therefore improving usability of the instrumentation packages (e.g. [email protected]).
What is the actual behavior?
Only a
x.y.zb0
pre-release packages are available (e.g. [email protected]).Additional context
I am aware this is a tooling issue and a pipenv specific defficiency but in general I believe it may lower the barrier of entry as pipenv is used quite frequently.
The text was updated successfully, but these errors were encountered: