summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Patch 983206: distutils obeys LDSHARED env var. Removed the code inAnthony Baxter2004-10-134-3/+6
| | | | | Python's own setup.py that did the same thing (and tested on Solaris, where LDSHARED is needed...)
* Patch 977343, Solaris likes sys/loadavg.h. Added support for sys/loadavg.hAnthony Baxter2004-10-134-3/+13
| | | | detection to configure &c.
* 969574Anthony Baxter2004-10-132-0/+4
|
* Patch #975056 - fixes for restartable signals on *BSD. In addition,Anthony Baxter2004-10-135-48/+28
| | | | a few remaining calls to signal() were converted to PyOS_setsig().
* Fixed a small bug. doctest didn't handle unicode docstrings containingJim Fulton2004-10-133-3/+26
| | | | non-ascii characters.
* oops. how did _that_ happen?Anthony Baxter2004-10-131-0/+1
|
* Backing out the basic dependency checking (from pycon sprint).Anthony Baxter2004-10-135-145/+3
| | | | | | This support was only a first cut, and doesn't deserve to be in a released version (where we have to support it in an ongoing manner)
* Don't spend quite as much time looking for leaks on Windows, whereFredrik Lundh2004-10-131-2/+4
| | | | it's rather expensive to create new processes.
* normalize case when comparing directory names (problem reported byFredrik Lundh2004-10-131-1/+2
| | | | "Khalid A. B." on python-dev)
* removed info@pythonware.com referenceFredrik Lundh2004-10-131-2/+1
| | | | | (should probably remove all traces of _xmlrpclib, but I'll leave that for another day.)
* Add a comment explaining -kb.Martin v. Löwis2004-10-131-0/+1
|
* New helper remove_stderr_debug_decorations(). This test passes in aTim Peters2004-10-131-7/+24
| | | | | debug build on Windows now. More applications of the helper may be needed on non-Windows platforms.
* Kill several problems at once: test_poll() failed sometimes for me.Tim Peters2004-10-132-8/+11
| | | | | | | | | | | Turns out the mysterious "expected output" file contained exactly N dots, because test_poll() has a loop that *usually* went around N times, printing one dot on each loop trip. But there's no guarantee of that, because the exact value of N depended on the vagaries of scheduling time.sleep()s across two different processes. So stopped printing dots, and got rid of the expected output file. Add a loop counter instead, and verify that the loop goes around at least a couple of times. Also cut the minimum time needed for this test from 4 seconds to 1.
* test_stdout_none(): Don't print "banana" to the screen in the middleTim Peters2004-10-131-2/+5
| | | | | of the test. It's testing stdout in a different process, so it has to print something, but I didn't find "banana" to be self-explanatory.
* Windows test_creationflags() test: print msg to stderr informing theTim Peters2004-10-131-1/+2
| | | | | | tester that a DOS box is expected to flash. Slash the sleep from 2 seconds to a quarter second (why would we want to wait 2 seconds just to stare at a DOS box?).
* Folded long lines.Tim Peters2004-10-131-23/+42
|
* XXX about extreme expense of test_no_leaking() on Windows. I'm not sureTim Peters2004-10-131-0/+1
| | | | | | what this is trying to do. If it's necessary for it to create > 1000 processes, it should be controlled by a new resource and not run by default on Windows.
* Experience with Zope2's tests showed it's a Bad Idea to make unittestTim Peters2004-10-121-45/+35
| | | | | | display a test's docstring as "the name" of the test. So changed most test docstrings to comments, and removed the clearly useless ones. Now unittest reports the actual names of the test methods.
* Wrap long lines.Tim Peters2004-10-121-43/+67
|
* Whitespace normalization.Tim Peters2004-10-124-47/+43
|
* Supply the _subprocess module under 7.1. I'm not sure what the statusTim Peters2004-10-122-0/+6
| | | | of this should be on non-WIN32 Windows variants.
* Before this turns into an unreadable mess, follow PEP 7 by usingTim Peters2004-10-121-315/+340
| | | | hard tab indents in C code.
* Improvements when running pdb as a script.Johannes Gijsbers2004-10-121-16/+81
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Bug fixes: * Use fresh copy of globals/locals so the script being debugged can't access the pdb namespace (e.g.: p line_prefix will no longer work). * Remove pdb.py's path from sys.path. Having it in there is normally not a problem, but it could prove irritating when messing with PYTHONPATH or invoking pdb via /usr/bin/pdf. * You can now set a breakpoint on the script being debugged, even if the script doesn't end with a '.py' extension. Also, setting breakpoints with absolute paths now works reliably. Enhancements: * Go directly to the first line of the script. * Enter post-mortem debugging if the script being debugged doesn't catch an exception. * Restart the script being debugged and preserve debugger state when the script being debugged exits. Cleanup: * Moved the __main__ method into a main() function. * Kill the (undocumented, not in __all__) mainmodule/mainpyfile globals, add a mainpyfile attribute to pdb. Thanks Ilya Sandler for the patch!
* Typo fixAndrew M. Kuchling2004-10-121-1/+1
|
* Finish off PEP 324 section; fix Peter's last nameAndrew M. Kuchling2004-10-121-3/+69
|
* Start section for PEP 324Andrew M. Kuchling2004-10-121-0/+22
|
* Fix PEP numberAndrew M. Kuchling2004-10-121-1/+1
|
* Added Peter Astrand's subprocess module.Fredrik Lundh2004-10-125-0/+2170
|
* Don't use mutable values for method defaults.Raymond Hettinger2004-10-121-2/+6
|
* Add two itemsAndrew M. Kuchling2004-10-111-0/+14
|
* Document that on Unix, the 'cmd' argument to the os.popen2/3/4 andJohannes Gijsbers2004-10-114-27/+75
| | | | | | | | | | popen2.popen2/3/4 functions can be a sequence. All texts are a variation on the following: On \UNIX, \var{cmd} may be a sequence, in which case arguments will be passed directly to the program without shell intervention (as with \function{os.spawnv()}). If \var{cmd} is a string it will be passed to the shell (as with \function{os.system()}).
* This is jiwon's patch to fix:Michael W. Hudson2004-10-111-1/+6
| | | | [ 1042238 ] Lib/compiler chokes on certain genexps
* Open source files in universal newlines mode.Michael W. Hudson2004-10-111-1/+1
|
* Added note about the new usegmt argument to email.Utils.formatdate().Barry Warsaw2004-10-111-0/+1
|
* Added a usegmt flag to email.Utils.formatdate - this allows it to beAnthony Baxter2004-10-115-7/+28
| | | | | used to replace rfc822.formatdate for protocols like HTTP (where 'GMT' must be the timezone string).
* SF patch 1044089: New C API function PyEval_ThreadsInitialized(), by NickTim Peters2004-10-117-10/+24
| | | | | Coghlan, for determining whether PyEval_InitThreads() has been called. Also purged the undocumented+unused _PyThread_Started int.
* Revert rev 2.35. It was based on erroneous reasoning -- the currentTim Peters2004-10-101-15/+8
| | | | | | | thread's id can't get duplicated, because (of course!) the current thread is still running. The code should work either way, but reverting the gratuitous change should make backporting easier, and gets the bad reasoning out of 2.35's new comments.
* PyInterpreterState_New(), PyThreadState_New(): use malloc/free directly.Tim Peters2004-10-102-4/+26
| | | | | | This appears to finish repairs for SF bug 1041645. This is a critical bugfix.
* find_key(): This routine wasn't thread-correct, and accounts for theTim Peters2004-10-102-5/+22
| | | | | | release-build failures noted in bug 1041645. This is a critical bugfix. I'm not going to backport it, though (no time).
* PyGILState_Release(): If we need to delete the TLS entry for this thread,Tim Peters2004-10-091-8/+15
| | | | | that must be done under protection of the GIL, for reasons explained in new comments.
* All known bugs are closed, and Python 2.4b1 is coming out soon, so bumpBarry Warsaw2004-10-091-1/+1
| | | | email's version number to 3.0b1.
* Fix SF bug # 1030941. In _parsegen(), in the clause where we'reBarry Warsaw2004-10-091-3/+7
| | | | | | | capturing_preamble but we found a StartBoundaryNotFoundDefect, we need to consume all lines from the current position to the EOF, which we'll set as the epilogue of the current message. If we're not at EOF when we return from here, the outer message's capturing_preamble assertion will fail.
* An example message for SF bug # 1030941.Barry Warsaw2004-10-091-0/+20
|
* test_missing_start_boundary(): A test for SF bug # 1030941.Barry Warsaw2004-10-091-0/+15
|
* _PyGILState_Init(), PyGILState_Ensure(): Since PyThread_set_key_value()Tim Peters2004-10-091-2/+5
| | | | | | | | | can fail, check its return value, and die if it does fail. _PyGILState_Init(): Assert that the thread doesn't already have an association for autoTLSkey. If it does, PyThread_set_key_value() will ignore the attempt to (re)set the association, which the code clearly doesn't want.
* Document the results of painful reverse-engineering of the "portable TLS"Tim Peters2004-10-091-6/+84
| | | | | | | | | code. PyThread_set_key_value(): It's clear that this code assumes the passed-in value isn't NULL, so document that it must not be, and assert that it isn't. It remains unclear whether existing callers want the odd semantics actually implemented by this function.
* Fix for SF bug # 1010102. The default is PureProxy not SMTPProxy.Barry Warsaw2004-10-091-1/+1
|
* __init__(): Coerce the input_charset to unicode (with ascii encoding) beforeBarry Warsaw2004-10-091-2/+3
| | | | | | calling .lower() on it. This fixes the problem described in SF patch # 866982 where in the tr_TR.ISO-8859-9 locale, 'I'.lower() isn't 'i'. unicodes are locale insensitive.
* Style guide & consistency changes. No semantic changes.Tim Peters2004-10-092-29/+41
|
* Trim trailing whitespace.Tim Peters2004-10-091-8/+8
|