This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: Unhelpful error message when mtime of a module is -1
Type: Stage:
Components: Interpreter Core Versions: Python 2.3
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: nnorwitz Nosy List: nnorwitz, pm67nz
Priority: low Keywords:

Created on 2004-06-21 09:26 by pm67nz, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (2)
msg21229 - (view) Author: Peter Maxwell (pm67nz) Date: 2004-06-21 09:26
This fragment of import.c:

  mtime = PyOS_GetLastModificationTime(pathname, fp);
  if (mtime == (time_t)(-1))
     return NULL;

is missing a PyErr_SetString(), so in at least one circumstance (an 
__init__.py file with an apparent mtime of 1 Jan 1970 created by a 
bug in darcs on debian linux) it produces "SystemError: NULL 
result without error in PyObject_Call".
msg21230 - (view) Author: Neal Norwitz (nnorwitz) * (Python committer) Date: 2005-10-03 04:52
Logged In: YES 
user_id=33168

Thanks for the info, you were correct.

Checked in as:
 * Misc/NEWS something large, 1.1193.2.119
 * Python/import.c 2.245, 2.240.2.3
History
Date User Action Args
2022-04-11 14:56:04adminsetgithub: 40423
2004-06-21 09:26:56pm67nzcreate