➜
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.
Created on 2012-12-12 11:43 by trent, last changed 2022-04-11 14:57 by admin. This issue is now closed.
| Messages (3) | |||
|---|---|---|---|
| msg177372 - (view) | Author: Trent Nelson (trent) *  |
Date: 2012-12-12 11:43 | |
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 proper VS project. (Additionally, the python3dll.vxcproj has no Debug configuration, which is what brought it to my attention in the first place.) Christian/Martin: is this python3dll.vcxproj and resulting python3.dll still used or can it be safely removed from pcbuild.sln? |
|||
| msg177380 - (view) | Author: Martin v. Löwis (loewis) * |
Date: 2012-12-12 16:39 | |
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). |
|||
| msg177383 - (view) | Author: Trent Nelson (trent) * |
Date: 2012-12-12 18:02 | |
Thanks Martin, I wasn't aware of that PEP. Explains why there isn't a debug configuration, too. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:57:39 | admin | set | github: 60872 |
| 2012-12-12 18:02:54 | trent | set | messages: + msg177383 |
| 2012-12-12 16:39:59 | loewis | set | status: open -> closed resolution: not a bug messages: + msg177380 |
| 2012-12-12 16:38:24 | jkloth | set | nosy:
+ jkloth |
| 2012-12-12 14:14:51 | trent | set | nosy:
+ brian.curtin |
| 2012-12-12 11:43:10 | trent | create | |