summaryrefslogtreecommitdiffstats
path: root/Objects/cellobject.c
Commit message (Collapse)AuthorAgeFilesLines
* Untabify C files. Will watch buildbots.Antoine Pitrou2010-05-091-88/+88
|
* This reverts r63675 based on the discussion in this thread:Gregory P. Smith2008-06-091-2/+2
| | | | | | | http://mail.python.org/pipermail/python-dev/2008-June/079988.html Python 2.6 should stick with PyString_* in its codebase. The PyBytes_* names in the spirit of 3.0 are available via a #define only. See the email thread.
* Renamed PyString to PyBytesChristian Heimes2008-05-261-2/+2
|
* A little reformating of Py3k warningsBenjamin Peterson2008-04-271-1/+1
|
* Use PyErr_WarnPy3k throughoutBenjamin Peterson2008-04-271-3/+2
|
* Fix tabs.Georg Brandl2008-03-251-1/+1
|
* Make Py3k warnings consistent w.r.t. punctuation; also respect theGeorg Brandl2008-03-251-2/+3
| | | | EOL 80 limit and supply more alternatives in warning messages.
* cell_compare needs to return -2 instead of NULL.Steven Bethard2008-03-181-1/+1
|
* Add py3k warnings for object, type, cell and dict comparisons. This should ↵Steven Bethard2008-03-181-0/+6
| | | | resolve issue2342 and partly resolve issue2373.
* Prevent a crash with nested scopes, again caused by calling Py_DECREF when ↵Amaury Forgeot d'Arc2008-02-161-1/+3
| | | | | | the pointer is still present in the containing structure.
* Issue #1445: Fix a SystemError when accessing the ``cell_contents``Amaury Forgeot d'Arc2007-11-241-1/+6
| | | | attribute of an empty cell object. Now a ValueError is raised.
* PEP 3123: Provide forward compatibility with Python 3.0, while keepingMartin v. Löwis2007-07-211-2/+1
| | | | | backwards compatibility. Add Py_Refcnt, Py_Type, Py_Size, and PyVarObject_HEAD_INIT.
* Another problem reported by Coverity. Backport candidate.Neal Norwitz2006-06-301-0/+2
|
* Use Py_VISIT in all tp_traverse methods, instead of traversing manually orThomas Wouters2006-04-151-2/+1
| | | | | | | | using a custom, nearly-identical macro. This probably changes how some of these functions are compiled, which may result in fractionally slower (or faster) execution. Considering the nature of traversal, visiting much of the address space in unpredictable patterns, I'd argue the code readability and maintainability is well worth it ;P
* Use Py_CLEAR instead of in-place DECREF/XDECREF or custom macros, forThomas Wouters2006-04-151-2/+1
| | | | tp_clear methods.
* Previously, Python code had no easy way to access the contents of aGeorg Brandl2006-03-181-0/+19
| | | | | cell object. Now, a ``cell_contents`` attribute has been added (closes patch #1170323).
* Use new GC API.Neil Schemenauer2001-08-291-6/+6
|
* repr's converted to using PyString_FromFormat() instead of sprintf'ingBarry Warsaw2001-08-241-7/+5
| | | | | | into a hardcoded char* buffer. Closes patch #454743.
* Merge of descr-branch back into trunk.Tim Peters2001-08-021-1/+1
|
* Variety of small INC/DECREF patches that fix reported memory leaksJeremy Hylton2001-03-131-0/+1
| | | | | | | | | | | | | | | | | | | | | with free variables. Thanks to Martin v. Loewis for finding two of the problems. This fixes SF buf 405583. There is also a C API change: PyFrame_New() is reverting to its pre-2.1 signature. The change introduced by nested scopes was a mistake. XXX Is this okay between beta releases? cell_clear(), the GC helper, must decref its reference to break cycles. frame_dealloc() must dealloc all cell vars and free vars in addition to locals. eval_code2() setup code must INCREF cells it copies out of the closure. The STORE_DEREF opcode implementation must DECREF the object it passes to PyCell_Set().
* PEP 227 implementationJeremy Hylton2001-01-251-0/+115
A cell contains a reference to a single PyObject. It could be implemented as a mutable, one-element sequence, but the separate type has less overhead.