Message260877
I don't know why it used to accept a string port, but I can't find anything in the docs indicating that is acceptable. I am guessing the doc authors assumed it was so obvious that a port is an integer they forgot to mention it.
I can guess that in the past some system API was used that considered the port a "servname" to be looked up in /etc/services (likely the getaddrinfo() call).
But if you were passing '12345' instead of 12345, well, you always had a latent bug in your program.
I don't think the code ought to be adjusted to explicitly reject string ports; but I do think the docs should be clarified on the issue. |
|
Date |
User |
Action |
Args |
2016-02-25 18:42:38 | gvanrossum | set | recipients:
+ gvanrossum, pitrou, vstinner, giampaolo.rodola, docs@python, xdegaye, yselivanov |
2016-02-25 18:42:38 | gvanrossum | set | messageid: <1456425758.93.0.776001411868.issue26437@psf.upfronthosting.co.za> |
2016-02-25 18:42:38 | gvanrossum | link | issue26437 messages |
2016-02-25 18:42:38 | gvanrossum | create | |
|