Message159578
The original change was introduced in this issue401197 which seems to use fqdn at *all appropriate places*. In this case, after about a decade, it was realized that using fdqn for client connection may not be appropriate when hostname is not set.
In 3.3, this is fixed by making address_string return client ip instead of client hostname.
In 2.7 and 3.2, I would like to see it fixed wherein, inside the log_message call, the address_string is not called instead direct client address is used. In this manner, we are not changing any return values of public api (address_string), but we are effectively eliminating the delay cased by fqdn looking while logging to sys.stderr. |
|
Date |
User |
Action |
Args |
2012-04-29 05:26:27 | orsenthil | set | recipients:
+ orsenthil, pitrou, schmir, eric.araujo, aerodonkey, ubershmekel, neologix, santoso.wijaya, python-dev, knicker.kicker, wmgaca |
2012-04-29 05:26:27 | orsenthil | set | messageid: <1335677187.79.0.538737502082.issue6085@psf.upfronthosting.co.za> |
2012-04-29 05:26:27 | orsenthil | link | issue6085 messages |
2012-04-29 05:26:26 | orsenthil | create | |
|