summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Fix for SF bug #425868.unknown2001-07-041-3/+3
| | | | | | We should not depend on two spaces between words, so use the white space after the to-be-encoded word only as lookahead and don't actually consume it in the regular expression.
* Clean up a bare except: clause.unknown2001-07-041-1/+1
|
* Clean up a bare except: clause.unknown2001-07-041-1/+1
|
* Make the implementations of getElementsByTagName() andFred Drake2001-07-041-11/+5
| | | | | getElementsByTagNameNS() consistent in form as well as functionality (cosmetic).
* Only write out one blank line before the request data.Fred Drake2001-07-042-3/+3
| | | | This closes SF patch #419459.
* Null commit with -f option to force an uprev and put HEADs firmly on the trunk.Kurt B. Kaiser2001-07-040-0/+0
|
* Null commit with -f option to force an uprev and put HEADs firmly on the trunk.Kurt B. Kaiser2001-07-040-0/+0
|
* This change adjusts the profiling/tracing support so that the commonFred Drake2001-07-033-47/+67
| | | | | | | | | | | | | | | | path (with no profile/trace function) through eval_code2() and eval_frame() avoids several checks. In the common cases of calls, returns, and exception propogation, eval_code2() and eval_frame() used to test two values in the thread-state: the profiling function and the tracing function. With this change, a flag is set in the thread-state if either of these is active, allowing a single check to suffice when both are NULL. This also simplifies the code needed when either function is in use but is already active (to avoid profiling/tracing the profiler/tracer); the flag is set to 0 when the profile/trace code is entered, allowing the same check to suffice for "already in the tracer" for call/return/ exception events.
* bug #416670Fredrik Lundh2001-07-031-16/+87
| | | | | added copy/deepcopy support to SRE (still not enabled, since it's not covered by the test suite)
* bug #232815Fredrik Lundh2001-07-031-1/+1
| | | | | ch is unsigned, so testing for negative values doesn't make sense (as noticed by the OpenVMS compiler)
* Marked the parameters to Stats.print_*() as optional.Fred Drake2001-07-021-3/+3
| | | | This closes SF bug #438032.
* reapplied darryl gallion's minimizing repeat fix. I'm still not 100%Fredrik Lundh2001-07-023-2/+4
| | | | | sure about this one, but test #133283 now works even with the fix in place, and so does the test suite. we'll see what comes up...
* Add another name.Fred Drake2001-07-021-0/+1
|
* pythonware repository roundtrip (untabification)Fredrik Lundh2001-07-021-12/+13
|
* added martin's BIGCHARSET patch to SRE 2.1.1. martin reports 2xFredrik Lundh2001-07-024-31/+107
| | | | speedups for certain unicode character ranges.
* Avoid using os.path.normcase() on sys.path elements; doing so causes pathsFred Drake2001-07-021-19/+22
| | | | | | to be presented in an unfamiliar case on case-preserving filesystems. This closes SF patch #436173.
* merged with pythonware's SRE 2.1.1 codebaseFredrik Lundh2001-07-022-5/+98
|
* Added the new unicode defines. Not really tested yet, but Python compiles ↵Jack Jansen2001-07-021-0/+9
| | | | again at least.
* Nuke hard tabs.Tim Peters2001-07-023-244/+242
|
* Whitespace normalization; the plat-riscos file didn't even get byTim Peters2001-07-021-6/+6
| | | | tabnanny.py.
* Add tentative 2.1.1 Windows build numbers.Tim Peters2001-07-021-0/+4
|
* A clever union-find implementation from c.l.py, due to David Eppstein.Tim Peters2001-07-021-0/+77
| | | | | This is another one that leaks memory without an explict clear! Time to bite this bullet.
* Added WeakLink...Generator classes (should have done that ages ago). These ↵Jack Jansen2001-07-012-0/+22
| | | | | | check the c-function pointer for being NULL before calling it and raise UnimplementedError if it is. This allows system libs to be weak-linked, thereby allowing us to generate functions that are only available on some OS versions without getting a NULL dereference if the function isn't available.
* - Use weaklink generators so we can support OSX-only calls without crashing ↵Jack Jansen2001-07-012-5/+41
| | | | | | on OS9. - Convert CFString to/from Python strings. Currently always MacRoman, to be fixed later (as is unicode support). Python->CFString conversion is automatic.
* Derive an industrial-strength conjoin() via cross-recursion loop unrolling,Tim Peters2001-06-301-9/+83
| | | | and fiddle the conjoin tests to exercise all the new possible paths.
* Turns out Neil didn't intend for *all* of his gen-branch work to getTim Peters2001-06-294-46/+78
| | | | | | | | | | | | | | | | | | | | committed. tokenize.py: I like these changes, and have tested them extensively without even realizing it, so I just updated the docstring and the docs. tabnanny.py: Also liked this, but did a little code fiddling. I should really rewrite this to *exploit* generators, but that's near the bottom of my effort/benefit scale so doubt I'll get to it anytime soon (it would be most useful as a non-trivial example of ideal use of generators; but test_generators.py has already grown plenty of food-for-thought examples). inspect.py: I'm sure Ping intended for this to continue running even under 1.5.2, so I reverted this to the last pre-gen-branch version. The "bugfix" I checked in in-between was actually repairing a bug *introduced* by the conversion to generators, so it's OK that the reverted version doesn't reflect that checkin.
* Use the more conventional "self" as the name of the self parameter in anFred Drake2001-06-291-1/+1
| | | | example. It actually confused a reader.
* Correct a markup error for an accented character.Fred Drake2001-06-291-1/+1
| | | | Reported by Milan Zamazal <pdm@zamazal.org>.
* Removed some stray periods, and fix up a number of visible markupFred Drake2001-06-291-18/+19
| | | | | | | consistency errors (mostly omitted "()" at the end of function and method names). Reported by Milan Zamazal <pdm@zamazal.org>.
* Two more names.Fred Drake2001-06-291-0/+2
|
* SourceForge bug #437041:Fred Drake2001-06-291-8/+8
| | | | | Use a portable format in the example that creates a timestamp suitable for use in email, also updating it and the footnote from RFC 822 to RFC 2822.
* Simplify an example based on comment from Thomas Holenstein <thomas@hex.ch>:Fred Drake2001-06-291-4/+1
| | | | | Do not use an extra flag variable to test only once in one subsequent if statement.
* Solve SF bug #231249: cgi.py opens too many (temporary) files.Guido van Rossum2001-06-291-4/+12
| | | | | | | | | | | | | | | | | | | | | | class FieldStorage: this patch changes read_lines() and co. to use a StringIO() instead of a real file. The write() calls are redirected to a private method that replaces it with a real, external file only when it gets too big (> 1000 bytes). This avoids problems in forms using the multipart/form-data encoding with many fields. The original code created a temporary file for *every* field (not just for file upload fields), thereby sometimes exceeding the open file limit of some systems. Note that the simpler solution "use a real file only for file uploads" can't be used because the form field parser has no way to tell which fields correspond to file uploads. It's *possible* but extremely unlikely that this would break someone's code; they would have to be stepping way outside the documented interface for FieldStorage and use f.file.fileno(), or depend on overriding make_file() to return a file-like object with additional known properties.
* Added a simple but general backtracking generator (conjoin), and a coupleTim Peters2001-06-291-1/+162
| | | | | | | | | examples of use. These poke stuff not specifically targeted before, incl. recursive local generators relying on nested scopes, ditto but also inside class methods and rebinding instance vars, and anonymous partially-evaluated generators (the N-Queens solver creates a different column-generator for each row -- AFAIK this is my invention, and it's really pretty <wink>). No problems, not even a new leak.
* Added CFURL support, and got base chaining to really work.Jack Jansen2001-06-283-46/+547
|
* Make basechain a class variable in stead of initializing it in __init__. ↵Jack Jansen2001-06-281-1/+1
| | | | That way it's more easily overridden.
* Another "if 0:" hack, this time to complain about otherwise invisibleTim Peters2001-06-282-2/+94
| | | | | | "return expr" instances in generators (which latter may be generators due to otherwise invisible "yield" stmts hiding in "if 0" blocks). This was fun the first time, but this has gotten truly ugly now.
* removed "register const" from scalar arguments to the unicodeFredrik Lundh2001-06-272-35/+35
| | | | predicates
* CFArray, CFData and CFDictonary are now covered, but mainly opaque.Jack Jansen2001-06-273-9/+2372
| | | | CFStrings are in better shape, but Unicode support and automatic conversion to/from Python strings remains to be done.
* Added a couple more types that Apple has taken a fancy to.Jack Jansen2001-06-271-1/+3
|
* Add more items that need to be written aboutAndrew M. Kuchling2001-06-271-0/+24
|
* Default to ucs2 when no argument to --enable-unicode is specified.Martin v. Löwis2001-06-272-29/+21
|
* make wchar_t usable again on Windows (this enables the MBCS codecs)Fredrik Lundh2001-06-271-0/+7
|
* Revise the interface to the profiling and tracing support for theFred Drake2001-06-273-151/+183
| | | | | | | | | | | | | | | | | | Python interpreter. This change adds two new C-level APIs: PyEval_SetProfile() and PyEval_SetTrace(). These can be used to install profile and trace functions implemented in C, which can operate at much higher speeds than Python-based functions. The overhead for calling a C-based profile function is a very small fraction of a percent of the overhead involved in calling a Python-based function. The machinery required to call a Python-based profile or trace function been moved to sysmodule.c, where sys.setprofile() and sys.setprofile() simply become users of the new interface. As a side effect, SF bug #436058 is fixed; there is no longer a _PyTrace_Init() function to declare.
* Revise the interface to the profiling and tracing support for theFred Drake2001-06-272-2/+16
| | | | | | | | | | | | | | | Python interpreter. This change adds two new C-level APIs: PyEval_SetProfile() and PyEval_SetTrace(). These can be used to install profile and trace functions implemented in C, which can operate at much higher speeds than Python-based functions. The overhead for calling a C-based profile function is a very small fraction of a percent of the overhead involved in calling a Python-based function. The machinery required to call a Python-based profile or trace function been moved to sysmodule.c, where sys.setprofile() and sys.setprofile() simply become users of the new interface.
* use Py_UNICODE_WIDE instead of USE_UCS4_STORAGE and Py_UNICODE_SIZEFredrik Lundh2001-06-275-16/+18
| | | | tests.
* Replace the text with a link to the PEP-ified version.Barry Warsaw2001-06-271-1113/+3
|
* Remove duplicate ', ' in dbhash.open()'s argument list.Thomas Wouters2001-06-271-1/+1
|
* This no longer leaks memory when run in an infinite loop. However,Tim Peters2001-06-271-81/+58
| | | | | | | | | | | | | | | | | | | | | that required explicitly calling LazyList.clear() in the two tests that use LazyList (I added a LazyList Fibonacci generator too). A real bitch: the extremely inefficient first version of the 2-3-5 test *looked* like a slow leak on Win98SE, but it wasn't "really": it generated so many results that the heap grew over 4Mb (tons of frames! the number of frames grows exponentially in that test). Then Win98SE malloc() starts fragmenting address space allocating more and more heaps, and the visible memory use grew very slowly while the disk was thrashing like mad. Printing fewer results (i.e., keeping the heap burden under 4Mb) made that illusion vanish. Looks like there's no hope for plugging the LazyList leaks automatically short of adding frameobjects and genobjects to gc. OTOH, they're very easy to break by hand, and they're the only *kind* of plausibly realistic leaks I've been able to provoke. Dilemma.
* Encode surrogates in UTF-8 even for a wide Py_UNICODE.Martin v. Löwis2001-06-275-17/+48
| | | | | | | Implement sys.maxunicode. Explicitly wrap around upper/lower computations for wide Py_UNICODE. When decoding large characters with UTF-8, represent expected test results using the \U notation.
generated by cgit v0.12 at 2024-11-11 10:29:29 (GMT)