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 Gabi.Davar, Waffle.Souffle, brian.curtin, loewis, ocean-city, sable, srid, tim.golden, tim.peters, zach.ware
Date 2014-05-06.20:29:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1399408195.91.0.612109341827.issue10752@psf.upfronthosting.co.za>
In-reply-to
Content
Still relevant, insofar as having Perl available is relevant.  That is, you only need Perl available if you're using vanilla OpenSSL sources, not if you're using sources pulled from svn.python.org (which most people should do, I would think).  I have never had a problem with build_ssl.py finding Perl, though.

That said, I don't see any harm in properly updating from os.popen to subprocess.

See also issue21141, which aims to make explicit that Perl is only needed to doctor up vanilla OpenSSL source.
History
Date User Action Args
2014-05-06 20:29:55zach.waresetrecipients: + zach.ware, tim.peters, loewis, ocean-city, sable, tim.golden, brian.curtin, srid, Gabi.Davar, Waffle.Souffle
2014-05-06 20:29:55zach.waresetmessageid: <1399408195.91.0.612109341827.issue10752@psf.upfronthosting.co.za>
2014-05-06 20:29:55zach.warelinkissue10752 messages
2014-05-06 20:29:55zach.warecreate