Zachary Ware added the comment:
Sure; currently, the "ssl" project emits messages from build_ssl.py concerning
the finding of Perl. On a machine with a usable Perl, it's just
" Found a working perl at 'C:\Perl\bin\perl.exe'"
On machines without Perl, its the more worrisome
"""
Can not find a suitable PERL:
NO perl interpreters were found on this machine at all!
Please install ActivePerl and ensure it appears on your path
No Perl installation was found. Existing Makefiles are used.
"""
The last line of that message (and the fact that the ssl-related projects build
ok anyway, if using source from svn.python.org) ought to make it clear that
Perl really isn't necessary, but removing the messages entirely removes the
possibility of misunderstanding. The messages are still useful if you actually
need the preparation part of build_ssl.py, though, so I don't want to just
remove them from the script. Divorcing the building from the preparation has
other benefits as well, which IMO would stand on their own, but that wasn't my
main goal here.
As for the brief discussion of Perl that remains in readme.txt, I think it
should stay as long as we include a mention of how to use non-svn.python.org
sources, just so that anyone needing to do a non-standard build will have some
warning. On the other hand, readme.txt could just give the script invocation,
and leave it up to the script to recommend Perl if it's not available.
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue21141>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
