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 r.david.murray
Recipients ckreddy, eric.smith, r.david.murray
Date 2018-06-08.15:05:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1528470312.32.0.592728768989.issue33806@psf.upfronthosting.co.za>
In-reply-to
Content
telnetlib provides a low level interface to the telnet protocol.  The dialog you mention appears to be transmitted on the telnet connection, so it is unlikely there is any bug or missing feature in telnetlib that would affect your problem.

The sentence in the docs you appear to be referring to ("Do not reopen an already connected instance.") is just telling you that once you have used to telnetlib to open a connection, don't call open again.  It has nothing to say about a telnet connection made by some other program.

So, you have an application level problem and should seek help on the python-list mailing list or some other general help forum.  Unless you can identify something *specific* in telnetlib (bug or missing feature) that prevents you from solving your problem, I don't think there's anything more to be done here.

(As an aside, have you tried sending /r/n after the a?)
History
Date User Action Args
2018-06-08 15:05:12r.david.murraysetrecipients: + r.david.murray, eric.smith, ckreddy
2018-06-08 15:05:12r.david.murraysetmessageid: <1528470312.32.0.592728768989.issue33806@psf.upfronthosting.co.za>
2018-06-08 15:05:12r.david.murraylinkissue33806 messages
2018-06-08 15:05:12r.david.murraycreate