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.

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;
 }
 

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;
 }