summaryrefslogtreecommitdiffstats
path: root/Doc/ext
Commit message (Collapse)AuthorAgeFilesLines
* Fixed "u#" parser marker to pass through Unicode objects as-is withoutMarc-André Lemburg2002-01-091-0/+2
| | | | | | going through the buffer interface API. Added tests for this to the _testcapi module and updated docs.
* Replace the "Cookbook approach" with the approach documented inFred Drake2001-12-131-15/+166
| | | | | PC/example_nt/readme.txt; this one does not rely on any external scripts. This "fixes" SF bug #221671 and most of SF bug #225003.
* Added discussion of protecting against screwing up the exception state inFred Drake2001-12-111-0/+48
| | | | an object's deallocator, including an example of how to do this.
* More info about the cycle detector.Guido van Rossum2001-12-071-2/+4
|
* Trivial spelling repair on new cyclic garbage text.Tim Peters2001-12-071-2/+2
|
* Added more information about reference counting limitations and the cycleFred Drake2001-12-071-0/+27
| | | | | detector. This closes SF bug #484950.
* Clarify the description of the creation of an owned reference from an APIFred Drake2001-11-291-5/+5
| | | | | function. This closes SF bug #486657.
* Add an index entry for the discussion of PyEval_CallObject().Fred Drake2001-11-291-8/+9
| | | | This is related to SF bug #485165.
* Clean up some markup cruft. A number of the macros that take noFred Drake2001-11-284-27/+27
| | | | | | | | parameters (like \UNIX) are commonly entered using an empty group to separate the markup from a following inter-word space; this is not needed when the next character is punctuation, or the markup is the last thing in the enclosing group. These cases were marked inconsistently; the empty group is now *only* used when needed.
* Exhibit good form in C code: always provide docstrings in method tables, andFred Drake2001-11-173-19/+25
| | | | | always fill in all slots of table entries. Fixed a few minor markup errors.
* Use the \note and \warning macros where appropriate.Fred Drake2001-10-201-6/+6
|
* Document required return values -1, 0, 1 for tp_compare handler, asGuido van Rossum2001-10-161-2/+11
| | | | suggested in SF patch #424475. Also document exception return.
* SF [#466125] PyLong_AsLongLong works for any integer.Tim Peters2001-09-301-0/+5
| | | | | | Generalize PyLong_AsLongLong to accept int arguments too. The real point is so that PyArg_ParseTuple's 'L' code does too. That code was undocumented (AFAICT), so documented it.
* Remove comment that no longer applies.Fred Drake2001-09-261-3/+0
|
* Document the rule that Python.h must be included before any standardFred Drake2001-09-061-2/+4
| | | | headers. This is the final checkin for SF bug #458768.
* Do not #include <stdio.h> since Python.h already does that.Fred Drake2001-09-061-1/+0
|
* Use the standard argument convention for main(), and conform to theFred Drake2001-09-061-1/+2
| | | | Python/C style guide.
* On Fred's suggestion, convert sprintf() examples to useBarry Warsaw2001-08-291-19/+11
| | | | | PyString_FromFormat(). Also fixed one grammar problem, and a few other mark-up issues. Sample code not checked.
* Split "Extending & Embedding" into separate files, one per chapter.Fred Drake2001-08-206-3158/+3155
|
* A large contribution from Dave Kuhlman describing what each of the slotsFred Drake2001-08-151-6/+385
| | | | | | | | | in the type object is used for, for many of the more commonly used slots. Thanks! (But there is still a lot more to write on this topic.) Markup and organizational changes by your friendly neighborhood documentation czar.
* Lots of new text and example code on embedding Python in C, contributedFred Drake2001-08-042-1/+309
| | | | | | | | | | | by Albert Hofkamp. Some editing has been done for style and markup consistency. This also supplies an example of importing modules and calling a function defined in the module, so this closes SF bug #440037 as well. (The long example code was moved to a separate file so that it would format properly.)
* Patch #411138: Rename config.h to pyconfig.h. Closes bug #231774.Martin v. Löwis2001-07-261-2/+2
|
* Corrected a section reference (title was wrong).Fred Drake2001-07-201-5/+8
| | | | | Added information on the return values of PyArg_ParseTuple() and PyArg_ParseTupleAndKeywords().
* Minor change to match the style guide.Fred Drake2001-07-141-1/+1
|
* Fix up a few style nits -- avoid "e.g." and "i.e." -- these makeFred Drake2001-07-061-22/+22
| | | | | translation more difficult, as well as reading the English more difficult for non-native speakers.
* Update to include the license information in a less annoying place.Fred Drake2001-06-201-0/+3
|
* Added new parser markers 'et' and 'et#' which do not recode stringMarc-André Lemburg2001-05-021-0/+12
| | | | | | | objects but instead assume that they use the requested encoding. This is needed on Windows to enable opening files by passing in Unicode file names.
* Markup nit: For the Python documents, we use \empt instead of \textit.Fred Drake2001-03-191-1/+1
|
* Py_BuildValue(): Add "D" conversion to create a Python complex value fromFred Drake2001-03-121-0/+3
| | | | | | | a Py_complex C value. Patch by Walter Dörwald. This closes SF patch #407148.
* There was a real leak in the "export a C API" example; fix that one.Fred Drake2001-03-021-4/+9
| | | | | (There are too many initspam() functions; they need to be renamed post-beta.)
* There is no longer a -X option to the interpreter, so remove the commentsFred Drake2001-03-021-21/+16
| | | | | | | | | | on how PyErr_NewException() behaves in that case. Clarify why an owned reference is kept in an extension module's variable that refers to the result of PyErr_NewException(); one reader thought that was a leak. Clean up some tabs and simplify some markup.
* Michael Hudson <mwh21@cam.ac.uk>:Fred Drake2001-02-191-9/+440
| | | | | | New material on defining extension types. Thanks! (Small markup adjustments made, but this is mostly as received.)
* Worked around bug SF #125880: changed the text of three sections thatFred Drake2001-01-221-3/+3
| | | | really nasty TeX source to "bleed" into the PDF "bookmarks".
* Updates to reflect pending changes to the XML conversion process.Fred Drake2000-11-221-1/+1
|
* Corrected a number of typos reported by Gilles CivarioFred Drake2000-11-171-12/+3
| | | | | | <gcivario@users.sourceforge.net>. This closes bug #122562.
* Fix cut & paste error that describes three paramters when there are onlyFred Drake2000-11-021-4/+3
| | | | | | | two [bug #119729]. Update use of distutils.sysconfig that "broke" when Greg W. changed the API [bug #119645].
* All acknowledgements have been moved to the Doc/ACKS file.Fred Drake2000-10-261-25/+21
| | | | | | | Adjusted to reflect the rename of Setup.in to Setup.dist. Added pointer to the "Distributing Python Modules" manual in the appropriate place.
* Added some comments on the interaction of reload() and extension modules.Fred Drake2000-10-021-1/+6
| | | | Based on comments from Chris Barker <cbarker@jps.net>.
* Include the new text on reporting bugs in a few useful places.Fred Drake2000-09-211-0/+5
| | | | This closes SourceForge bug #114792.
* Special case the "s#" PyArg_Parse() token for Unicode objects:Marc-André Lemburg2000-09-211-4/+4
| | | | | | | | "s#" will now return a pointer to the default encoded string data of the Unicode object instead of a pointer to the raw UTF-16 data. The latter is still available via PyObject_AsReadBuffer().
* Add a brief section on linking Python as an embedded scripting language.Fred Drake2000-09-081-0/+37
| | | | This closes SourceForge bug #110833.
* Markup errors: \cfuntion -> \cfunctionFred Drake2000-08-111-3/+3
|
* Added descriptions of the new parser markers for PyArg_ParseTuple().Marc-André Lemburg2000-08-031-16/+77
|
* needs a spaceGreg Stein2000-07-091-1/+1
|
* Remove the only Py_PROTO in the docs.Fred Drake2000-07-091-1/+1
|
* Small grammatical correction from Frank Stajano. Added comment withFred Drake2000-06-301-2/+9
| | | | suggestion from Frank for an example and further explanation.
* Enhanced memory-reference information in the description of Py_BuildValue(),Fred Drake2000-06-281-1/+5
| | | | based on response from Frank Stajano <fstajano@uk.research.att.com>.
* Added memory-reference information to the description of Py_BuildValue(),Fred Drake2000-06-281-1/+6
| | | | based on comments from Frank Stajano <fstajano@uk.research.att.com>.
* Oops, better also note that the module initialization function must beFred Drake2000-05-101-0/+2
| | | | extern "C" for C++.
* Section "The Module's Method Table and Initialization Function":Fred Drake2000-05-101-7/+10
| | | | | | Explain that the name of the initialization function must be init<module>(). Omission noted by Daniel Kozan <crum@dev-group.com>.