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.

Author michael.driscoll
Recipients brian.curtin, docs@python, eric.araujo, ezio.melotti, michael.driscoll, tim.golden, tshepang, weirdink13
Date 2012-05-25.20:28:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1337977716.18.0.621730148805.issue14901@psf.upfronthosting.co.za>
In-reply-to
Content
Okay. Here are a couple from http://docs.python.org/faq/windows.html#how-do-i-run-a-python-program-under-windows:

"You may also find that you have a Start-menu entry such as Start ‣ Programs ‣ Python 2.2 ‣ Python (command line)"

Then just a little farther down are several example paths with "c:\Python23\python"


Then in http://docs.python.org/faq/windows.html#how-can-i-embed-python-into-a-windows-application there's the following line:

"Do _not_ build Python into your .exe file directly. On Windows, Python must be a DLL to handle importing modules that are themselves DLL’s. (This is the first key undocumented fact.) Instead, link to pythonNN.dll; it is typically installed in C:\Windows\System. NN is the Python version, a number such as “23” for Python 2.3."


In http://docs.python.org/faq/windows.html#pyrun-simplefile-crashes-on-windows-but-not-on-unix-why there's this line:

"The Python 1.5.* DLLs (python15.dll) are all compiled with MS VC++ 5.0 and with multithreading-DLL options (/MD)."


I see fixed http://docs.python.org/faq/windows.html#how-do-i-emulate-os-kill-in-windows as it mentions BOTH Python 2.7 and 3.2
History
Date User Action Args
2012-05-25 20:28:36michael.driscollsetrecipients: + michael.driscoll, tim.golden, ezio.melotti, eric.araujo, brian.curtin, docs@python, tshepang, weirdink13
2012-05-25 20:28:36michael.driscollsetmessageid: <1337977716.18.0.621730148805.issue14901@psf.upfronthosting.co.za>
2012-05-25 20:28:35michael.driscolllinkissue14901 messages
2012-05-25 20:28:35michael.driscollcreate