Hi!
The PR #416 has the current case:
all to keep a generic recipe which works for any version;configure() section and raise ConanInvalidConfiguration to the specific case.Now we need to decide what to do with this situation:
As the generic recipe should not be contaminated with specific versions, we can create an entire new folder version, copying ALL files from all folder and only adding the configure(self) section.
Use python_requires("fmt/6.0.0") for 6.1.0 as we only need to add a restriction.
python_requires is experimental.Import all/conanfile.py as Python module and customize as we need.
python_requiresBreak the rule of purity and add configure() in the generic recipe to ignore only that specific configuration.
python_requires("fmt/6.0.0")
I don't think so. This doesn't sound the right mechanism to solve this problem.
Besides other problems, like being experimental, it is not the right tool for this. Better explicit than implicit.
I don't see a strong reason why the recipe cannot use the version in configure() to raise an invalid configuration error. That would be flat, easy to read, easy to maintain and understandable by users.
I don't see a strong reason why the recipe cannot use the version in configure() to raise an invalid configuration error
Great! At same time we have a formal definition for future similar cases.
Added this question to the FAQ https://github.com/conan-io/conan-center-index/wiki/FAQ#are-python-requires-allowed-in-the-conan-center-index Thanks!
Most helpful comment
I don't think so. This doesn't sound the right mechanism to solve this problem.
Besides other problems, like being experimental, it is not the right tool for this. Better explicit than implicit.
I don't see a strong reason why the recipe cannot use the version in
configure()to raise an invalid configuration error. That would be flat, easy to read, easy to maintain and understandable by users.