[issue21273] don't defined socket constants which are not implemented for GNU/Hurd

2014-04-28 Thread Antoine Pitrou
Antoine Pitrou added the comment: Ok, rejecting. -- resolution: - rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21273 ___

[issue21273] don't defined socket constants which are not implemented for GNU/Hurd

2014-04-17 Thread Benjamin Peterson
Benjamin Peterson added the comment: I'm not sure this is a good idea. In general, we expose whatever libc defines, and let it give ENOSYS (or similar) errors if the underlying system doesn't actually support the behavior. Presumably, the Hurd might implement SO_REUSEPORT at some point.

[issue21273] don't defined socket constants which are not implemented for GNU/Hurd

2014-04-17 Thread Antoine Pitrou
Antoine Pitrou added the comment: Indeed, this complicates the conditional defines for no obvious benefit. -- nosy: +pitrou ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21273 ___

[issue21273] don't defined socket constants which are not implemented for GNU/Hurd

2014-04-16 Thread Matthias Klose
New submission from Matthias Klose: Comment out constant exposed on the API which are not implemented on GNU/Hurd. They would not work at runtime anyway. -- components: Extension Modules files: hurd-disable-nonworking-constants.diff keywords: patch messages: 216610 nosy: doko priority: