[conda] Where to report bugs in package specs?

[Skip Montanaro]

Where is the correct place to report bugs with package specs? Google
led me here:

https://conda.io/docs/help-support.html

It talks about "conda" and "conda-build", but is silent about packaging.

At the moment, I'm interesting getting a tighter dependency spec in
the hypothesis package on its dependent attrs package:

https://anaconda.org/anaconda/hypothesis

At work, we have attrs 15.2.0 and 17.[234].0 and hypothesis 3.46.0. I
can't import hypothesis when attrs 15.2.0 is installed. If I bump to
17.2.0, it works fine.

I can file a bug with the hypothesis folks, but it's not at all clear
that they maintain the package spec. A quick skim of the github
project didn't reveal a meta.yaml file. The setup.py file is pretty
clear on the version dependency:

install_requires = ['attrs>=16.0.0', 'coverage']

That version dependency was introduced 2018-01-23. According to the
hypothesis/version.py file history, v 3.46.0 (what I have available at
work) was released 2018-02-25, so it appears the attrs version
dependency failed to make the jump from pip to conda.

So, in general, where should I report package metadata bugs?

Thx,

Skip Montanaro

[Eric Dill]

Hi Skip,

It depends which channel you got the package from. You can check with the
output of

conda list

which should show something like this

# packages in environment at /Users/edill/miniconda:
#
anaconda-client 1.6.3 py36_0 conda-forge
appnope 0.1.0 py36_0 conda-forge
<snip>
numpy 1.13.1 py36_nomkl_0 [nomkl] defaults
<snip>

The last column in the output above ^ is the "channel" where you got the
package.
If that channel for attrs is conda-forge then you should raise an issue on
the "feedstock"
here: https://github.com/conda-forge/attrs-feedstock/blob/master/recipe/meta.yaml.
If that channel is defaults then I think the place for that is on this
repo: https://github.com/ContinuumIO/anaconda-recipes

Post by Skip Montanaro
Where is the correct place to report bugs with package specs? Google
https://conda.io/docs/help-support.html
It talks about "conda" and "conda-build", but is silent about packaging.
At the moment, I'm interesting getting a tighter dependency spec in
https://anaconda.org/anaconda/hypothesis
At work, we have attrs 15.2.0 and 17.[234].0 and hypothesis 3.46.0. I
can't import hypothesis when attrs 15.2.0 is installed. If I bump to
17.2.0, it works fine.
I can file a bug with the hypothesis folks, but it's not at all clear
that they maintain the package spec. A quick skim of the github
project didn't reveal a meta.yaml file. The setup.py file is pretty
install_requires = ['attrs>=16.0.0', 'coverage']
That version dependency was introduced 2018-01-23. According to the
hypothesis/version.py file history, v 3.46.0 (what I have available at
work) was released 2018-02-25, so it appears the attrs version
dependency failed to make the jump from pip to conda.
So, in general, where should I report package metadata bugs?
Thx,
Skip Montanaro

[Skip Montanaro]

Post by Eric Dill
It depends which channel you got the package from. You can check with the
output of
conda list

...

Both hypothesis and attrs come from conda/anaconda, which I believe is
our internal mirror of the standard set of packages. I'll open a help
ticket on the second GitHub repo.

The help-support page I originally referenced would probably benefit
from the information in Eric's post.

Thanks,

Skip