Closed pramodk closed 3 years ago
yaml
module is used to merge yaml file.
We merge yaml file when people put some .clang-format.extend
in the root of the git repository to update the default .clang-format
file (or cmake or tidy).
@tristan0x I cannot find a requirements.txt
in this repository, how is it handled?
Could this be optional?
Could this be optional?
A quick move is to restrict the import yaml
only where it is used. For instance, in this particular case, it would only fail if one provides a .clang-format.extend
at the root a project. But yeah, at some point we want to read and write yaml files.
Could this be optional?
A quick move is to restrict the
import yaml
only where it is used. For instance, in this particular case, it would only fail if one provides a.clang-format.extend
at the root a project. But yeah, at some point we want to read and write yaml files.
It already seems needed only when use (the import
is at beginning of the function using the module.
And, it would be nice if CMake try to give clear error message instead of silent error like above. (e.g. FindPythonModule can be used to check if pyyaml exists)
And so make it always needed globally?
I don't know how the overall workflow works here but what I was thinking of is : 1) you see <....>.extend
file exist at the top level 2) pyyaml module doesn't exist 3) then raise an error
I agree with @pramodk I would:
While building CoreNEURON in vanilla docker Ubuntu 20.04 image with typical build dependencies, I see:
Is
yaml
necessary dependency?