We should keep the discussion on the mailing list. (Use Reply All when you reply.)
On Sep 6, 2017, at 06:35, David Epstein wrote: > On 06/09/2017 08:58, Ryan Schmidt wrote: >> On Sep 5, 2017, at 18:29, David Epstein wrote: >> >> >>> What is the procedure for adding to bug report #54728. >>> >> Log in to our Trac with your GitHub account. This will reveal the new >> comment field at the bottom of the ticket which you can type into and then >> submit. >> > I have a GitHub account, but I don't think I have ever used it. When I logged > in to https://github.com I got > Learn Git and GitHub without any code! > > Using the Hello World guide, you’ll create a repository, start a branch, > write comments, and open a pull request. > > I could click on "Read the Guide" or "Start a Project". But the second wasn't > relevant and the first sounded as though it would take more time than I have. > Also I wasn't sure whether reading the guide would enable me to comment on > the relevant ticket. > ====================================================== > All I now want to add to Ticket #54728 is this: > > Action: installed python36 with no variant. Result: readline misbehaves in > python interpreter. > Next Action: installed python36+readline. Result: port notes python36 says > "install py36-readline" > Next Action: installed py36-readline. Result: python interpreter > crashes on receiving Carriage Return > Next Action: deactivated py36-readline. Result: readline in python > interpreter appears to work perfectly > Next Action: activated py36-readline. Result: python interpreter > crashes on receiving Carriage Return > Next Action: deactivated py36-readline. Result: readline appears to work > perfectly > > Action necessary from maintainer: please edit the note from "port install > python36" to improve the advice. > ======================================================= > Please give me more details about getting access to github's macports/trac, > or else please include the above lines of comment. All you need to do is click the "GitHub Login" link at the top of any MacPorts Trac page, or visit: https://trac.macports.org/login Then you can add comments to tickets or file new tickets. > It's not clear that my experience has much to do with this ticket, but there > could be a common origin. Possibly a new ticket should be opened, but I don't > want to do that, as I understand too little of what is going on. I think we already know that using py36-readline causes a crash, and that upstream may have already fixed the problem and just needs to release a new version. https://trac.macports.org/ticket/53360 Incidentally, it seems that py36-gnureadline replaces py36-readline, and the question of removing the entire py-readline port seems to have stalled: https://trac.macports.org/ticket/44206 But the current version of py36-gnureadline has the same problem. https://trac.macports.org/ticket/53176 I don't think we need any additional tickets describing the same problem.
