watchdog: 'pip install watchdog' fails on macOS 10.15.2 Catalina
pip install watchdog
fails after I upgraded to macOS 10.15.2 with this error:
Complete output (202 lines):
running install
running build
running build_py
creating build
creating build/lib.macosx-10.14-x86_64-3.5
creating build/lib.macosx-10.14-x86_64-3.5/watchdog
copying src/watchdog/watchmedo.py -> build/lib.macosx-10.14-x86_64-3.5/watchdog
copying src/watchdog/version.py -> build/lib.macosx-10.14-x86_64-3.5/watchdog
copying src/watchdog/events.py -> build/lib.macosx-10.14-x86_64-3.5/watchdog
copying src/watchdog/__init__.py -> build/lib.macosx-10.14-x86_64-3.5/watchdog
creating build/lib.macosx-10.14-x86_64-3.5/watchdog/utils
copying src/watchdog/utils/unicode_paths.py -> build/lib.macosx-10.14-x86_64-3.5/watchdog/utils
copying src/watchdog/utils/compat.py -> build/lib.macosx-10.14-x86_64-3.5/watchdog/utils
copying src/watchdog/utils/win32stat.py -> build/lib.macosx-10.14-x86_64-3.5/watchdog/utils
copying src/watchdog/utils/__init__.py -> build/lib.macosx-10.14-x86_64-3.5/watchdog/utils
copying src/watchdog/utils/dirsnapshot.py -> build/lib.macosx-10.14-x86_64-3.5/watchdog/utils
copying src/watchdog/utils/delayed_queue.py -> build/lib.macosx-10.14-x86_64-3.5/watchdog/utils
copying src/watchdog/utils/platform.py -> build/lib.macosx-10.14-x86_64-3.5/watchdog/utils
copying src/watchdog/utils/bricks.py -> build/lib.macosx-10.14-x86_64-3.5/watchdog/utils
copying src/watchdog/utils/echo.py -> build/lib.macosx-10.14-x86_64-3.5/watchdog/utils
creating build/lib.macosx-10.14-x86_64-3.5/watchdog/observers
copying src/watchdog/observers/fsevents.py -> build/lib.macosx-10.14-x86_64-3.5/watchdog/observers
copying src/watchdog/observers/inotify.py -> build/lib.macosx-10.14-x86_64-3.5/watchdog/observers
copying src/watchdog/observers/__init__.py -> build/lib.macosx-10.14-x86_64-3.5/watchdog/observers
copying src/watchdog/observers/api.py -> build/lib.macosx-10.14-x86_64-3.5/watchdog/observers
copying src/watchdog/observers/inotify_buffer.py -> build/lib.macosx-10.14-x86_64-3.5/watchdog/observers
copying src/watchdog/observers/winapi.py -> build/lib.macosx-10.14-x86_64-3.5/watchdog/observers
copying src/watchdog/observers/read_directory_changes.py -> build/lib.macosx-10.14-x86_64-3.5/watchdog/observers
copying src/watchdog/observers/kqueue.py -> build/lib.macosx-10.14-x86_64-3.5/watchdog/observers
copying src/watchdog/observers/inotify_c.py -> build/lib.macosx-10.14-x86_64-3.5/watchdog/observers
copying src/watchdog/observers/polling.py -> build/lib.macosx-10.14-x86_64-3.5/watchdog/observers
copying src/watchdog/observers/fsevents2.py -> build/lib.macosx-10.14-x86_64-3.5/watchdog/observers
creating build/lib.macosx-10.14-x86_64-3.5/watchdog/tricks
copying src/watchdog/tricks/__init__.py -> build/lib.macosx-10.14-x86_64-3.5/watchdog/tricks
running egg_info
writing top-level names to src/watchdog.egg-info/top_level.txt
writing requirements to src/watchdog.egg-info/requires.txt
writing src/watchdog.egg-info/PKG-INFO
writing entry points to src/watchdog.egg-info/entry_points.txt
writing dependency_links to src/watchdog.egg-info/dependency_links.txt
reading manifest file 'src/watchdog.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: no files found matching '*.h' under directory 'src'
writing manifest file 'src/watchdog.egg-info/SOURCES.txt'
running build_ext
building '_watchdog_fsevents' extension
creating build/temp.macosx-10.14-x86_64-3.5
creating build/temp.macosx-10.14-x86_64-3.5/src
clang -Wno-unused-result -Wsign-compare -Wunreachable-code -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/include -DWATCHDOG_VERSION_STRING="0.10.0" -DWATCHDOG_VERSION_MAJOR=0 -DWATCHDOG_VERSION_MINOR=10 -DWATCHDOG_VERSION_BUILD=0 -I/Users/ericvanegmond/.pyenv/versions/3.5.3/include/python3.5m -c src/watchdog_fsevents.c -o build/temp.macosx-10.14-x86_64-3.5/src/watchdog_fsevents.o -std=c99 -pedantic -Wall -Werror -Wextra -fPIC -Wno-error=unused-command-line-argument
In file included from src/watchdog_fsevents.c:22:
In file included from /Users/ericvanegmond/.pyenv/versions/3.5.3/include/python3.5m/Python.h:25:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/include/stdio.h:64:
/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/include/_stdio.h:137:9: error: type nullability specifier '_Nullable' is a Clang extension [-Werror,-Wnullability-extension]
int (* _Nullable _close)(void *);
^
/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/include/_stdio.h:93:16: error: pointer is missing a nullability type specifier (_Nonnull, _Nullable, or _Null_unspecified) [-Werror,-Wnullability-completeness]
unsigned char *_base;
^
/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/include/_stdio.h:93:16: note: insert '_Nullable' if the pointer may be null
unsigned char *_base;
^
_Nullable
.
.
.
/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/include/stdio.h:391:44: note: insert '_Nullable' if the pointer may be null
fpos_t (* _Nullable)(void *, fpos_t, int),
^
_Nullable
/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/include/stdio.h:391:44: note: insert '_Nonnull' if the pointer should never be null
fpos_t (* _Nullable)(void *, fpos_t, int),
^
_Nonnull
/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/include/stdio.h:392:25: error: type nullability specifier '_Nullable' is a Clang extension [-Werror,-Wnullability-extension]
int (* _Nullable)(void *));
^
fatal error: too many errors emitted, stopping now [-ferror-limit=]
20 errors generated.
error: command 'clang' failed with exit status 1
----------------------------------------
Any suggestions on how to resolve this? So far I’ve tried removing and reinstalling both xcode and command line tools which hasn’t helped. Not sure what else to try here.
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 1
- Comments: 23
Thanks for your continuous effort, @BoboTiG!
I tested f87d1cf3eb79c308ff7b8eca8cc74ad51385f58d and everything is working fine! 👍
This is the output of
./.venv/bin/watchmedo --help
:OK, I removed
-Werror
completely, there is no way we lost more time on that … Do you confirm this is fixed now? (And so sorry for taking so much of your times.)OK we will finally get that fixed! Please, tell me that this is fixed on the
fix-use-sys-platform
branch 🤞 (I force pushed)The release 0.10.1 is out 😃
I love when it works so smoothly 😃 Thanks a lot. Now we are finally ready for a bugfix release.
@BoboTiG I tested as well and it resolves the issues I was having. Thank you!!!
Ah that is an excellent news, thanks @keimlink !
I orce-pushed on the same branch. Could you have another try please? Sorry to ask you that 😃
350d9f46720337fb197aaeb30884239cba2dc6d7 is part of #467, which is part of release 0.10.0.
So I would guess that before 0.10.0
-Werror
wasn’t used, so these warnings were not enabled.I will simply fix the code, thanks for the report @keimlink 😃