<div dir="ltr">Gah, and anyway, the interpreter is likely not going to even let you get that far even if the C API worked. What *was* I thinking...I somehow over looked that minor detail.<br></div><div class="gmail_extra"><br><div class="gmail_quote">On 4 February 2017 at 21:59, Shaheed Haque <span dir="ltr"><<a href="mailto:srhaque@theiet.org" target="_blank">srhaque@theiet.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span class="">On 4 February 2017 at 21:56, Barry <span dir="ltr"><<a href="mailto:barry@barrys-emacs.org" target="_blank">barry@barrys-emacs.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="m_-1102236078397629829gmail-"><br>
<br>
> On 4 Feb 2017, at 21:35, Shaheed Haque <<a href="mailto:srhaque@theiet.org" target="_blank">srhaque@theiet.org</a>> wrote:<br>
><br>
> Hi Barry,<br>
><br>
> The tuple API does have a PyTuple_SetItem operation,<br>
<br>
</span>But that can only be used once to init the tuple. You cannot come back and replace a value.<br>
List is the only option if the array can be updated.<br></blockquote></span><div><br>I suspect you may well be right.<br> <span class="m_-1102236078397629829gmail-HOEnZb"></span><br><span class="m_-1102236078397629829gmail-HOEnZb"></span></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="m_-1102236078397629829gmail-HOEnZb"><font color="#888888">
Barry<br>
</font></span></blockquote></div><br></div></div>
</blockquote></div><br></div>