Derrick Hudson wrote:
On Sun, May 08, 2005 at 02:28:55PM +0200, yuppie wrote: | Hi! | | On Windows, this 15 months old change in ZConfig sets the default | hostname for inet_address to 'localhost': | | http://svn.zope.org/ZConfig/?rev=376&view=rev | | I have no idea why this was changed, the checkin message is not very | helpful: "fix the default hostname for address datatypes for Windows"
| Any comments?
Search the list archives for a discussion of why that was changed. IIRC it is due to quirks in Windows' network libraries -- a test was failing because the system API to query the identity of the socket did something funny with 'localhost' vs. '127.0.0.1' and that caused the comparison in the test to fail even though there was no actual defect.
OTOH, after a quick look at the referenced defects and archived emails I may be remembering something else.
Anyways, hopefully my memory will help you. If not, well that's all I can offer.
I couldn't find anything in the archives, but Tim's Entry #5 in http://www.zope.org/Collectors/Zope/1728 might explain the change in ZConfig. It seems to work around an issue with connect() on Windows. But I still believe it was wrong to change the 'inet_address' datatype in ZConfig. Cheers, Yuppie
On 5/9/05, yuppie <y.2005-@wcm-solutions.de> wrote:
But I still believe it was wrong to change the 'inet_address' datatype in ZConfig.
I spoke with Tim about this briefly today, and I can't remember the reasons for some of the relevant changes. I suspect at this point that putting less magic in the ZConfig type is probably the right thing; much of the remaining magic should be able to disappear at that point. -Fred -- Fred L. Drake, Jr. <fdrake at gmail.com> Zope Corporation
participants (2)
-
Fred Drake -
yuppie