I did all of those things.
Pip wasn’t installed and failed to self-install. So i reverted to easy_install.
After I cleared out the old install ‘.egg’ files pillow was no longer installed.
I changed the install directory to ensure that /Users/Shared/weewx was the
final resting place for all of the parts that would be installed.
The thing that bothers me at this point is that the C code is (apparently, I
can’t see the invocation lines) being compiled for x86 32bit mode, rather than
x86_64 mode, so the linker is throwing shade on the install process.
After performing all the magic you suggested, and still seeing failure, I then
deleted everything up to that point, re-unpacked the original weewx tarball and
started again. It was at this point that these errors re-appear. Note that the
pillow .egg file is in /Users/Shared/weewx/bin.
My PYTHONPATH is set to /Users/Shared/weewx/bin, as I got errors if that
wasn’t set. This may be a source of some problem. I’m not a python expert. (Big
data, sure; python, not so much)
Clearly I’m doing something silly because I’m sure that I’m not the first
person to try to install weewx on a MacOS based system. If I am blazing a
trail, then it is all on me. 8^)
David
> On Mar 4, 2018, at 12:02 PM, Thomas Keffer <[email protected]> wrote:
>
> I think you are making this more complicated than it has to be.
>
> First, we already established that you have something like Pillow or PIL
> already installed, so why try to install again?
>
> Second, did you check to see if you already have pip? If not, easy_install is
> perfectly fine. It just doesn't handle some corner cases as well.
>
> Third, did you try my suggestion in an email earlier today to change change
> into the correct directory? This may be the only problem you are having.
>
> -tk
>
> On Sun, Mar 4, 2018 at 11:24 AM, David & Katherine Barto <[email protected]
> <mailto:[email protected]>> wrote:
> I guess that MacOS really isn’t supported. 8^)
>
> Attempting to install pillow using the provided configure and install
> instructions (easy_install PIL) failed so I ‘easy_install pillow’, and that
> leaves me with a sinking feeling. After many compile warnings (-Werror
> anyone?) I get the following
>
> ld: warning: ignoring file /opt/local/lib/libfreetype.dylib, file was built
> for x86_64 which is not the architecture being linked (i386):
> /opt/local/lib/libfreetype.dylib
>
> This is then followed by more install errors making me think that pillow
> isn’t happy.
>
> Adding Pillow 5.0.0 to easy-install.pth file
>
> Installed /Users/Shared/weewx/bin/Pillow-5.0.0-py2.7-macosx-10.11-intel.egg
> Processing dependencies for pillow
> Finished processing dependencies for pillow
> Exception in thread Thread-1:
> Traceback (most recent call last):
> File
> "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/threading.py",
> line 810, in __bootstrap_inner
> self.run()
> File
> "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/threading.py",
> line 763, in run
> self.__target(*self.__args, **self.__kwargs)
> File
> "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/multiprocessing/pool.py",
> line 330, in _handle_workers
> debug('worker handler exiting')
> TypeError: 'NoneType' object is not callable
>
> Exception TypeError: Exception in thread Thread-2:
> Traceback (most recent call last):
> File
> "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/threading.py",
> line 810, in __bootstrap_inner
> self.run()
> File
> "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/threading.py",
> line 763, in run
> self.__target(*self.__args, **self.__kwargs)
> File
> "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/multiprocessing/pool.py",
> line 366, in _handle_tasks
> debug('task handler got sentinel')
> TypeError: 'NoneType' object is not callable
>
> TypeError("'NoneType' object does not support item deletion",) in <Finalize
> object, dead> ignored
>
> David
>
>
>> On Mar 4, 2018, at 8:42 AM, David & Katherine Barto <[email protected]
>> <mailto:[email protected]>> wrote:
>>
>>
>>> On Mar 3, 2018, at 3:42 PM, Thomas Keffer <[email protected]
>>> <mailto:[email protected]>> wrote:
>>>
>>> Nice to have a Mac expert around! Perhaps in a quiet moment you can tell me
>>> how to get the system logger to work on High Sierra.
>>>
>>> The biggest problem you are going to have is device drivers. In particular,
>>> if your hardware appears as anything other than a simple serial device, you
>>> may have problems getting it to work. From your first email, it looks like
>>> you have a Davis Vantage, which is a good thing, because it uses a serial
>>> interface. Hopefully, the Mac will recognize it as such.
>>>
>>> Get the prerequisites installed, as per the MacOS instructions
>>> <http://weewx.com/docs/macos.htm>. I know the instructions say to use
>>> easy_install (we should change that), but pip usually works better. If
>>> you're already installed everything using easy_install, don't worry about
>>> it.
>>>
>>> If you have a Vantage, you do not need to install pyusb
>>>
>>> Judging from your 2nd email, it looks like you tried installing weewx in
>>> /Users/Shared/weewx/... So try deleting everything in that directory.
>>>
>>> Then it's pretty much following the directions in the MacOS instructions,
>>> making sure to let the installer run to completion.
>>>
>>> An easy to overlook step is editing the file setup.cfg to reflect your
>>> nonstandard install location (normally, weewx is installed into
>>> /home/weewx, but /home is reserved on the Mac).
>>>
>>> /Users/Shared/weewx/weewx-3.8.0/setup.cfg:
>>>
>>> # Configuration file for weewx installer. The syntax is from module
>>> # ConfigParser. See http://docs.python.org/library/configparser.html
>>> <http://docs.python.org/library/configparser.html>
>>>
>>> [install]
>>>
>>> # Set the following to the root directory where weewx should be installed
>>> home = /Users/Shared/weewx
>>>
>>> # Given the value of 'home' above, the following are reasonable values
>>> prefix =
>>> exec-prefix =
>>> install_lib = %(home)s/bin
>>> install_scripts = %(home)s/bin
>>>
>>> -tk
>>>
>>>
>>> On Sat, Mar 3, 2018 at 2:12 PM, kdbarto <[email protected]
>>> <mailto:[email protected]>> wrote:
>>>
>>>> On Mar 3, 2018, at 2:00 PM, Thomas Keffer <[email protected]
>>>> <mailto:[email protected]>> wrote:
>>>>
>>>> The Mac is an "unsupported platform," but I'm sure we can get it working.
>>>>
>>>> First, see if you already have a copy of PIL or Pillow. From the command
>>>> line:
>>>>
>>>> python -c "import PIL”
>>> Had no output. I’ll assume that is good.
>>>
>>>>
>>>> If that gives you an import error, try this
>>>>
>>>> python -c "import Image"
>>>>
>>>> If either of these work, then you are probably OK, and do not need to
>>>> install Pillow. I say "probably," because it's possible your previous
>>>> attempt to install using "install" resulted in a corrupted copy being left
>>>> behind. We'll see.
>>>>
>>>> If neither of these two command lines work, then you will need to install
>>>> Pillow. Use pip to do so. Your system probably already has pip, but if it
>>>> doesn't see the pip website <https://pip.pypa.io/en/stable/installing/>
>>>> for instructions on how to install it.
>>>>
>>>> With pip in hand, install Pillow:
>>>>
>>>> pip install pillow
>>>>
>>>> As for your second error, "KeyError", that looks like it may be caused by
>>>> an incomplete install. Did you use setup.py to install? Normally, the
>>>> weewx configuration file comes with a station type of "unspecified". That
>>>> is then replaced by setup.py with your actual hardware type. This second
>>>> step somehow did not get completed.
>>>>
>>>> Try deleting everything and trying again, this time making sure you let
>>>> the setup.py install run to completion.
>>>
>>> Deleting everything. I’m good with that. Where is this everything you refer
>>> to? 8^)
>>> I’m well versed in all things Unix and programming, so being technical is
>>> OK with me. (My name appears in every iPhone shipped, for instance).
>>>
>>> David
>>>
>>>>
>>>> Hope this gets you started.
>>>>
>>>> -tk
>>>>
>>>> On Sat, Mar 3, 2018 at 1:42 PM, David <[email protected]
>>>> <mailto:[email protected]>> wrote:
>>>> I’m just following the instructions from the weewx website. At this point
>>>> it fails to launch.
>>>>
>>>> What I read on the Wview mailing list was that this was a good replacement
>>>> and was actively developed and maintained, unlike wview.
>>>>
>>>> I guess I just need to know what to do ‘next’. Is there an un-install I
>>>> can try to reset, and then try again?
>>>>
>>>> David
>>>>
>>>>> On Mar 3, 2018, at 11:46 AM, Thomas Keffer <[email protected]
>>>>> <mailto:[email protected]>> wrote:
>>>>>
>>>>> This seems to be a problem with the Pillow install, and not with WeeWX.
>>>>>
>>>>> First, are you sure you need to install Pillow? Most Python installations
>>>>> come with a version of PIL or Pillow.
>>>>>
>>>>> Second, I have generally had better luck installing things with pip,
>>>>> rather than BSD install or easy_install.
>>>>>
>>>>> -tk
>>>>>
>>>>>
>>>>> On Sat, Mar 3, 2018 at 10:38 AM, David Barto <[email protected]
>>>>> <mailto:[email protected]>> wrote:
>>>>> wviewd_vpro is consuming 75% of the cpu. So I thought I’d give weewx a
>>>>> shot.
>>>>>
>>>>> Installing from their instructions shows the following problem, and since
>>>>> I don’t know Python that well I though I’d ask if this is ‘OK’.
>>>>> After doing this, trying it again shows that it is installed according to
>>>>> the installer program.
>>>>>
>>>>> Anyone here have any answers about these problems?
>>>>>
>>>>> David
>>>>>
>>>>>
>>>>> MacOS 10.11.6
>>>>>
>>>>> marvin:Desktop$ python -V
>>>>> Python 2.7.10
>>>>>
>>>>> sudo install Pillow
>>>>>
>>>>> Adding Pillow 5.0.0 to easy-install.pth file
>>>>>
>>>>> Installed
>>>>> /Library/Python/2.7/site-packages/Pillow-5.0.0-py2.7-macosx-10.11-intel.egg
>>>>> Processing dependencies for Pillow
>>>>> Finished processing dependencies for Pillow
>>>>> Exception in thread Thread-1:
>>>>> Traceback (most recent call last):
>>>>> File
>>>>> "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/threading.py",
>>>>> line 810, in __bootstrap_inner
>>>>> self.run()
>>>>> File
>>>>> "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/threading.py",
>>>>> line 763, in run
>>>>> self.__target(*self.__args, **self.__kwargs)
>>>>> File
>>>>> "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/multiprocessing/pool.py",
>>>>> line 330, in _handle_workers
>>>>> debug('worker handler exiting')
>>>>> TypeError: 'NoneType' object is not callable
>>>>>
>>>>> Exception TypeError: TypeError("'NoneType' object does not support item
>>>>> deletion",) in <Finalize object, dead> ignored
>>>>> Exception in thread Thread-2:
>>>>> Traceback (most recent call last):
>>>>> File
>>>>> "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/threading.py",
>>>>> line 810, in __bootstrap_inner
>>>>> self.run()
>>>>> File
>>>>> "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/threading.py",
>>>>> line 763, in run
>>>>> self.__target(*self.__args, **self.__kwargs)
>>>>> File
>>>>> "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/multiprocessing/pool.py",
>>>>> line 366, in _handle_tasks
>>>>> debug('task handler got sentinel')
>>>>> TypeError: 'NoneType' object is not callable
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>
>
