You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I tried to install cookiecutter, I got the following error:
Running setup.py install for PyYAML
checking if libyaml is compilable
clang -fno-strict-aliasing -fno-common -dynamic -I/usr/local/include -I/usr/local/opt/sqlite/include -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I/usr/local/Cellar/python/2.7.6/Frameworks/Python.framework/Versions/2.7/include/python2.7 -c build/temp.macosx-10.9-x86_64-2.7/check_libyaml.c -o build/temp.macosx-10.9-x86_64-2.7/check_libyaml.o
build/temp.macosx-10.9-x86_64-2.7/check_libyaml.c:2:10: fatal error: 'yaml.h' file not found
#include <yaml.h>
^
1 error generated.
libyaml is not found or a compiler error: forcing --without-libyaml
(if libyaml is installed correctly, you may need to
specify the option --include-dirs or uncomment and
modify the parameter include_dirs in setup.cfg)
Successfully installed cookiecutter binaryornot jinja2 PyYAML
Cleaning up...
I don't know if libyaml is required in order for cookiecutter to work properly, but if so, then the output is misleading since the "Successfully installed PyYAML" message implies that it was installed correctly.
I was able to avoid this error by installing libyaml using Homebrew:
$ brew install libyaml
The text was updated successfully, but these errors were encountered:
I think PyYAML will fall back to a pure-python parser if libyaml is not available, so even when it said it failed, everything is cool.
On a related note: if someone has to use yaml for part of the functionality (in this case, for .cookiecutterrc) it seems like they should get to use it wherever.
When I tried to install cookiecutter, I got the following error:
I don't know if libyaml is required in order for cookiecutter to work properly, but if so, then the output is misleading since the "Successfully installed PyYAML" message implies that it was installed correctly.
I was able to avoid this error by installing libyaml using Homebrew:
The text was updated successfully, but these errors were encountered: