Closed do3cc closed 8 years ago
The following patch corrects this problem:
--- a/persistent/_timestamp.c
+++ b/persistent/_timestamp.c
@@ -478,7 +478,7 @@ TimeStamp_TimeStamp(PyObject *obj, PyObject *args)
}
PyErr_Clear();
- if (!PyArg_ParseTuple(args, "iii|iid", &y, &mo, &d, &h, &m, &sec))
+ if (!PyArg_ParseTuple(args, "iiiiid", &y, &mo, &d, &h, &m, &sec))
return NULL;
return TimeStamp_FromDate(y, mo, d, h, m, sec);
}
@jimfulton, can you recall a reason why the h
, m
, and sec
were optional? ZODB never constructs a TimeStamp instance with anything other than an 8-byte octet or 5 ints and a float.
This is on master: