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 zach.ware
Recipients jpe, terry.reedy, zach.ware
Date 2013-04-22.16:44:58
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I agree it would be nice, but I'm not sure how easy or practical it would be to implement, particularly making sure that NASM is on the PATH.  And besides, at some point, we have to draw the line between what we can reasonably do for a user and what we can reasonably expect a user to do for themselves.  That line falls at minimum after installation of Visual C++ 2010, which would be nearly impossible to properly install from a batch script, and is currently also after installation of NASM and Perl, which are both optional anyway--you can build Python without NASM, you'll just have build errors and won't have SSL support.  I think that's a reasonable place to keep the line: short of trying to install external programs for the user.

I think it would be good to have a nice error/warning message in build.bat if NASM (or MSVC++, for that matter) can't be found, possibly with a URL pointing to where to look for an installer.  Something along the lines of:

where nasm >nul 2>&1

if %ERRORLEVEL% == 1 (
    echo NASM not found on PATH.  It can be downloaded from
    set /P _continue=Continue without NASM? (y/n)
    if %_continue% == n exit /B 1 else echo Continuing...

Does that come anywhere close to scratching your itch?
Date User Action Args
2013-04-22 16:44:58zach.waresetrecipients: + zach.ware, jpe, terry.reedy
2013-04-22 16:44:58zach.waresetmessageid: <>
2013-04-22 16:44:58zach.warelinkissue17717 messages
2013-04-22 16:44:58zach.warecreate