| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
| |
Will backport
|
| |
|
|
| |
two gigabytes.
|
| |
|
|
|
|
|
|
|
|
|
| |
test suite.
For urllib2, move the import of gopherlib into the
only function that uses it: users (including the
test suite) certainly shouldn't see a deprecation
warning just because they import urllib2! If they
actually use gopher_open(), fine, _then_ they should
see a deprecation warning.
|
| |
|
|
|
| |
code _importing_ gopherlib instead of gopherlib's
call to warnings.warn.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
return address using smtplib.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
| |
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
|
| | |
|
| |
|
|
| |
Added 'extra' keyword argument handling to logging calls, as discussed on python-dev.
|
| | |
|
| |
|
|
| |
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!
|
| | |
|
| |
|
|
| |
logging._handlers.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Not sure why/how _handlers/_handlerList is out of sync. This could
indicate a deeper problem.
In test_logging, the only absolutely necessary change to get working
was tcpserver.abort = 1. But we don't want to wait infinitely
to join the threads, so give a 2.0 second timeout.
There doesn't appear to be a need for a local abort variable
in serve_until_stopped, so just use the instance member.
Note the problem is only on HEAD, not in 2.4.
|
| |
|
|
|
|
|
|
|
|
|
| |
on both Unix (SVR4 and BSD) and Windows. Restores behaviour of passing -1
for anonymous memory on Unix. Use MAP_ANONYMOUS instead of _ANON since
the latter is deprecated according to Linux (gentoo) man pages.
Should we continue to allow mmap.mmap(0, length) to work on Windows?
0 is a valid fd.
Will backport bugfix portions.
|
| | |
|
| | |
|
| |
|
|
|
| |
Port from Python 2.3/email 2.5: Add a test for the tm_yday field is 1 in the
return of parsedate().
|
| |
|
|
|
| |
touch the recursion limit. The applied patch inlines the recursive
__helper method in a non-recursive way.
|
| |
|
|
| |
as python builtin bsddb.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
tty opened by os.openpty() isn't always a tty according to os.isatty(), when
it's tested inside the process that opened it. Doesn't affect actual
functionality, as using a tty this way is rarely, if ever, useful. Ignoring
the failure allows the test for actual functionality to continue.
Will backport to 2.4-maint.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Expand set of errors caught in set_context(). Some new errors, some
old error messages changed for consistency.
Fixed error checking in generator expression code. The first set of
tests were impossible condition given the grammar. In general, the
ast code uses REQ() for those sanity checks.
Fix some error handling for augmented assignments. As comments in the
code explain, set_context() ought to work here, but I got unexpected
crashes when I tried it. Should come back to this.
Add note to Grammar that yield expression is a special case.
Add doctest cases for SyntaxErrors raised by ast.c.
|
| |
|
|
| |
(test cases and dbobj wrapping)
|
| |
|
|
|
|
|
|
|
|
| |
before the listener was ready (on gentoo x86 buildslave). This
caused the listener to not exit normally since nobody connected to it
(waited in accept()). The exception was raised in the other thread
and the test failed.
This fix doesn't completely eliminate the race, but should make it
near impossible to trigger. Hopefully it's good enough.
|
| | |
|
| |
|
|
| |
Will backport.
|
| |
|
|
| |
synchronization and termination.
|
| | |
|
| |
|
|
|
| |
specifications, raises IOErrors when proxies for unsupported protocols
are defined, and uses the https proxy on https redirections.
|
| |
|
|
|
|
|
| |
- The path separator isn't "/" on Windows.
- Leaving behind a read-only file causes cascades
of bogus failures on Windows.
|
| | |
|
| | |
|
| |
|
|
| |
ref leaks
|
| | |
|
| | |
|
| | |
|
