➜

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 pitrou
Recipients Matthew Stoltenberg, gregory.p.smith, pitrou
Date 2017-12-06.23:54:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <cb40c32d-cf6a-a0cf-6b4e-9e08dbd6fac7@free.fr>
In-reply-to <1512603703.9.0.213398074469.issue32224@psf.upfronthosting.co.za>
Content 
I think we still want the full tuple passed to connect().  We may want
to truncate the tuple when used for other purposes.

Le 07/12/2017 à 00:41, Matthew Stoltenberg a écrit :
> 
> Matthew Stoltenberg <d3matt@gmail.com> added the comment:
> 
> The naive change is to have the host, port tuple assignment use only the first two values from address. I can open a PR with that change (and update the docstring for the function) if that's the right change. For reference, the python socketpair implementation (if _socket is missing it) ignores flow_info and scope_id, but I'm not sure that's the right thing to do.
> 
> ----------
> 
> _______________________________________
> Python tracker <report@bugs.python.org>
> <https://bugs.python.org/issue32224>
> _______________________________________
>
History
Date User Action Args
2017-12-06 23:54:27pitrousetrecipients: + pitrou, gregory.p.smith, Matthew Stoltenberg
2017-12-06 23:54:27pitroulinkissue32224 messages
2017-12-06 23:54:26pitroucreate