summaryrefslogtreecommitdiffstats
path: root/Include/sliceobject.h
Commit message (Collapse)AuthorAgeFilesLines
* Merge p3yk branch with the trunk up to revision 45595. This breaks a fairThomas Wouters2006-04-211-0/+1
| | | | | | | | | | | | | | | | | | | | number of tests, all because of the codecs/_multibytecodecs issue described here (it's not a Py3K issue, just something Py3K discovers): http://mail.python.org/pipermail/python-dev/2006-April/064051.html Hye-Shik Chang promised to look for a fix, so no need to fix it here. The tests that are expected to break are: test_codecencodings_cn test_codecencodings_hk test_codecencodings_jp test_codecencodings_kr test_codecencodings_tw test_codecs test_multibytecodec This merge fixes an actual test failure (test_weakref) in this branch, though, so I believe merging is the right thing to do anyway.
* Merge ssize_t branch.Martin v. Löwis2006-02-151-5/+5
|
* Wrote down the invariants of some common objects whose structure isArmin Rigo2004-10-281-2/+2
| | | | | | | | | | exposed in header files. Fixed a few comments in these headers. As we might have expected, writing down invariants systematically exposed a (minor) bug. In this case, function objects have a writeable func_code attribute, which could be set to code objects with the wrong number of free variables. Calling the resulting function segfaulted the interpreter. Added a corresponding test.
* Excise DL_EXPORT from Include.Mark Hammond2002-08-121-5/+5
| | | | Thanks to Skip Montanaro and Kalle Svensson for the patches.
* This is my nearly two year old patchMichael W. Hudson2002-06-111-0/+3
| | | | | | | | | [ 400998 ] experimental support for extended slicing on lists somewhat spruced up and better tested than it was when I wrote it. Includes docs & tests. The whatsnew section needs expanding, and arrays should support extended slices -- later.
* ANSI-fication and Py_PROTO extermination.Fred Drake2000-07-091-6/+6
|
* Add DL_IMPORT(returntype) for all officially exported functions.Guido van Rossum1998-12-041-2/+2
|
* Forget about Ellipses b/w compatibility.Guido van Rossum1996-10-161-1/+0
|
* Ellipses -> Ellipsis rename (the dictionary really says that it shouldGuido van Rossum1996-10-111-4/+4
| | | | | | | | be Ellipsis!). Bumped the API version because a linker-visible symbol is affected. Old C code will still compile -- there's a b/w compat macro. Similarly, old Python code will still run, builtin exports both Ellipses and Ellipsis.
* Slice and ellipses interfaceGuido van Rossum1996-07-301-0/+40