summaryrefslogtreecommitdiff
path: root/PCbuild/python.vcxproj
diff options
context:
space:
mode:
authorBrian Curtin <brian@python.org>2012-12-23 16:53:21 -0600
committerBrian Curtin <brian@python.org>2012-12-23 16:53:21 -0600
commit445ad997ab7fd5ad8dd77250bb17c82ad40c1f1f (patch)
tree7bc829a888aa76693fe0c3431d8984fb1c2bae5d /PCbuild/python.vcxproj
parent77377574dcecac2d5936f2418e36cd9de4d90247 (diff)
downloadcpython-git-445ad997ab7fd5ad8dd77250bb17c82ad40c1f1f.tar.gz
Fix #14470. Remove w9xpopen per PEP 11.
As stated in PEP 11, 3.4 removes code on Windows platforms where COMSPEC points to command.com. The w9xpopen project in Visual Studio was added to support that case, and there was a special case in subprocess to cover that situation. This change removes the w9xpopen project from the Visual Studio solution and removes any references to the w9xpopen executable.
Diffstat (limited to 'PCbuild/python.vcxproj')
-rw-r--r--PCbuild/python.vcxproj6
1 files changed, 1 insertions, 5 deletions
diff --git a/PCbuild/python.vcxproj b/PCbuild/python.vcxproj
index d0a9de0b06..e1d05e5e50 100644
--- a/PCbuild/python.vcxproj
+++ b/PCbuild/python.vcxproj
@@ -357,12 +357,8 @@
<Project>{cf7ac3d1-e2df-41d2-bea6-1e2556cdea26}</Project>
<ReferenceOutputAssembly>false</ReferenceOutputAssembly>
</ProjectReference>
- <ProjectReference Include="w9xpopen.vcxproj">
- <Project>{e9e0a1f6-0009-4e8c-b8f8-1b8f5d49a058}</Project>
- <ReferenceOutputAssembly>false</ReferenceOutputAssembly>
- </ProjectReference>
</ItemGroup>
<Import Project="$(VCTargetsPath)\Microsoft.Cpp.targets" />
<ImportGroup Label="ExtensionTargets">
</ImportGroup>
-</Project> \ No newline at end of file
+</Project>