It's really tricky to get accurate usage or download data for given package versions, platforms, etc, that can inform decision making (e.g. dropping osx-64).
Different conda clients are using different user agent strings for their repodata and package downloads so, even if we could query those, we could only do so for conda requests. Other tools like mamba, pixi or rattler-build are not providing as much information. We would also need a mechanism for specific contexts to extend the user agent with custom values (e.g. conda-forge might want to flag their internal CI jobs so they don't add noise to the real user data).
For example, in conda, the lack of a standard way to do so results in runtime patches like this.
I propose two things:
References:
It's really tricky to get accurate usage or download data for given package versions, platforms, etc, that can inform decision making (e.g. dropping osx-64).
Different conda clients are using different user agent strings for their repodata and package downloads so, even if we could query those, we could only do so for
condarequests. Other tools likemamba,pixiorrattler-buildare not providing as much information. We would also need a mechanism for specific contexts to extend the user agent with custom values (e.g. conda-forge might want to flag their internal CI jobs so they don't add noise to the real user data).For example, in
conda, the lack of a standard way to do so results in runtime patches like this.I propose two things:
pip's custom JSON user agent strings)References: