If you entered a pathname for a nonexisting file to a FSSpec constructor

on OSX then the actual error (file not found) was obscured by the
error message that tried to be helpful about the allowed arguments. Fixed.

diff --git a/Mac/Modules/file/_Filemodule.c b/Mac/Modules/file/_Filemodule.c
index 70a8720abca51bf718d7148a5e79db1e8d2c445a..0df4c2ec1766700e355ea5b0774ca1959b7a39a9 100644 (file)
--- a/Mac/Modules/file/_Filemodule.c
+++ b/Mac/Modules/file/_Filemodule.c
@@ -2671,7 +2671,9 @@ PyMac_GetFSSpec(PyObject *v, FSSpec *spec)
                }
                return 1;
        }
+#if !TARGET_API_MAC_OSX
        PyErr_SetString(PyExc_TypeError, "FSSpec, FSRef, pathname or (refnum, parid, path) required");
+#endif
        return 0;
 }
 

diff --git a/Mac/Modules/file/filesupport.py b/Mac/Modules/file/filesupport.py
index 7238e8878257a59f448b0095617f7655da8e4e82..ffe6c0ee2703516db0499a2a09d9263624ab70ae 100644 (file)
--- a/Mac/Modules/file/filesupport.py
+++ b/Mac/Modules/file/filesupport.py
@@ -195,7 +195,9 @@ PyMac_GetFSSpec(PyObject *v, FSSpec *spec)
                }
                return 1;
        }
+#if !TARGET_API_MAC_OSX
        PyErr_SetString(PyExc_TypeError, "FSSpec, FSRef, pathname or (refnum, parid, path) required");
+#endif
        return 0;
 }