| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Py_SAFE_DOWNCAST can evaluate its first argument multiple
times in a debug build. This caused two distinct assert-
failures in test_unicode run under a debug build. Rewrote
the code in trivial ways so that multiple evaluation of the
first argument doesn't hurt.
|
|
|
|
|
|
| |
mixing signed and unsigned types in comparison.
Relatedly, `dataSize` is declared as DWORD, not as
int, so change relevant cast from (int) to (DWORD).
|
| |
|
|
|
|
| |
whitespace.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
signed with unsigned types in comparison.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
test_file to fail on Windows in reality (can't delete
a still-open file), but a new bare "except:" hid that
test_file failed on Windows, and leaving behind the
still-open TESTFN caused a cascade of bogus failures
in later tests.
So, close the file, and stop hiding failure to unlink.
|
|
|
|
|
|
|
| |
* Allow the 3rd argument to generator.throw() to be None.
The 'raise' statement does the same, and anyway it follows the
general policy that optional arguments of built-ins should, when
reasonable, have a default value specifiable from Python.
|
|
|
|
| |
the *. Only some files/dirs were copied, not everything.)
|
| |
|
| |
|
|
|
|
|
|
|
| |
readline/readlines/read/readinto, loudly break by raising ValueError, rather
than silently deliver data out of order or hitting EOF prematurely.
Probably not a bugfix candidate, even though it affects no 'working' code.
|
|
|
|
| |
http://mail.python.org/pipermail/python-dev/2006-February/060524.html
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Proposed by Tim Peters.
|
|
|
|
|
| |
call_function(), rather than commenting on the lack of an explanation in a
comment.
|
| |
|
| |
|
|
|
|
| |
is an output parameter or not. Added support for that.
|
|
|
|
|
| |
of seconds, producing numbers 1000 times too large. It would be nice to
write a test for this, but how... (thanks mwh)
|
|
|
|
| |
keyword parameter.
|
| |
|
|
|
|
| |
Added 'extra' keyword argument handling to logging calls, as discussed on python-dev.
|
| |
|
|
|
|
|
|
| |
regrtest.py. If we grep for just "fail", that finds bsddb deadlock
messages, which presumably are just warnings. They don't cause
a test failure.
|
|
|
|
|
| |
It is out of date, though, thanks to lacking info on the arena API. It also
should eventually be removed in favor of updating PEP 339.
|
|
|
|
| |
Will port to Python 2.4.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Based on lsprof (patch #1212837) by Brett Rosen and Ted Czotter.
With further editing by Michael Hudson and myself.
History in svn repo: http://codespeak.net/svn/user/arigo/hack/misc/lsprof
* Module/_lsprof.c is the internal C module, Lib/cProfile.py a wrapper.
* pstats.py updated to display cProfile's caller/callee timings if available.
* setup.py and NEWS updated.
* documentation updates in the profiler section:
- explain the differences between the three profilers that we have now
- profile and cProfile can use a unified documentation, like (c)Pickle
- mention that hotshot is "for specialized usage" now
- removed references to the "old profiler" that no longer exists
* test updates:
- extended test_profile to cover delicate cases like recursion
- added tests for the caller/callee displays
- added test_cProfile, performing the same tests for cProfile
* TO-DO:
- cProfile gives a nicer name to built-in, particularly built-in methods,
which could be backported to profile.
- not tested on Windows recently!
|
| |
|
|
|
|
|
|
|
|
|
| |
- Call tp_dealloc on the static baseclass, not dynamic (which leads to
infinite loops with more than one baseclass)
- Call tp_new and tp_init on baseclasses (overridable)
-This line, and those below, will be ignored--
M bgen/bgenObjectDefinition.py
|
| |
|
|
|
|
| |
logging._handlers.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
is larger than FD_SETSIZE.
This can only be acheived with ulimit -n SOME_NUMBER_BIGGER_THAN_FD_SETSIZE
which is typically only available to root. Since this wouldn't normally
be run in a test (ie, run as root), it doesn't seem too worthwhile to
add a normal test. The bug report has one version of a test. I've
written another. Not sure what the best thing to do is.
Do the check before calling internal_select() because we can't set
an error in between Py_BEGIN_ALLOW_THREADS and Py_END_ALLOW_THREADS.
This seemed the clearest solution, ie handle before calling internal_select()
rather than inside. Plus there is at least one place outside
of internal_select() that needed to be handled.
Will backport.
|
| |
|
| |
|
| |
|