summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* Issue2564: Prevent a hang in "import test.autotest", which runs the entire testAmaury Forgeot d'Arc2008-04-082-5/+3
| | | | | | | suite as a side-effect of importing the module. - in test_capi, a thread tried to import other modules - re.compile() imported sre_parse again on every call.
* Add itemsAndrew M. Kuchling2008-04-081-2/+65
|
* Suppress compilation of py3_ files upon installation.Martin v. Löwis2008-04-081-1/+1
|
* Typographical fix: 32bit -> 32-bit, 64bit -> 64-bitAndrew M. Kuchling2008-04-081-4/+4
|
* Typo fixAndrew M. Kuchling2008-04-071-2/+2
|
* Write PEP 3127 section; add itemsAndrew M. Kuchling2008-04-071-8/+82
|
* #2525: update timezone info examples in the docs.Georg Brandl2008-04-071-8/+38
|
* Make the "private CRT" case work, by editing theMartin v. Löwis2008-04-071-5/+17
| | | | manifest in DLLs to refer to the root copy of the CRT.
* Drop support for 7.1 CRT.Martin v. Löwis2008-04-071-38/+5
|
* Make private_crt feature object a global variable.Martin v. Löwis2008-04-071-1/+1
|
* Delete ALLUSERS property merged from CRT merge module, so that per-user ↵Martin v. Löwis2008-04-071-0/+5
| | | | installations become possible again.
* changed "2500 components" to "several thousand" since the number keepsMark Summerfield2008-04-071-2/+3
| | | | growning:-)
* Use the new PyFile_IncUseCount & PyFile_DecUseCount calls appropriatlyGregory P. Smith2008-04-072-0/+19
| | | | | within the standard library. These modules use PyFile_AsFile and later release the GIL while operating on the previously returned FILE*.
* Bug #2388: Fix gcc warnings when compiling with --enable-unicode=ucs4.Martin v. Löwis2008-04-073-6/+25
|
* correct heading underline for new "Cross-compiling on Windows" sectionMark Hammond2008-04-071-1/+1
|
* Issue #2513: enable 64bit cross compilation on windows.Mark Hammond2008-04-0716-65/+323
|
* Make file objects as thread safe as the underlying libc FILE* implementation.Gregory P. Smith2008-04-065-83/+373
| | | | | | | | | | | close() will now raise an IOError if any operations on the file object are currently in progress in other threads. Most code was written by Antoine Pitrou (pitrou). Additional testing, documentation and test suite cleanup done by me (gregory.p.smith). Fixes issue 815646 and 595601 (as well as many other bugs and references to this problem dating back to the dawn of Python).
* Add enough debugging information to diagnose failures where theJeffrey Yasskin2008-04-061-5/+14
| | | | | | | | HandlerBException is ignored, and fix one such problem, where it was thrown during the __del__ method of the previous Popen object. We may want to find a better way of printing verbose information so it's not spammy when the test passes.
* Don't run kill_python as part of the build process. Change the buildbots so ↵Trent Nelson2008-04-064-24/+18
| | | | they have to call it explicitly instead.
* typeSkip Montanaro2008-04-061-1/+1
|
* From issue 1753245 - better _winreg support for x64.Mark Hammond2008-04-061-0/+133
| | | | | Adds _winreg.DisableReflectionKey, EnableReflectionKey, QueryReflectionKey, KEY_WOW64_64KEY and KEY_WOW64_32KEY.
* Fix test_distutils to not fail when running 'make test' from a Python buildThomas Wouters2008-04-052-1/+23
| | | | | | | | | directory that is not the source directory (ie, one created using '/path/to/source/configure'.) Leaves this test very slightly degraded in that particular case, compared to the build-in-sourcedir case, but that case isn't a particularly strong test either: neither test the actual path that will be used after installing. There isn't a particularly good way to test this, and a poor test beats a failing test.
* Declare inittimezone static.Skip Montanaro2008-04-051-2/+3
|
* Write PEP 3119 sectionAndrew M. Kuchling2008-04-051-18/+119
|
* Mention that the tuple returned by __reduce__ is pickled as normal.Georg Brandl2008-04-051-2/+3
|
* Markup fixes; write PEP 3118 sectionAndrew M. Kuchling2008-04-051-19/+61
|
* Add script to merge msvcr90.Martin v. Löwis2008-04-051-0/+70
|
* Add two features to distinguish between private and SxS CRT.Martin v. Löwis2008-04-051-1/+7
|
* Extend sizes of various fields, to support the CRT90 merge module.Martin v. Löwis2008-04-051-59/+59
|
* Prevent test_sqlite from hanging on older versions of sqlite.Neal Norwitz2008-04-051-0/+8
| | | | | | | | | | The problem is that when trying to do the second insert, sqlite seems to sleep for a very long time. Here is the output from strace: read(6, "SQLite format 3\0\4\0\1\1\0@ \0\0\0\1\0\0\0\0"..., 1024) = 1024 nanosleep({4294, 966296000}, <unfinished ...> I don't know which version this was fixed in, but 3.2.1 definitely fails.
* Various editsAndrew M. Kuchling2008-04-051-16/+45
|
* Markup fix; explain what interval timers do; typo fixAndrew M. Kuchling2008-04-051-2/+8
|
* Minor editsAndrew M. Kuchling2008-04-051-3/+3
|
* Revert r62152 (Issue #2550). Being able to observe the results of all the ↵Trent Nelson2008-04-041-76/+0
| | | | buildbots was certainly useful. All of the platforms that have some form of BSD lineage -- FreeBSD, OS X, Solaris and Tru64 -- all pass the test. Windows and Linux, on the other hand, don't. Windows I knew about, Linux was a surprise. Knowing this, I believe a more appropriate fix will revolve around test_support.bind_socket() -- this method needs to return a port that nothing in the system has bound already. The best way to do this may just be to rely on ephemeral ports, rather than having the user specify a desired port, then fall back to four random ports, then try 0.
* News entry for: Sync with files from the just released libffi 3.0.5 version.Thomas Heller2008-04-041-0/+4
|
* More files from libffi 3.0.5.Thomas Heller2008-04-044-22/+20
| | | | Removed libffi.pc.in because it is not needed for ctypes.
* Issue 2550: extend test_socket.py to test SO_REUSEADDR semantics when bind() ↵Trent Nelson2008-04-041-0/+76
| | | | is called on identical (host, port) combinations in two separate sockets. This should raise an EADDRINUSE socket.error in all cases, irrespective of whether or not SO_REUSEADDR is set on the sockets. However, with Windows, when SO_REUSEADDR is set on the sockets, no error is thrown (an error is thrown when the option isn't set), which results in an extremely wedged python process whenever accept() is called on either of the bound sockets. I'm committing this test now to observe if it's only Windows that has this behaviour (via the buildbots). Note: this WILL break all Windows buildbots for now; once I've observed the results on other platforms, I'll revert, then start looking into a patch.
* Oops again. EINTR is in errno, not signal.Jeffrey Yasskin2008-04-041-1/+1
|
* Sync with files from the just released libffi 3.0.5 version.Thomas Heller2008-04-045-2/+1246
|
* stupid, stupid, stupid!Fred Drake2008-04-041-1/+0
|
* my previous change did what I said it should not: it changed the currentFred Drake2008-04-042-7/+48
| | | | | | | directory to the directory in which the setup.py script lived (which made __file__ wrong) fixed, with test that the script is run in the current directory of the caller
* Issue #2544: On HP-UX systems, use 'gcc -shared' for linking when gccThomas Heller2008-04-043-3/+14
| | | | is used as compiler.
* Issue #2543: Make ctypes compatible (again) with Python 2.3, 2.4, and 2.5.Thomas Heller2008-04-043-27/+39
|
* - Issue #2385: distutils.core.run_script() makes __file__ available, so theFred Drake2008-04-043-1/+46
| | | | | controlled environment will more closely mirror the typical script environment. This supports setup.py scripts that refer to data files.
* Doh! os.read() raises an OSError, not an IOError when it's interrupted.Jeffrey Yasskin2008-04-041-2/+5
| | | | | And fix some flakiness in test_itimer_prof, which could detect that the timer had reached 0 before the signal arrived announcing that fact.
* post release updatesBarry Warsaw2008-04-041-1/+25
|
* #1733757: the interpreter would hang on shutdown, if the function set by ↵Amaury Forgeot d'Arc2008-04-033-7/+41
| | | | | | | | | | | | sys.settrace calls threading.currentThread. The correction somewhat improves the code, but it was close. Many thanks to the "with" construct, which turns python code into C calls. I wonder if it is not better to sys.settrace(None) just after running the __main__ module and before finalization.
* Make kill_python a little more forgiving if it can't obtain a snapshot of ↵Trent Nelson2008-04-031-5/+9
| | | | module information for a given python[_d].exe process. Failing here was too pessimistic; the python[_d].exe process may be owned by another user, which is the case in some buildbot environments.
* Add the correct OutputFile values for debug builds. Fixes r62129's commit.Trent Nelson2008-04-031-0/+2
|
* Reimplement kill_python. The existing version had a number of flaws, ↵Trent Nelson2008-04-0313-99/+513
| | | | | | | | | | | | | | | | | | | namely, it didn't work for x64 and it wasn't precise about which python_d.exe it was killing -- it just killed the first one it came across that happened to have 'pcbuild\python_d.exe' or 'build\python_d.exe' in it's path. The new version has been rewritten from the ground up and now lives in PCbuild, instead of Tools\buildbot, and it has also been incorporated into the Visual Studio solution (pcbuild.sln) as 'kill_python'. The solution has also been altered such that kill_python is called where necessary in the build process in order to prevent any linking errors due to open file locks. In lieu of this, all of the existing bits and pieces in Tools\buildbot that called out to kill_python at various points have also been removed as they are now obsolete. Tested on both Win32 and x64. Change set (included to improve usefulness of svnmerge log entry): M PCbuild\pythoncore.vcproj M PCbuild\pcbuild.sln M PCbuild\release.vsprops A PCbuild\kill_python.vcproj M PCbuild\debug.vsprops A PCbuild\kill_python.c D Tools\buildbot\kill_python.bat D Tools\buildbot\kill_python.mak M Tools\buildbot\build.bat D Tools\buildbot\Makefile M Tools\buildbot\build-amd64.bat M Tools\buildbot\buildmsi.bat D Tools\buildbot\kill_python.c
generated by cgit v0.12 at 2024-10-24 21:14:57 (GMT)