Fix conda-build & conda 4.11.0 incompatibility

[chenghlee]

Checklist

• Used a personal fork of the feedstock to propose changes
• Bumped the build number (if the version is unchanged)
• Reset the build number to 0 (if the version changed)
• Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• Ensured the license file is being packaged.

[conda-forge-linter]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

[mbargull]

Probably not what you'd want, c.f. conda-forge/conda-feedstock#108 (comment)
(but I'm also not sure what the actual behavior will be).

[kenodegard]

@mbargull had to reread the 4.4.0 release log a few times...so since conda-build actually depends on conda this isn't a constrains (which is optional) instead we want to inject this requirement as a depends?

Suggested change

	if "constrains" in record:
	record["constrains"].append("conda !=4.11.0")
	else:
	record["constrains"] = ["conda !=4.11.0"]
	for i, d in enumerate(record["depends"]):
	if dep in d:
	record["depends"][i] += ",<4.11.0"
	break
	else:
	record["depends"].append("conda <4.11.0")

[jakirkham]

Related to issue ( conda/conda-build#4333 )

[jakirkham]

cc @conda-forge/core

[hmaarrfk]

Sorry for letting this slip, but is this still relevant 1.5 years later?

[beckermr]

same response as in the other thread.

[hmaarrfk]

Ok. I was trying to see how I could help move things forward, either as clear up, review, or maybe just updating the suggested patches to make them current. The easiest would have been to close but it seems like it makes more sense to move them forward.

I didn't want to forget about "old PRs".