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 gvanrossum, loewis, ncoghlan, neologix, pitrou, serhiy.storchaka, vstinner
Date 2014-08-04.13:14:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1407158073.42.0.398740960704.issue22127@psf.upfronthosting.co.za>
In-reply-to
Content
> Perhaps it is time to add support of ipaddress objects in socket functions.

What I was thinking too :-)
However, beware the parsing cost of ipaddress objects themselves.

One common pattern when doing UDP networking is the following:

  def datagram_received(self, remote_addr, data):
      # process data
      ...
      self.send_to(remote_addr, response_data)

If you want to pass an ipaddress object to send_to, you have to make it so that datagram_received() gives you an ipaddress object too.

Perhaps we need a more low-level solution, e.g. a parsing cache integrated in the C socket module.
History
Date User Action Args
2014-08-04 13:14:33pitrousetrecipients: + pitrou, gvanrossum, loewis, ncoghlan, vstinner, neologix, serhiy.storchaka
2014-08-04 13:14:33pitrousetmessageid: <1407158073.42.0.398740960704.issue22127@psf.upfronthosting.co.za>
2014-08-04 13:14:33pitroulinkissue22127 messages
2014-08-04 13:14:33pitroucreate