summaryrefslogtreecommitdiffstats
path: root/Tools/scripts/combinerefs.py
Commit message (Collapse)AuthorAgeFilesLines
* bpo-39573: Use the Py_TYPE() macro (GH-21433)Victor Stinner2020-07-101-1/+1
| | | Replace obj->ob_type with Py_TYPE(obj).
* bpo-22831: Use "with" to avoid possible fd leaks in tools (part 2). (GH-10927)Serhiy Storchaka2019-03-301-4/+5
|
* Issue #5319: New Py_FinalizeEx() API to exit with status 120 on failureMartin Panter2015-11-301-2/+2
|
* Fix missing or wrong shebangs and missing executable bits for scripts (#10318)Éric Araujo2011-07-261-0/+0
|
* convert shebang lines: python -> python3Benjamin Peterson2010-03-111-1/+1
|
* Fix a last use of file() that should be open().Guido van Rossum2007-12-061-1/+2
|
* Convert print statements to function calls in Tools/.Collin Winter2007-08-031-7/+7
|
* Docstring clarifications.Tim Peters2003-04-191-7/+12
|
* Don't double-space the "??? new object ..." messages.Guido van Rossum2003-04-181-1/+1
|
* Heh -- I checked in an old version of this, at a time I documented theTim Peters2003-04-181-3/+1
| | | | internal read() as being a generator but hadn't yet changed it into one.
* _Py_PrintReferenceAddresses(): also print the type name. In real useTim Peters2003-04-181-0/+124
I'm finding some pretty baffling output, like reprs consisting entirely of three left parens. At least this will let us know what type the object is (it's not str -- there's no quote character in the repr). New tool combinerefs.py, to combine the two output blocks produced via PYTHONDUMPREFS.