RetroSearch Browse

Tue Feb 10 10:57:37 EST 2004 · https://mail.python.org/pipermail/python-dev/2004-February/042470.html

"Raymond Hettinger" <raymond.hettinger at verizon.net> wrote in message
news:00c401c3efa5$b08d5300$2008a044 at oemcomputer...
> risk is warranted.  The offending code would have to be by-passing
> the C API for lists and tinkering with the internals in atypical
> way (swapping one pointer for another and/or altering ob_size is
> typical; downward resizing the existing pointer is not).

Hasn't or can't such bypass and tinkering be defined as 'unsupported,
proceed at your own risk, and don't complain when internals change', just
as when accessing certain internals visible from Python code?

TJR

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2004-February/042470.html below:

[Python-Dev] Re: Optimization of the Year