summaryrefslogtreecommitdiffstats
path: root/Doc
Commit message (Collapse)AuthorAgeFilesLines
* lots of markup nits, most commonly Unix/unix --> \UNIXFred Drake2006-07-3020-49/+49
|
* [Bug #793553] Correct description of keyword arguments for SSL authenticationAndrew M. Kuchling2006-07-301-4/+4
|
* markup cleanupsFred Drake2006-07-292-11/+11
|
* Fix case for 'Unix'Andrew M. Kuchling2006-07-292-2/+2
|
* Follow TeX's conventions for hyphensAndrew M. Kuchling2006-07-291-3/+3
|
* fix minor markup error that introduced extra punctuationFred Drake2006-07-291-2/+1
|
* Add a comment to the csv reader documentation that explains why theSkip Montanaro2006-07-291-0/+11
| | | | | treatment of newlines changed in 2.5. Pulled almost verbatim from a comment by Andrew McNamara in <http://python.org/sf/1465014>.
* SF bug #1193966: Weakref types documentation misplacedFred Drake2006-07-292-84/+87
| | | | | | The information about supporting weakrefs with types defined in C extensions is moved to the Extending & Embedding manual. Py_TPFLAGS_HAVE_WEAKREFS is no longer mentioned since it is part of Py_TPFLAGS_DEFAULT.
* [Patch #1068277] Clarify that os.path.exists() can return False depending on ↵Andrew M. Kuchling2006-07-291-2/+5
| | | | permissions. Fred approved committing this patch in December 2004!
* [Patch #1490989 from Skip Montanaro] Mention debugging builds in the API ↵Andrew M. Kuchling2006-07-292-5/+56
| | | | documentation. I've changed Skip's patch to point to Misc/SpecialBuilds and fiddled with the markup a bit.
* emphasize and oddball nuance of LaTeX comment syntaxFred Drake2006-07-291-4/+4
|
* document the footnote usage patternFred Drake2006-07-292-3/+17
|
* make the reference to older versions of the documentation a linkFred Drake2006-07-291-2/+3
| | | | to the right page on python.org
* Reorganize the docs for 'file' and 'open()' after some discussion with Fred.Andrew M. Kuchling2006-07-291-63/+74
| | | | | | | | | | | | | | | | | We want to encourage users to write open() when opening a file, but open() was described with a single paragraph and 'file' had lots of explanation of the mode and bufsize arguments. I've shrunk the description of 'file' to cross-reference to the 'File objects' section, and to open() for an explanation of the arguments. open() now has all the paragraphs about the mode string. The bufsize argument was moved up so that it isn't buried at the end; now there's 1 paragraph on mode, 1 on bufsize, and then 3 more on mode. Various other edits and rearrangements were made in the process. It's probably best to read the final text and not to try to make sense of the diffs.
* expunge the xmlcore changes:Fred Drake2006-07-292-22/+0
| | | | | | | | | | | | | | | | | | | 41667, 41668 - initial switch to xmlcore 47044 - mention of xmlcore in What's New 50687 - mention of xmlcore in the library reference re-apply xmlcore changes to xml: 41674 - line ending changes (re-applied manually), directory props 41677 - add cElementTree wrapper 41678 - PSF licensing for etree 41812 - whitespace normalization 42724 - fix svn:eol-style settings 43681, 43682 - remove Python version-compatibility cruft from minidom 46773 - fix encoding of \r\n\t in attr values in saxutils 47269 - added XMLParser alias for cElementTree compatibility additional tests were added in Lib/test/test_sax.py that failed with the xmlcore changes; these relate to SF bugs #1511497, #1513611
* Set bug/patch count. Take a bow, everyone!Andrew M. Kuchling2006-07-291-1/+1
|
* [Bug #1528258] Mention that the 'data' argument can be None.Andrew M. Kuchling2006-07-291-3/+13
| | | | | | The constructor docs referred the reader to the add_data() method's docs, but they weren't very helpful. I've simply copied an earlier explanation of 'data' that's more useful.
* Fix typoMatt Fleming2006-07-291-1/+1
|
* Typo fixAndrew M. Kuchling2006-07-291-1/+1
|
* [Bug #1530382] Document SSL.server(), .issuer() methodsAndrew M. Kuchling2006-07-291-0/+52
|
* [Bug #1519571] Document some missing functions: setup(), title(), done()Andrew M. Kuchling2006-07-291-0/+39
|
* [Bug #1529157] Mention raw_input() and input(); while I'm at it, reword the ↵Andrew M. Kuchling2006-07-291-4/+7
| | | | description a bit
* Reword paragraph to match the order of the subsequent sectionsAndrew M. Kuchling2006-07-291-2/+2
|
* Update URLAndrew M. Kuchling2006-07-291-1/+1
|
* Add exampleAndrew M. Kuchling2006-07-291-0/+13
|
* Bug #835255: The "closure" argument to new.function() is now documented.Georg Brandl2006-07-291-2/+5
|
* Bug #1529871: The speed enhancement patch #921466 broke Python's compliancePhillip J. Eby2006-07-281-1/+19
| | | | | | with PEP 302. This was fixed by adding an ``imp.NullImporter`` type that is used in ``sys.path_importer_cache`` to cache non-directory paths and avoid excessive filesystem operations during imports.
* Add example. Should I propagate this example to all the other DBM-ish ↵Andrew M. Kuchling2006-07-281-0/+26
| | | | modules, too?
* Don't overwrite built-in name; add some blank lines for readabilityAndrew M. Kuchling2006-07-281-1/+3
|
* Add exampleAndrew M. Kuchling2006-07-281-1/+44
|
* Add exampleAndrew M. Kuchling2006-07-281-0/+12
|
* Typo fixAndrew M. Kuchling2006-07-281-1/+1
|
* [Patch #1529811] Correction to description of r|* modeAndrew M. Kuchling2006-07-281-3/+3
|
* Live with that "the hardware address" is an ill-definedTim Peters2006-07-281-12/+15
| | | | | | | concept, and that different ways of trying to find "the hardware address" may return different results. Certainly true on both of my Windows boxes, and in different ways (see whining on python-dev).
* Patch #1520294: Support for getset and member descriptors in types.py,Barry Warsaw2006-07-272-4/+47
| | | | | | | | | | | | | | | | | | | | | | | | | | | | inspect.py, and pydoc.py. Specifically, this allows for querying the type of an object against these built-in C types and more importantly, for getting their docstrings printed in the interactive interpreter's help() function. This patch includes a new built-in module called _types which provides definitions of getset and member descriptors for use by the types.py module. These types are exposed as types.GetSetDescriptorType and types.MemberDescriptorType. Query functions are provided as inspect.isgetsetdescriptor() and inspect.ismemberdescriptor(). The implementations of these are robust enough to work with Python implementations other than CPython, which may not have these fundamental types. The patch also includes documentation and test suite updates. I commit these changes now under these guiding principles: 1. Silence is assent. The release manager has not said "no", and of the few people that cared enough to respond to the thread, the worst vote was "0". 2. It's easier to ask for forgiveness than permission. 3. It's so dang easy to revert stuff in svn, that you could view this as a forcing function. :) Windows build patches will follow.
* Add exampleAndrew M. Kuchling2006-07-271-0/+12
|
* Add exampleAndrew M. Kuchling2006-07-271-0/+14
|
* Reword paragraphAndrew M. Kuchling2006-07-271-3/+2
|
* If binhex is higher-level than binascii, it should come first in the chapterAndrew M. Kuchling2006-07-271-1/+1
|
* Mention base64 module; rewrite last sentence to be more positiveAndrew M. Kuchling2006-07-271-4/+5
|
* Add punctuation mark; add some examplesAndrew M. Kuchling2006-07-271-1/+25
|
* Update URL; add exampleAndrew M. Kuchling2006-07-271-1/+19
|
* Repair typosAndrew M. Kuchling2006-07-271-1/+1
|
* Add missing wordAndrew M. Kuchling2006-07-271-1/+2
|
* Typo fix ('publically' is rare, poss. non-standard)Andrew M. Kuchling2006-07-271-1/+1
|
* Add exampleAndrew M. Kuchling2006-07-271-0/+37
|
* Resync optparse with Optik 1.5.3: minor tweaks for/to tests.Greg Ward2006-07-231-1/+1
|
* More RFC 2231 improvements for the email 4.0 package. As Mark Sapiro rightlyBarry Warsaw2006-07-211-1/+10
| | | | | | | | | | | | | | | | | | | | | | | | points out there are really two types of continued headers defined in this RFC (i.e. "encoded" parameters with the form "name*0*=" and unencoded parameters with the form "name*0="), but we were were handling them both the same way and that isn't correct. This patch should be much more RFC compliant in that only encoded params are %-decoded and the charset/language information is only extract if there are any encoded params in the segments. If there are no encoded params then the RFC says that there will be no charset/language parts. Note however that this will change the return value for Message.get_param() in some cases. For example, whereas before if you had all unencoded param continuations you would have still gotten a 3-tuple back from this method (with charset and language == None), you will now get just a string. I don't believe this is a backward incompatible change though because the documentation for this method already indicates that either return value is possible and that you must do an isinstance(val, tuple) check to discriminate between the two. (Yeah that API kind of sucks but we can't change /that/ without breaking code.) Test cases, some documentation updates, and a NEWS item accompany this patch.
* markup fixFred Drake2006-07-201-2/+2
|
* Updated documentation for TimedRotatingFileHandler relating to how rollover ↵Vinay Sajip2006-07-201-7/+5
| | | | files are named. The previous documentation was wrongly the same as for RotatingFileHandler.
generated by cgit v0.12 at 2025-03-01 07:24:21 (GMT)