Message 125634 - Python tracker

➜

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	rosslagerwall
Recipients	belopolsky, georg.brandl, giampaolo.rodola, gregory.p.smith, loewis, pitrou, rosslagerwall
Date	2011-01-07.09:19:14
SpamBayes Score	2.0033495e-07
Marked as misclassified	No
Message-id	<1294391959.02.0.642168643566.issue10812@psf.upfronthosting.co.za>
In-reply-to

Content
> it's a bit asymmetric that gethostname is in the socket > module and supports Windows, and sethostname is in the POSIX > module. It would be useful to have a gethostname in the POSIX > module also which is a) POSIX only and b) supports embedded > NUL bytes. According to the spec for gethostname(), the hostname that it returns is null-terminated so it won't support embedded NUL bytes. Should we still add it anyway?

>  it's a bit asymmetric that gethostname is in the socket
>  module and supports Windows, and sethostname is in the POSIX
>  module. It would be useful to have a gethostname in the POSIX
>  module also which is a) POSIX only and b) supports embedded
>  NUL bytes.

According to the spec for gethostname(), the hostname that it returns is null-terminated so it won't support embedded NUL bytes. Should we still add it anyway?

History
Date	User	Action	Args
2011-01-07 09:19:19	rosslagerwall	set	recipients: + rosslagerwall, loewis, georg.brandl, gregory.p.smith, belopolsky, pitrou, giampaolo.rodola
2011-01-07 09:19:19	rosslagerwall	set	messageid: <1294391959.02.0.642168643566.issue10812@psf.upfronthosting.co.za>
2011-01-07 09:19:14	rosslagerwall	link	issue10812 messages
2011-01-07 09:19:14	rosslagerwall	create