> > > > On Mon, Mar 5, 2018 at 5:13 AM, kdbarto <[email protected] <javascript:>> > wrote: > >> >> Pip wasn’t installed and failed to self-install. So i reverted to >> easy_install. >> > this is why the macos installation guide says to use easy_install, not pip.
python installation and dependencies are a pain, and the python2 vs python3 makes everything even worse. if you do everything *exactly* by the recipe, you will probably be ok. but slight variations will often bring everything crashing down on you. on some operating systems like centos/redhat, you risk breaking the system if you install python modules using python instead of the system's packaging system. for example, doing a 'pip install foo' could break the system, whereas doing a 'yum install python-foo' could work just fine. on macos it is even more dangerous, since there is no system packaging system. on macos, you have all the third-party packagers such as fink, macports, or homebrew. plus the native python variants of pip or easy_install. plus the packaged python variants like anaconda. one override rule: do not mix installation methods. if you go native, stay native. if you go macports, stay macports. even if you are a python godess. luckily, weewx has few dependencies, and the dependencies it has are rather benign - other than PIL/Pillow, they do not require compilation. i don't know why the mac instructions, as written, did not work for you: http://weewx.com/docs/macos.htm it would help to know *exactly* what you did so that we can fix the instructions, or fix your procedure. those instructions worked for me on virgin macos installations from macosx 10.6.8 to macosx 10.11 (i have not tried on 10.12). m
