[issue16668] Remove python3dll.vcxproj from pcbuild.sln

2012-12-12 Thread Trent Nelson
Trent Nelson added the comment: Thanks Martin, I wasn't aware of that PEP. Explains why there isn't a debug configuration, too. -- ___ Python tracker ___ __

[issue16668] Remove python3dll.vcxproj from pcbuild.sln

2012-12-12 Thread Martin v . Löwis
Martin v. Löwis added the comment: Yes, it's still used. python3.dll is different from python3X.dll, and specified in PEP 384. It will remain in Python until Python 4 comes along (and then likely be replaced by python4.dll). -- resolution: -> invalid status: open -> closed __

[issue16668] Remove python3dll.vcxproj from pcbuild.sln

2012-12-12 Thread Jeremy Kloth
Changes by Jeremy Kloth : -- nosy: +jkloth ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue16668] Remove python3dll.vcxproj from pcbuild.sln

2012-12-12 Thread Trent Nelson
Changes by Trent Nelson : -- nosy: +brian.curtin ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.py

[issue16668] Remove python3dll.vcxproj from pcbuild.sln

2012-12-12 Thread Trent Nelson
New submission from Trent Nelson: As far as I can tell, the python3dll.vcxproj is bitrot and should be removed from pcbuild.sln. It's a makefile target project that invokes ..\PC\python3.mak, which builds a target named python3.dll; however, pythoncore.vxcproj builds python34[_d].dll as a pro