duplicate_key_in_meta_yaml doesn't respect selectors
This is understandable given how it's done, but when `yaml.load` hits a duplicate key it throws an error that's passed on as a linter error that can't be skipped. That's often going to be correct, but it doesn't then respect selectors, such as in https://github.com/bioconda/bioconda-recipes/pull/16968. We should really come up with a way around this, as a number of recipes can not longer be "built" because of it. The normal cause of this is that binaries are being redistributed, which while not ideal is sometimes the only option.
diff --git a/bioconda_utils/recipe.py b/bioconda_utils/recipe.py
index da15965..d39c40c 100644
--- a/bioconda_utils/recipe.py
+++ b/bioconda_utils/recipe.py
@@ -272,8 +272,11 @@ class Recipe():
             return None
         if not variants:
             return None
-        if any(" " in v for v in variants):
-            # can't handle "[py2k or osx]" style things
+        for k in list(variants.keys()):
+            if " " in k:
+                # can't handle "[py2k or osx]" style things
+                del variants[k]
+        if not variants:
             return None
 
         new_lines = []
['bioconda_utils/recipe.py']