[issue6926] socket module missing IPPROTO_IPV6, IPPROTO_IPV4

Maximilian Hils added the comment: Thanks for the insanely quick feedback. I still think this is a bug, so I filed https://bugs.python.org/issue29515 with additional details. Let's continue there. -- ___ Python tracker

[issue6926] socket module missing IPPROTO_IPV6, IPPROTO_IPV4

Christian Heimes added the comment: The constants are defined on Linux. That means Windows does not define the constants and therefore the socket module can't export them. This ticket is closed. If you still think it's a bug, please open a new ticket and reference this ticket. --

[issue6926] socket module missing IPPROTO_IPV6, IPPROTO_IPV4

Maximilian Hils added the comment: This still seems to be an issue with the offical Python 3.6 builds on Windows 10: Python 3.6.0 (v3.6.0:41df79263a11, Dec 23 2016, 07:18:10) [MSC v.1900 32 bit (Intel)] on win32 >>> import socket >>> socket.IPPROTO_IPV6 Traceback (most recent call last):

[issue6926] socket module missing IPPROTO_IPV6, IPPROTO_IPV4

Berker Peksag added the comment: Py_WINVER has been updated to use 0x0600 (_WIN32_WINNT_VISTA) in 57e2549cc9a6 (issue 23451) Since the consensus was to keep 2.7 as is I'm closing this as 'out of date'. -- nosy: +berker.peksag resolution: -> out of date stage: needs patch -> resolved

[issue6926] socket module missing IPPROTO_IPV6, IPPROTO_IPV4

STINNER Victor added the comment: I don't think that Windows XP is officially no more supported in Python. I would prefer an explicit mention in the PEP 11. So please don't use this argument to close an issue. -- nosy: +haypo ___ Python tracker

[issue6926] socket module missing IPPROTO_IPV6, IPPROTO_IPV4

Mark Lawrence added the comment: It looks as if we're talking at cross purposes. PEP11 will not be updated any more for Windows releases, we will be following the Microsoft support life cycle. That is clearly of interest to anybody wishing to make code changes against this issue. I do not

[issue6926] socket module missing IPPROTO_IPV6, IPPROTO_IPV4

Mark Lawrence added the comment: As XP is now out of support here are links http://legacy.python.org/dev/peps/pep-0011/#microsoft-windows http://support.microsoft.com/lifecycle/ that I hope come in useful. -- nosy: +BreamoreBoy versions: +Python 3.5 -Python 3.3

[issue6926] socket module missing IPPROTO_IPV6, IPPROTO_IPV4

Changes by Christian Heimes li...@cheimes.de: -- versions: +Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6926 ___ ___ Python-bugs-list

[issue6926] socket module missing IPPROTO_IPV6, IPPROTO_IPV4

Changes by Brian Curtin cur...@acm.org: -- nosy: +brian.curtin ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6926 ___ ___ Python-bugs-list mailing

[issue6926] socket module missing IPPROTO_IPV6, IPPROTO_IPV4

Éric Araujo mer...@netwok.org added the comment: Should this be fixed before the final release? -- components: +Library (Lib) -IO nosy: +eric.araujo, georg.brandl ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6926

[issue6926] socket module missing IPPROTO_IPV6, IPPROTO_IPV4

Gregory P. Smith g...@krypto.org added the comment: IMNSHO it should but that would violate our release practices to do it this late in the cycle. I expect the release manager to decline. It isn't a critical issue, the end result is that people will hard code the constants into their own

[issue6926] socket module missing IPPROTO_IPV6, IPPROTO_IPV4

Changes by Antoine Pitrou pit...@free.fr: -- stage: - needs patch versions: +Python 3.3 -Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6926 ___

[issue6926] socket module missing IPPROTO_IPV6, IPPROTO_IPV4

Raymond Hettinger rhettin...@users.sourceforge.net added the comment: I would consider it to be regression and bugfix that is not inappropriate to repair at this point. -- nosy: +rhettinger ___ Python tracker rep...@bugs.python.org

[issue6926] socket module missing IPPROTO_IPV6, IPPROTO_IPV4

Martin v. Löwis mar...@v.loewis.de added the comment: I would consider it to be regression and bugfix that is not inappropriate to repair at this point. I'd also be in favor of fixing it. To reduce the risk of breaking something, I'd only raise socketmodule to a more recent Windows API. Of

[issue6926] socket module missing IPPROTO_IPV6, IPPROTO_IPV4

Changes by Giampaolo Rodola' g.rod...@gmail.com: -- nosy: +giampaolo.rodola ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6926 ___ ___

[issue6926] socket module missing IPPROTO_IPV6, IPPROTO_IPV4

Martin v. Löwis mar...@v.loewis.de added the comment: Following the python-dev consensus, I have now added a warning to the 2.7 installer that this will be the last release supporting Windows 2000. I still think that we should not bump the SDK version above 500 for 2.7. Changing the SDK level

[issue6926] socket module missing IPPROTO_IPV6, IPPROTO_IPV4

Gregory P. Smith g...@krypto.org added the comment: In PC/pyconfig.h we #define Py_WINVER to _WIN32_WINNT_WIN2K (0x500) for 32bit builds. I think we should update this to _WIN32_WINNT_WINXP (0x501) for all builds, not just 64bit. Assigning to loewis as he does our windows release builds

[issue6926] socket module missing IPPROTO_IPV6, IPPROTO_IPV4

Martin v. Löwis mar...@v.loewis.de added the comment: Bumping the API level to XP might mean that we stop supporting Windows 2000; I'm not sure whether we agreed to that yet. I'd be curious to find out why the constants were defined in Python 2.5. --

[issue6926] socket module missing IPPROTO_IPV6, IPPROTO_IPV4

Gregory P. Smith g...@krypto.org added the comment: extended support for windows 2000 server ends in a few months, mainstream support ended 5 years ago: http://support.microsoft.com/lifecycle/?LN=en-usx=8y=9p1=7274 That, IMNSHO, implies that python 2.7 and 3.2 should not bother supporting

[issue6926] socket module missing IPPROTO_IPV6, IPPROTO_IPV4

New submission from Jason R. Coombs jar...@jaraco.com: It appears that somewhere between Python 2.5 and Python 2.6, some socket constants were lost in Windows builds. Python 2.6.2 (r262:71605, Apr 14 2009, 22:46:50) [MSC v.1500 64 bit (AMD64)] on win32 Type help, copyright, credits or license

[issue6926] socket module missing IPPROTO_IPV6, IPPROTO_IPV4

Jason R. Coombs jar...@jaraco.com added the comment: This comment from the MSDN docs may be relevant: On the Microsoft Windows Software Development Kit (SDK) released for Windows Vista and later, the organization of header files has changed and IPPROTO_IPV6 level is defined in the Ws2def.h

[issue6926] socket module missing IPPROTO_IPV6, IPPROTO_IPV4

Jason R. Coombs jar...@jaraco.com added the comment: I think I found the problem. It appears Python is compiled with #define _WIN32_WINNT 0x0500 But IPPROTO_IPV6 (and other constants) are only defined #if(_WIN32_WINNT = 0x0501) What's the proper fix for this issue? --

[issue6926] socket module missing IPPROTO_IPV6, IPPROTO_IPV4

Jason R. Coombs jar...@jaraco.com added the comment: I think a suitable test case for this issue is: if hasattr(sys, 'getwindowsversion'): if sys.getwindowsversion() = (5,1): assert hasattr(socket, 'IPPROTO_IPV6') -- ___ Python tracker