summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Fix a warning on alphaNeal Norwitz2006-04-281-1/+1
|
* Fix some warnings on Mac OS X 10.4Neal Norwitz2006-04-283-21/+9
|
* Try to really fix the slow buildbots this time.Neal Norwitz2006-04-281-0/+1
| | | | | | Printing to stdout, doesn't mean the data was actually written. It depends on the buffering, so we need to flush. This will hopefully really fix the buildbots getting killed due to no output on the slow bots.
* Add some whitespace to be more consistent.Neal Norwitz2006-04-281-11/+13
|
* Add more ignores of ImportWarnings; these are all just potential triggersThomas Wouters2006-04-271-1/+3
| | | | | (since they won't trigger if zlib is already sucessfully imported); they were found by grepping .py files, instead of looking at warning output :)
* - Add new Warning class, ImportWarningThomas Wouters2006-04-276-7/+60
| | | | | | | | | | | | | | - Warn-raise ImportWarning when importing would have picked up a directory as package, if only it'd had an __init__.py. This swaps two tests (for case-ness and __init__-ness), but case-test is not really more expensive, and it's not in a speed-critical section. - Test for the new warning by importing a common non-package directory on sys.path: site-packages - In regrtest.py, silence warnings generated by the build-environment because Modules/ (which is added to sys.path for Setup-created modules) has 'zlib' and '_ctypes' directories without __init__.py's.
* Added SVN access for Steven Bethard and Talin, for PEP updating.David Goodger2006-04-271-0/+7
|
* Do the small-memory run of big-meormy tests using a prime number, ratherThomas Wouters2006-04-271-1/+1
| | | | | than a convenient power-of-2-and-multiple-of-5, so incorrect testing algorithms fail more easily.
* Some style fixes and size-calculation fixes. Also do the small-memory runThomas Wouters2006-04-271-16/+21
| | | | | using a prime number, rather than a convenient power-of-2-and-multiple-of-5, so incorrect testing algorithms fail more easily.
* Rerun the libffi configuration if any of the files used for thatThomas Heller2006-04-271-1/+6
| | | | are newer then fficonfig.py.
* Some more size-estimate fixes, for large-list-tests.Thomas Wouters2006-04-271-2/+2
|
* markup fixGeorge Yoshida2006-04-271-4/+4
|
* Mention the xmlrpclib.Error base class, which is used in one of the examplesAndrew M. Kuchling2006-04-271-3/+5
|
* [Bug #1477140] Import Error base classAndrew M. Kuchling2006-04-271-1/+1
|
* [Bug #1477102] Add necessary import to exampleAndrew M. Kuchling2006-04-271-0/+1
| | | | | | | This may be a useful style question for the docs -- should examples show the necessary imports, or should it be assumed that the reader will figure it out? In the What's New, I'm not consistent but usually opt for omitting the imports.
* Bump document versionAndrew M. Kuchling2006-04-271-1/+1
|
* Now that 2.5a2 is out, revert to the current dateAndrew M. Kuchling2006-04-271-1/+1
|
* Tagging for release of Python 2.5a2Anthony Baxter2006-04-271-0/+1
|
* 2.5a2v2.5a2Anthony Baxter2006-04-271-1/+1
|
* 2.5a2Anthony Baxter2006-04-275-5/+10
|
* add missing wordFred Drake2006-04-271-1/+1
|
* - update version numbers in file names again, until we have a better wayFred Drake2006-04-271-6/+12
| | | | - elaborate instructions for Cygwin support (closes SF #839709)
* one more place to use the current Python versionFred Drake2006-04-261-2/+2
|
* Fix build on MIPS for libffi. I haven't tested this yet because IHye-Shik Chang2006-04-264-2/+15
| | | | don't have an access on MIPS machines. Will be tested by buildbot. :)
* Some more test-size-estimate fixes: test_append and test_insert trigger aThomas Wouters2006-04-261-3/+7
| | | | list resize, which overallocates.
* Add tests for += and *= on strings, and fix the memory-use estimate for theThomas Wouters2006-04-261-3/+37
| | | | list.extend tests (they were estimating half the actual use.)
* Use GS- and bufferoverlowU.lib where appropriate, for AMD64.Martin v. Löwis2006-04-2610-11/+11
|
* Whitespace normalization.Tim Peters2006-04-262-922/+922
|
* The result of SF patch #1471578: big-memory tests for strings, lists andThomas Wouters2006-04-264-3/+1013
| | | | | | tuples. Lots to be added, still, but this will give big-memory people something to play with in 2.5 alpha 2, and hopefully get more people to write these tests.
* Add labels to all sectionsAndrew M. Kuchling2006-04-261-11/+11
|
* [Bug #1475080] Fix exampleAndrew M. Kuchling2006-04-261-2/+2
|
* Fix an error in the last contextlib.closing exampleNick Coghlan2006-04-261-3/+3
|
* Fix this test on Solaris. There can be embedded \r, so don't just replaceNeal Norwitz2006-04-261-2/+2
| | | | the one at the end.
* Patch from Aldo Cortesi (OpenBSD buildbot owner).Neal Norwitz2006-04-261-7/+14
| | | | | | | | | | After the patch (45590) to add extra debug stats to the gc module, Python was crashing on OpenBSD due to: Fatal Python error: Interpreter not initialized (version mismatch?) This seems to occur due to calling collect() when initialized (in pythonrun.c) is set to 0. Now, the import will occur in the init function which shouldn't suffer this problem.
* minor adjustment suggested by Peter GephardtFred Drake2006-04-261-1/+1
|
* markup fixes, cleanupFred Drake2006-04-262-38/+67
|
* Rev 45706 renamed stuff in contextlib.py, but didn't renameTim Peters2006-04-261-8/+8
| | | | | | | | | | | | | | uses of it in test_with.py. As a result, test_with has been skipped (due to failing imports) on all buildbot boxes since. Alas, that's not a test failure -- you have to pay attention to the 1 skip unexpected on PLATFORM: test_with kinds of output at the ends of test runs to notice that this got broken. It's likely that more renaming in test_with.py would be desirable.
* Implement MvL's improvement on __context__ in Condition;Guido van Rossum2006-04-251-5/+1
| | | | | this can just call __context__ on the underlying lock. (The same change for Semaphore does *not* work!)
* Fix compiler warnings on Darwin.Thomas Heller2006-04-251-5/+5
| | | | | Patch by Brett Canon, see https://sourceforge.net/tracker/?func=detail&atid=532156&aid=1475959&group_id=71702
* Define MAXPATHLEN to be at least PATH_MAX, if that's defined. Python usesThomas Wouters2006-04-253-0/+12
| | | | | | | | | MAXPATHLEN-sized buffers for various output-buffers (like to realpath()), and that's correct on BSD platforms, but not Linux (which uses PATH_MAX, and does not define MAXPATHLEN.) Cursory googling suggests Linux is following a newer standard than BSD, but in cases like this, who knows. Using the greater of PATH_MAX and 1024 as a fallback for MAXPATHLEN seems to be the most portable solution.
* Fix SF bug #1476111: SystemError in socket sendto. The AF_INET6 andThomas Wouters2006-04-251-0/+16
| | | | | | AF_PACKET cases in getsockaddrarg were missing their own checks for tuple-ness of the address argument, which means a confusing SystemError was raised by PyArg_ParseTuple instead.
* minor tweakGeorge Yoshida2006-04-251-1/+1
|
* SF bug/patch #1433877: string parameter to ioctl not null terminatedThomas Wouters2006-04-253-13/+12
| | | | | | | The new char-array used in ioctl calls wasn't explicitly NUL-terminated; quite probably the cause for the test_pty failures on Solaris that we circumvented earlier. (I wasn't able to reproduce it with this patch, but it has been somewhat elusive to start with.)
* Rework context terminologyAndrew M. Kuchling2006-04-251-21/+22
|
* Add two items; easy_install is now off the table, though pkgutil still isAndrew M. Kuchling2006-04-251-1/+14
|
* Fix markup glitch in unittest docs. Will backport.Thomas Wouters2006-04-251-1/+1
|
* Fix latex typoNick Coghlan2006-04-251-1/+1
|
* Move the PEP 343 documentation and implementation closer to theNick Coghlan2006-04-257-139/+163
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | terminology in the alpha 1 documentation. - "context manager" reverts to its alpha 1 definition - the term "context specifier" goes away entirely - contextlib.GeneratorContextManager is renamed GeneratorContext There are still a number of changes relative to alpha 1: - the expression in the with statement is explicitly called the "context expression" in the language reference - the terms 'with statement context', 'context object' or 'with statement context' are used in several places instead of a bare 'context'. The aim of this is to avoid ambiguity in relation to the runtime context set up when the block is executed, and the context objects that already exist in various application domains (such as decimal.Context) - contextlib.contextmanager is renamed to contextfactory This best reflects the nature of the function resulting from the use of that decorator - decimal.ContextManager is renamed to WithStatementContext Simple dropping the 'Manager' part wasn't possible due to the fact that decimal.Context already exists and means something different. WithStatementContext is ugly but workable. A technically unrelated change snuck into this commit: contextlib.closing now avoids the overhead of creating a generator, since it's trivial to implement that particular context manager directly.
* Revert previous change, SKIP had a versionadded elsewhereNeal Norwitz2006-04-251-1/+0
|
* Restore Walters nameNeal Norwitz2006-04-251-1/+1
|
generated by cgit v0.12 at 2024-11-27 00:50:27 (GMT)