Message89717
| Author | ocean-city |
|---|---|
| Recipients | amaury.forgeotdarc, ocean-city |
| Date | 2009-06-26.01:00:37 |
| SpamBayes Score | 3.5956294e-08 |
| Marked as misclassified | No |
| Message-id | <1245978041.38.0.30815646392.issue6344@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
> I don't know what mf.read(-1) should do I'm not sure neither. I think the problem is that mmap uses size_t as length, but uses Py_ssize_t for PyArg_ParseTuple. (PyArg_ParseTuple doesn't support size_t) I think this discrepancy should be fixed. If mmap should use size_t because it should cover all possible memory region which size_t can represent but Py_ssize_t cannot, maybe should PyArg_ParseTuple support size_t? |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2009-06-26 01:00:41 | ocean-city | set | recipients: + ocean-city, amaury.forgeotdarc |
| 2009-06-26 01:00:41 | ocean-city | set | messageid: <1245978041.38.0.30815646392.issue6344@psf.upfronthosting.co.za> |
| 2009-06-26 01:00:39 | ocean-city | link | issue6344 messages |
| 2009-06-26 01:00:38 | ocean-city | create | |