-
-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ClobberWarnings when installing pylint for conda-build tests #27
Comments
Thanks @pmspire. Sounds like the issue is in Can you please try installing |
I tried, but wasn't able, to reproduce this issue only via |
Thanks @pmspire. There's probably a flag that we would need to add to the |
conda-forge/configparser-feedstock#20 is open to potentially address this upstream. |
Thanks @pmspire. Have merged that now. Can you please retest after the new |
Will do. Is there a better way for me to know when new packages are available than to check with |
The |
Hang on, I'm in the wrong issue! Let me double-check this reproducer, with |
Yes, confirmed: The recipe mentioned at the top of this issue also now builds without the |
Thanks @pmspire :) |
Hi, I am experiencing a similar issue when updating this feedstock: The error is:
I haven't been able to find any help out there, could you please let us know your thoughts? Best regards, |
@sebastian-luna-valero, please open an issue on that feedstock. Thanks! |
Thanks @jakirkham I am one of the maintainers of the other feedstock, and I don't know how to proceed. Please let me know how to ask for help. |
Would open the issue on the other feedstock and cc core for help 🙂 |
Issue:
Apologies in advance if this ends up having nothing to do with this feedstock... Maybe it's a
conda-build
problem, but I didn't find anything appropriate in their GitHub issues and thought I might get some insight here. I'd be grateful for any input.When building a package that uses
pylint
for tests, I'm getting warnings/errors likeHere's the recipe:
I'm building with
I get the same warnings (some claim to be errors, but the build seems to proceed in any case) with a Miniconda3 as with Miniconda2. However, if I change the python version from
2.7
to3.7
inmeta.yaml
, the warnings/errors disappear.I actually get the same behavior if I do
conda build .
and so usedefaults
packages instead ofconda-forge
, but I thought I might make better progress asking here about this.Environment (
conda list
):Details about
conda
and system (conda info
):The text was updated successfully, but these errors were encountered: