| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
with some extensions and changes from me.
This closes SF patch #472825.
|
|
|
|
|
| |
function.
This closes SF bug #486657.
|
|
|
|
| |
This is related to SF bug #485165.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Change PREFIX to PREFIXES, which contains a sequence of prefix strings.
This is useful since we want to look for both Py and PY.
- Wrap a long line.
- Collect struct tags as well as typedef names. Since we generally only
use one of the other, that improves coverage.
- Make the script executable on Unix.
This could use a better approach to determine if a symbol is documented,
and could easily avoid keeping the massive string in memory. That would
take time to actually write more code, though, so we'll bail on that
for now.
|
|
|
|
|
|
|
|
|
|
| |
vgetargskeywords(): Now that this routine is checking for bad input
(rather than dump core in some cases), some bad calls are raising errors
that previously "worked". This patch makes the error strings more
revealing, and changes the exceptions from SystemError to RuntimeError
(under the theory that SystemError is more of a "can't happen!" assert-
like thing, and so inappropriate for bad arguments to a public C API
function).
|
|
|
|
|
| |
fixes the problem reported in SF bug #477023 (Jonathan Mark): "pdb:
unexpected path confuses Emacs".
|
|
|
|
|
|
| |
ZipFile.__del__(): call ZipFile.close(), like its docstring says it does.
ZipFile.close(): allow calling more than once (as all file-like objects
in Python should support).
|
|
|
|
|
|
|
| |
pass the buffer length. Stop using it. It should be deprecated, but too
late in the release cycle to do that now.
New static format_float() does the same thing but requires passing the
buffer length too. Use it instead.
|
|
|
|
|
| |
Also change all the helper functions to pass along the size of the
msgbuf and use PyOS_snprintf() when writing into the buffer.
|
|
|
|
|
|
| |
const char* instead of char*. The change is conceptually correct, and
indirectly fixes a compiler wng introduced when somebody else innocently
passed a const char* to this function.
|
| |
|
| |
|
|
|
|
|
|
| |
seterror() uses a char array and a pointer to the current position in
that array. Use snprintf() and compute the amount of space left in
the buffer based on the current pointer position.
|
|
|
|
|
|
| |
If it returns -1 (which indicates overflow on old Linux platforms and
perhaps on Windows) or size greater than buffer, write a message
indicating that the previous message was truncated.
|
|
|
|
| |
overrun avoidance.
|
|
|
|
| |
overrun avoidance.
|
|
|
|
| |
redefinition problem.
|
|
|
|
| |
Also reformat calculate_path() using the standard format.
|
|
|
|
|
|
|
|
| |
com_arglist(), symtable_check_unoptimized(), symtable_params(),
symtable_global(), symtable_list_comprehension():
Conversion of sprintf() to PyOS_snprintf() for buffer overrun
avoidance.
|
|
|
|
| |
buffer overrun avoidance.
|
|
|
|
| |
PyOS_snprintf() for buffer overrun avoidance.
|
|
|
|
| |
PyOS_snprintf() for buffer overrun avoidance.
|
|
|
|
| |
for buffer overrun avoidance.
|
|
|
|
| |
overrun avoidance.
|
|
|
|
| |
sprintf() to PyOS_snprintf() for buffer overrun avoidance.
|
|
|
|
| |
buffer overrun avoidance.
|
|
|
|
|
|
|
| |
sprintf() to PyOS_snprintf() for buffer overrun avoidance.
complex_print(), complex_repr(), complex_str(): Call complex_to_buf()
passing in sizeof(buf).
|
| |
|
|
|
|
|
| |
Also replace a switch statement with one case and a default to an
if/else.
|
| |
|
| |
|
|
|
|
|
| |
Also changed <>-style #includes to ""-style in some places where the
former didn't make sense.
|
|
|
|
|
| |
Just being sure. The old code looks like it was safe, but there's no
harm in double-checking.
|
|
|
|
| |
the usage docs: (a) align properly, (b) explain properly.
|
|
|
|
| |
before 2.2b1.
|
|
|
|
| |
Change macros as requested by Guido
|
| |
|
| |
|
| |
|
|
|
|
| |
achieve a more sensible organization.
|
|
|
|
|
|
|
| |
is opened for writing; this closes SF bug #485342.
Added notes that file objects are also accepted in the place of file
descriptors.
|
|
|
|
| |
list of modules.
|
|
|
|
|
|
|
|
| |
parameters (like \UNIX) are commonly entered using an empty group to
separate the markup from a following inter-word space; this is not
needed when the next character is punctuation, or the markup is the
last thing in the enclosing group. These cases were marked
inconsistently; the empty group is now *only* used when needed.
|
|
|
|
|
|
|
|
| |
output.
Patch includes additional test case test_basic_line_wrap().
This patch is a candidate for Python 2.1.2.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
PyEval_EvalCodeEx(): increment tstate->recursion_depth around the
decref of the frame, because the C stack for this call is still in
use and the decref can lead to __del__ methods getting called.
While this gives tstate->recursion_depth a value proportional to the
depth of the C stack (instead of a small constant no matter how
deeply __del__s recurse), it's not enough to stop the reported crash
when using the default recursion limit on Windows.
Bugfix candidate.
|
|
|
|
|
|
|
| |
Bugfix candidate.
tb_displayline(): the sprintf format was choking off the file name, but
used plain %s for the function name (which can be arbitrarily long).
Limit both to 500 chars max.
|
|
|
|
|
|
|
|
| |
More changes to the formatdate epoch test: the Mac epoch is in
localtime, so east of GMT it falls in 1903:-( Changed the test to
obtain the epoch in both local time and GMT, and do the right
thing in the comparisons. As a sanity measure also check that
day/month is Jan 1.
|
| |
|