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 vitaly.krug
Recipients christian.heimes, vitaly.krug
Date 2018-03-08.21:37:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1520545029.73.0.467229070634.issue33023@psf.upfronthosting.co.za>
In-reply-to
Content
Hi Christian, thank you for following up. Here is my use case, and perhaps you can suggest something else that will work:

I am refactoring the transport layer in the Pika AMQP client library. The user provides an ssl.SSLContext instance for connecting to an AMQP broker (e.g., RabbitMQ). Pika will resolve the hostname via getaddrinfo and make attempts to establish TCP and AMQP connection to the candidate IP addresses until one succeeds in establishing an AMQP connection over SSL. Each connection attempt will require a fresh unadulterated clone of the ssl.SSLContext instance provided by user to avoid any side-effects from prior connection attempts.

How can I obtain this pristine clone cleanly for each new connection attempt?
History
Date User Action Args
2018-03-08 21:37:09vitaly.krugsetrecipients: + vitaly.krug, christian.heimes
2018-03-08 21:37:09vitaly.krugsetmessageid: <1520545029.73.0.467229070634.issue33023@psf.upfronthosting.co.za>
2018-03-08 21:37:09vitaly.kruglinkissue33023 messages
2018-03-08 21:37:09vitaly.krugcreate