Author Zero
Recipients Zero, paul.moore, steve.dower, terry.reedy, tim.golden, zach.ware
Date 2017-09-14.19:50:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1505418617.55.0.339159278979.issue31476@psf.upfronthosting.co.za>
In-reply-to
Content
Ever since Python 3.6.1, trying to open a Python-source library module in IDLE on Windows (10) has not worked properly since the installer has only been providing *.pyc files. Learning how to use Python has always been easy since it (1) has a great help document, (2) makes it easy to get help() on objects, and (3) allows the source to easily be explored and/or patched. Is there something special that needs to be done to get both the standard library's *.py files and precompile them to *.pyc during installation?

I would be glad to run further tests if the Windows installer can be run headless with specific command-line arguments.
History
Date User Action Args
2017-09-14 19:50:17Zerosetrecipients: + Zero, terry.reedy, paul.moore, tim.golden, zach.ware, steve.dower
2017-09-14 19:50:17Zerosetmessageid: <1505418617.55.0.339159278979.issue31476@psf.upfronthosting.co.za>
2017-09-14 19:50:17Zerolinkissue31476 messages
2017-09-14 19:50:17Zerocreate