On 04/30/2015 02:42 PM, intrigeri wrote:
> Dominyk Tiller wrote (30 Apr 2015 01:29:09 GMT) :
>> The latest tarball seems to be having some runtime hiccups on OS X 10.10.3.
>
>> A simple `mat -l` fails with this error:
>
>> =================================
>> Traceback (most recent call last):
>> File "/usr/local/Cellar/mat/0.5.3/libexec/bin/mat", line 142, in <module>
>> main()
>> File "/usr/local/Cellar/mat/0.5.3/libexec/bin/mat", line 116, in main
>> list_supported()
>> File "/usr/local/Cellar/mat/0.5.3/libexec/bin/mat", line 96, in
>> list_supported
>> for item in mat.list_supported_formats():
>> File
>> "/usr/local/Cellar/mat/0.5.3/libexec/lib/python2.7/site-packages/libmat/mat.py",
>> line 67, in list_supported_formats
>> with open(path, 'r') as xmlfile:
>> TypeError: coercing to Unicode: need string or buffer, NoneType found
>> =================================
>
> It looks like MAT can't find its FORMATS file. If we want to support
> installing MAT files into arbitrary locations, then we'll need to have
> something similar to ./configure and automake etc., that patches the
> data files' location into the program files.
This seems completely overkill to me,
I'd rather hardcode OSX's default path.
