This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ronaldoussoren
Recipients Alexander.Belopolsky, eric.araujo, georg.brandl, ronaldoussoren, stefanholek
Date 2010-03-09.22:00:30
SpamBayes Score 9.0286807e-07
Marked as misclassified No
Message-id <1268172031.72.0.863621517773.issue6953@psf.upfronthosting.co.za>
In-reply-to
Content
Changing get_history_item to be 0-based would be a backward incompatible change.

The point of my report is that the documentation of the readline documentation should mention how the APIs actually behave, you currently have to hunt down that information in the documentation from libreadline.

Stefan's message does point to a potentional issue though: history_base is  not exposed to python code, and hence Python code cannot use the correct offset.  I don't understand the documentation for history_get in that same document though, it says "get the item at `offset`, starting from `history_base`". I don't understand if that means that `offset` must be at least `history_base` or something else (and won't read the readline sources to find out).
History
Date User Action Args
2010-03-09 22:00:31ronaldoussorensetrecipients: + ronaldoussoren, georg.brandl, eric.araujo, Alexander.Belopolsky, stefanholek
2010-03-09 22:00:31ronaldoussorensetmessageid: <1268172031.72.0.863621517773.issue6953@psf.upfronthosting.co.za>
2010-03-09 22:00:30ronaldoussorenlinkissue6953 messages
2010-03-09 22:00:30ronaldoussorencreate