summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Add \ulink, grammar production markup.Fred Drake2001-07-061-0/+15
|
* Add support for \ulink and hyperlink grammars.Fred Drake2001-07-061-2/+151
| | | | | | | do_cmd_verbatiminput(): Write out a text file containing the content of the input file with a .txt extension, and add a link to it at the bottom of the presentation. This easier retrieval of example source code for copy & paste use.
* Revise a comment about styles I don't think LaTeX2HTML can generate,Fred Drake2001-07-061-1/+15
| | | | | | but which came from their default stylesheet. Add styles for the new hyperlinked grammar productions.
* Add new material on some markup that will be checked in shortly. ThisFred Drake2001-07-061-34/+137
| | | | | | | | | includes some minor new inline markup and markup to generate hyperlinked grammar productions. Adopt a "style guide" document -- this beats writing our own and means we'll have a chance at consistency, without having to make it all up ourselves.
* Packaged versions of the HTML format need to include any .txt files thatFred Drake2001-07-061-3/+3
| | | | | were generated by the use of the productionlist environment or the \verbatiminput macro.
* More names, yay!Fred Drake2001-07-061-0/+2
|
* Add entries for recently defined markup.Fred Drake2001-07-061-0/+23
|
* Simplification to mirror a better conversion specification and moreFred Drake2001-07-061-6/+1
| | | | powerful latex2esis.py.
* Allow optional arguments to LaTeX macros to span lines. This is legal inFred Drake2001-07-061-1/+1
| | | | | LaTeX and we have at least one occurance of that in the content, so this script needs to support it as well.
* bug #436596Fredrik Lundh2001-07-061-2/+2
| | | | re.findall doesn't take a maxsplit argument
* Once again, attempt to preserve $Revision$Barry Warsaw2001-07-060-0/+0
|
* Fix up a few style nits -- avoid "e.g." and "i.e." -- these makeFred Drake2001-07-0617-98/+105
| | | | | translation more difficult, as well as reading the English more difficult for non-native speakers.
* (py-version): Hopefully fixed my XEmacs settings so this doesn't getBarry Warsaw2001-07-061-1/+1
| | | | clobbered on checkin.
* Amazing. A very subtle change in policy in descr-branch actuallyGuido van Rossum2001-07-061-1/+1
| | | | | | | | | | | | | | | | found a bug here. Here's the deal: Class PyShell derives from class OutputWindow. Method PyShell.close() wants to invoke its parent method, but because PyShell long ago was inherited from class PyShellEditorWindow, it invokes PyShelEditorWindow.close(self). Now, class PyShellEditorWindow itself derives from class OutputWindow, and inherits the close() method from there without overriding it. Under the old rules, PyShellEditorWindow.close would return an unbound method restricted to the class that defined the implementation of close(), which was OutputWindow.close. Under the new rules, the unbound method is restricted to the class whose method was requested, that is PyShellEditorWindow, and this was correctly trapped as an error.
* Fix up a few style nits -- avoid "e.g." and "i.e." -- these makeFred Drake2001-07-061-4/+6
| | | | | | | | | translation more difficult, as well as reading the English more difficult for non-native speakers. Add an index entry for the Telnet protocol. Always refer to the protocol as Telnet instead of telnet.
* (py-continuation-offset): Update docstring to describe that thisBarry Warsaw2001-07-061-4/+9
| | | | | | | | additional offset is only applied to continuation lines for block opening statements. (py-compute-indentation): Only add py-continuation-offset if py-statement-opens-block-p is true.
* Fix up a few style nits -- avoid "e.g." and "i.e." -- these makeFred Drake2001-07-0612-103/+105
| | | | | translation more difficult, as well as reading the English more difficult for non-native speakers.
* SF bug #439104: Tuple richcompares has code-typo.Tim Peters2001-07-061-1/+1
| | | | | | Symptom: (1, 2, 3) <= (1, 2) returned 1. This was already fixed in CVS for tuples, but an isomorphic error was in the list richcompare code.
* Fix up a few style nits -- avoid "e.g." and "i.e." -- these makeFred Drake2001-07-061-58/+62
| | | | | translation more difficult, as well as reading the English more difficult for non-native speakers.
* When reading a continuation line, make sure we still use the transformedFred Drake2001-07-062-1/+9
| | | | | | | name when filling in the internal data structures, otherwise we incorrectly raise a KeyError. This fixes SF bug #432369.
* Explain the exit code for the wait() method, including a reference toFred Drake2001-07-061-1/+6
| | | | | | the os.W*() functions used to interpret the return value. This fixes SF bug #429361.
* Fix up a few style nits -- avoid "e.g." and "i.e." -- these makeFred Drake2001-07-062-23/+23
| | | | | translation more difficult, as well as reading the English more difficult for non-native speakers.
* Removed fpectlmodule.c and fpetestmodule.c from the Windows build. TheyTim Peters2001-07-051-30/+0
| | | | weren't functional under Windows even if enabled.
* The fpectl module does not work on Windows, so remove Windows from theFred Drake2001-07-051-2/+2
| | | | | | \platform statement. Also fix a minor style consistency nit in an example.
* Fix a markup error: do not omit a method's parameter list if it isFred Drake2001-07-051-1/+1
| | | | empty.
* Allow underscores in tag names and quote characters in unquoted attributeFred Drake2001-07-051-2/+2
| | | | | | | values. The change for attribute values matches the way Mozilla and Navigator view the world, at least. This closes SF bug #436621.
* Added more information on the differences between the htmllib and HTMLParserFred Drake2001-07-053-3/+16
| | | | modules.
* List constraints on xrange() objects.Guido van Rossum2001-07-051-8/+14
|
* Rip out tests for xrange() features no longer supported.Guido van Rossum2001-07-051-14/+0
|
* News about xrange().Guido van Rossum2001-07-051-0/+4
|
* Complete the xrange-simplification checkins: call PyRange_New() withGuido van Rossum2001-07-051-1/+1
| | | | fewer arguments.
* Rip out the fancy behaviors of xrange that nobody uses: repeat, slice,Guido van Rossum2001-07-053-229/+18
| | | | | contains, tolist(), and the start/stop/step attributes. This includes removing the 4th ('repeat') argument to PyRange_New().
* - minor cleanup, removed bogus commentsJust van Rossum2001-07-051-9/+13
| | | | | - make method reload handle __private attrs correctly - fixed whole word search
* don't crash when encountering bad marshal dataJust van Rossum2001-07-051-1/+2
|
* SF bug #438295: [Windows] __init__.py cause strange behaviorTim Peters2001-07-051-11/+28
| | | | | | | | | | Probable fix (the bug report doesn't have enough info to say for sure). find_init_module(): Insist on a case-sensitive match for __init__ files. Given __INIT__.PY instead, find_init_module() thought that was fine, but the later attempt to do find_module("__INIT__.PY") didn't and its caller silently suppressed the resulting ImportError. Now find_init_module() refuses to accept __INIT__.PY to begin with. Bugfix candidate; specific to platforms with case-insensitive filesystems.
* Do conversion of CFStrings to/from unicode.unknown2001-07-042-43/+255
|
* Set the default 8-bit encoding based on the system script and language.unknown2001-07-041-0/+2
|
* Don't promise mac-japanese encoding as we don't have a codec for it.unknown2001-07-041-1/+4
| | | | Return a reasonable name for the general macos exception (MacOS.Error).
* Added a non-recursive implementation of conjoin(), and a Knight's Tourunknown2001-07-041-2/+291
| | | | | | | | | | | | solver. In conjunction, they easily found a tour of a 200x200 board: that's 200**2 == 40,000 levels of backtracking. Explicitly resumable generators allow that to be coded as easily as a recursive solver (easier, actually, because different levels can use level-customized algorithms without pain), but without blowing the stack. Indeed, I've never written an exhaustive Tour solver in any language before that can handle boards so large ("exhaustive" == guaranteed to find a solution if one exists, as opposed to probabilistic heuristic approaches; of course, the age of the universe may be a blip in the time needed!).
* dummy checkin for testing, please ignoreunknown2001-07-041-1/+0
|
* 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)
generated by cgit v0.12 at 2024-11-23 02:11:16 (GMT)