[issue21517] installer Python default setting fails with mac Python Launcher
New submission from Andrew Harrington: I installed Python 3.4 on my Mac (OSX 10.9.2), with the option to make python 3.4 my default python3, so which python3 prints /Library/Frameworks/Python.framework/Versions/3.4/bin/python3 which is fine. A terminal then brings up python 3.4, fine. However the Python Launcher uses /usr/bin/python3 and the Python 3,4 install script does not change that. (I had it pointing to python 3.3 before, and it remained that way after installing Python 3.4.) Since the Python Launcher is a pretty standard way to start Python, this would be nice to fix, or at least in the installer have a comment that the something more needs to be set! -- assignee: ronaldoussoren components: Macintosh messages: 218697 nosy: Andrew.Harrington, ronaldoussoren priority: normal severity: normal status: open title: installer Python default setting fails with mac Python Launcher type: behavior versions: Python 3.4 ___ Python tracker <http://bugs.python.org/issue21517> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21517] installer Python default setting fails with mac Python Launcher
Andrew Harrington added the comment: I see not messing with /usr/bin. Your note about Python Launcher would be a nice addition to the Mac installer notes. I would encourage that before closing this. On Sat, May 17, 2014 at 1:57 AM, Ned Deily wrote: > > Ned Deily added the comment: > > Python.org installers do not install anything to /usr/bin; they do, by > default, install symbolic links in /usr/local/bin. Python 3 installers set > the symlink "/usr/local/bin/python3" to the most recently installed > version. The Python Launcher app has several open design issues, including > whether it should be included at all. Currently, each version of Python > (from python.org) installs its own copy of Python Launcher.app but they > all share the same preference file. You can set the path to your preferred > interpreter version by launching Python Launcher.app and then, in the > Preferences pane, selecting the file type (e.g. "Python Script") and typing > the interpreter path into the "Interpreter:" text box (e.g. > "/usr/local/bin/python3.4"), rather than using any of the preset defaults > in the pulldown list. > > -- > nosy: +ned.deily > resolution: -> works for me > stage: -> resolved > status: open -> closed > > ___ > Python tracker > <http://bugs.python.org/issue21517> > ___ > -- Dr. Andrew N. Harrington Computer Science Department Graduate Program Director g...@cs.luc.edu Loyola University Chicago 529 Lewis Tower, 111 E. Pearson St. (Downtown) 104 Loyola Hall, 1032 W. Sheridan Road (Rogers Park) http://www.cs.luc.edu/~anh Phone: 312-915-7982 Fax:312-915-7998 ahar...@luc.edu (as professor, not gpd role) -- ___ Python tracker <http://bugs.python.org/issue21517> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23544] Idle stacker viewer crash OSX
New submission from Andrew Harrington: 1. In idle 3.4.3, OSX 10.10, active state Tk 8.5.17, starting data: Python 3.4.3 (v3.4.3:9b73f1c3e601, Feb 23 2015, 02:52:03) [GCC 4.2.1 (Apple Inc. build 5666) (dot 3)] on darwin 2. start debugger, open very simple demo file, attached: 3. run, so debugger starts, step into main() 4. In debug menu, select Stack Viewer 5. hangs (apple swirling color wheel forever). Same error is repeatable. -- components: IDLE files: goodScope.py messages: 236842 nosy: Andrew.Harrington priority: normal severity: normal status: open title: Idle stacker viewer crash OSX type: crash versions: Python 3.4 Added file: http://bugs.python.org/file38269/goodScope.py ___ Python tracker <http://bugs.python.org/issue23544> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23544] IDLE hangs when selecting Stack View with debug active
Andrew Harrington added the comment: I was using this without looking at documentation, as a newbies would. Graying and disabling until after an exception makes sense, but even the menu item name is misleading: any time the program is running there is a stack that you might want to view. Better labels in the menu than "Stack Viewer" would be "stack trace" or "stack after exception" (maybe too long) or "stack after crash". On Fri, Feb 27, 2015 at 4:49 PM, Terry J. Reedy wrote: > > Terry J. Reedy added the comment: > > Verified on Windows whenever the debugger is active, meaning that a > program is running. (Debug On just means that it will become active when > code is run.) No stepping is needed; debugger can be pointing to the inital > docstring line. For me also, Idle stops and has to be externally closed, > as opposed to totally disappearing by itself. > > The doc for Stack Viewer says "Show the stack traceback of the last > exception". Example: > > >>> 1/0 > Traceback (most recent call last): > File "", line 1, in > 1/0 > ZeroDivisionError: division by zero > >>> > > Selecting Stack Viewer pops up a viewer box. This still works after > [DEBUG ON] > >>> > turns the debugger on but inactive. Entering anything at the prompt > disables viewing the 'last' exception, contrary to my understanding of the > short doc. So I might add '(if no other code has been run)' to the doc. > > Selecting Stack Viewer while a program is running (sleeping in this next > example) > > >>> import time; time.sleep(10); 1/0 > > brings up a box after the exception is printed. So 'last exception' can > actually be 'next exception'. But in this case, the user process is left > 'running' and no '>>> ' prompt appears, and one must Shell -> Restart to do > anything further. This is not good behavior. > > When one selects Debug -> Debugger while user code is running, Idle brings > up a message box "Don't debug now: You can only toggle the debugger when > idle". I think Debug -> Stack Viewer should be similarly disabled, though > perhaps graying out the menu entry might be better. It could also be grayed > out when there the 'last exception' cannot be viewed because other code has > been run. Stack Viewer should definitely be ignored when the debugger is > active, and I see no need to let people select it *before* an exception > occurs and the prompt is displayed. The next menu entry, Auto-open Stack > Viewer, takes care of opening upon future exceptions. > > -- > stage: -> needs patch > title: IDLE hangs with debug on and stack viewer -> IDLE hangs when > selecting Stack View with debug active > > ___ > Python tracker > <http://bugs.python.org/issue23544> > ___ > -- Dr. Andrew N. Harrington Computer Science Department Graduate Program Director g...@cs.luc.edu Loyola University Chicago 529 Lewis Tower, 111 E. Pearson St. (Downtown) 104 Loyola Hall, 1032 W. Sheridan Road (Rogers Park) http://www.cs.luc.edu/~anh Phone: 312-915-7982 Fax:312-915-7998 ahar...@luc.edu (as professor, not gpd role) -- ___ Python tracker <http://bugs.python.org/issue23544> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
