Ok, then how about prefixing with _, adding a comment saying in big, bold letters: FOR DEBUGGING PURPOSES ONLY, THIS LEAKS, and only defining in a debug build? n -- On 4/11/06, Jeremy Hylton <jeremy at alum.mit.edu> wrote: > It's intended as an internal debugging API. I find it very convenient > for adding with a printf() here and there, which is how it got added > long ago. It should really have a comment mentioning that it leaks > the repr object, and starting with an _ wouldn't be bad either. > > Jeremy > > On 4/11/06, Neal Norwitz <nnorwitz at gmail.com> wrote: > > On 4/11/06, Raymond Hettinger <raymond.hettinger at verizon.net> wrote: > > > > > > > It strikes me that it should not be used, or maybe renamed to _PyObject_REPR. > > > > Should removing or renaming it be done in 2.5 or in Py3K? > > > > > > Since it is intrinsically buggy, I would support removal in Py2.5 > > > > +1 on removal. Google only turned up a handleful of uses that I saw. > > > > n > > _______________________________________________ > > Python-Dev mailing list > > Python-Dev at python.org > > http://mail.python.org/mailman/listinfo/python-dev > > Unsubscribe: http://mail.python.org/mailman/options/python-dev/jeremy%40alum.mit.edu > > >
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4