| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
taken from a Debian patch. Should we update the version for each release?
|
|
|
|
|
|
|
|
| |
sporadically on other platforms. This is really a band-aid that doesn't
fix the underlying issue in SocketServer. It's not clear if it's worth
it to fix SocketServer, however, I opened a bug to track it:
http://python.org/sf/1540386
|
|
|
|
| |
Now we're even. :-)
|
| |
|
| |
|
| |
|
|
|
|
| |
file correctly even on Windows.
|
|
|
|
| |
when file is read-only.
|
|
|
|
| |
raises the correct exceptions.
|
|
|
|
|
| |
Add a test to test_inspect to make sure indented source
is recognized correctly. (fixes #1224621)
|
| |
|
| |
|
|
|
|
|
| |
Remove the -no-stack-protector compiler flag for OpenBSD
as it has been reported to be unneeded.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
ctypes instances no longer have the internal and undocumented
'_as_parameter_' attribute which was used to adapt them to foreign
function calls; this mechanism is replaced by a function pointer in
the type's stgdict.
In the 'from_param' class methods, try the _as_parameter_ attribute if
other conversions are not possible.
This makes the documented _as_parameter_ mechanism work as intended.
Change the ctypes version number to 1.0.1.
|
|
|
|
|
|
|
|
|
|
| |
Replace UnicodeDecodeErrors raised during == and !=
compares of Unicode and other objects with a new
UnicodeWarning.
All other comparisons continue to raise exceptions.
Exceptions other than UnicodeDecodeErrors are also left
untouched.
|
|
|
|
| |
area because the size if unknown in source/callproc.c.
|
|
|
|
| |
Fixes klockwork issues #188, #189.
|
|
|
|
| |
Fixes klockwork issues #183, #184, #185.
|
|
|
|
| |
Fixes klockwork issue #207.
|
| |
|
|
|
|
|
| |
about the best we can do is call PyErr_WriteUnraisable and go on.
We won't be able to do the call below either, so verify delstr is valid.
|
| |
|
| |
|
|
|
|
| |
Klocwork 225-228
|
|
|
|
| |
Klocwork 281
|
|
|
|
| |
(Followup of Klocwork 274)
|
|
|
|
|
| |
Fix a bunch of refleaks in the init of the module. This would only be found
when running python -v.
|
|
|
|
| |
Klocwork 341-342
|
|
|
|
|
|
|
| |
that PyString_AsString() returns a valid pointer. (The problem can
arise when zlib.decompress doesn't return a string.)
Klocwork 346
|
|
|
|
| |
Klocwork 180-181
|
|
|
|
|
| |
Fix a bunch of refleaks in the init of the module. This would only be found
when running python -v.
|
|
|
|
|
|
| |
__oct__, __hex__ don't return a string.
Klocwork 308
|
|
|
|
|
|
|
|
| |
to write the .pyc to NULL.
Check results of PyList_GetItem() and PyModule_GetDict() are not NULL.
Klocwork 282, 283, 285
|
|
|
|
| |
Should fix most of Klocwork 234-272.
|
|
|
|
|
|
| |
Verify that PyEval_Get{Globals,Locals} returned valid pointers.
Klocwork 231-232
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
were failing due to inappropriate clipping of numbers larger than 2**31
with new-style classes. (typeobject.c) In reviewing the code for classic
classes, there were 2 problems. Any negative value return could be returned.
Always return -1 if there was an error. Also make the checks similar
with the new-style classes. I believe this is correct for 32 and 64 bit
boxes, including Windows64.
Add a test of classic classes too.
|
|
|
|
|
|
|
| |
I modified this patch some by fixing style, some error checking, and adding
XXX comments. This patch requires review and some changes are to be expected.
I'm checking in now to get the greatest possible review and establish a
baseline for moving forward. I don't want this to hold up release if possible.
|
| |
|
|
|
|
|
|
|
|
|
| |
protected by "if verbose:", which caused the test to fail on
all non-Windows boxes.
Note that I deliberately didn't convert this to unittest yet,
because I expect it would be even harder to debug this on Tru64
after conversion.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
appears to be utterly insane. Plug some theoretical
insecurities in the test script:
- Verify that the SIGALRM handler was actually installed.
- Don't call alarm() before the handler is installed.
- Move everything that can fail inside the try/finally,
so the test cleans up after itself more often.
- Try sending all the expected signals in
force_test_exit(), not just SIGALRM. Since that was
fixed to actually send SIGALRM (instead of invisibly
dying with an AttributeError), we've seen that sending
SIGALRM alone does not stop this from hanging.
- Move the "kill the child" business into the finally
clause, so the child doesn't survive test failure
to send SIGALRM to other tests later (there are also
baffling SIGALRM-related failures in test_socket).
- Cancel the alarm in the finally clause -- if the
test dies early, we again don't want SIGALRM showing
up to confuse a later test.
Alas, this still relies on timing luck wrt the spawned
script that sends the test signals, but it's hard to see
how waiting for seconds can so often be so unlucky.
test_threadedsignals: curiously, this test never fails
on Tru64, but doesn't normally signal SIGALRM. Anyway,
fixed an obvious (but probably inconsequential) logic
error.
|
|
|
|
|
|
| |
Ensure we don't pass NULL to free.
Klocwork #306 (at least the first part, checking malloc)
|
|
|
|
| |
Klocwork #298-299.
|
|
|
|
|
|
| |
Check seq in both portions of if/else.
Klocwork #289-290.
|
|
|
|
| |
Klocwork #214
|
|
|
|
| |
were not supposed to go it. Only Modules/_ctypes/cfields.c was supposed to be changed
|