On Sep 6, 2017, at 02:41, David Epstein wrote:
> I don't suppose that the output from a port install command is saved
> automatically somewhere? It seems like it would often be useful to have this
> output saved.
Nope, not saved anywhere.
> Last night I posted (with the same subject line as this email) a problem
> about python3.6 and readline.
> This morning I seem to have fixed the problem by deactivating py36-readline
> (but I have only done cursory tests).
> I have just activated py36-readme, and python3.6 again crashes immediately.
> Subsequent deactivation restores sanity.
> Conclusion: Although I cannot be sure that my current version python36
> @3.6.2_0+readline (active) solves all my readline problems, I can be sure
> that it was BAD to install py36-readline on top of this.
>
> I would like to check that the installation of python36+readline really did
> advise me to install py36-readline, or did I just misread or imagine the
> advice?
>
> Can I check what port install told me, without having explicitly asked the
> unix shell to save the output?
You can re-display any port's notes, e.g.:
$ port notes python36
python36 has the following notes:
To make this the default Python or Python 3 (i.e., the version run
by the 'python' or 'python3' commands), run one or both of:
sudo port select --set python python36
sudo port select --set python3 python36
##############################################################
# IF YOU ARE USING PYTHON FROM THE TERMINAL, PLEASE INSTALL:
# py36-readline
# TO AVOID A LIBEDIT / PYTHON INTERACTION ISSUE.
# REF: https://trac.macports.org/ticket/48807
##############################################################
