![]() It turns out that, with osascript, if you catch the error and try again, it works. There is a potential workaround that could be used so that way macOS 10.12.5 works. So I'm going to mark this issue as "pending fixed" until the official release of 10.12.6. Good news! Apple appears to have fixed the osascript regression in the most recent macOS 10.12.6 public beta (version 2). ![]() However, the opacity of the system is such that there is no way to get any further information (even though we know the bug number).įWIW: The bug in osascript is still present in the current 10.12.6 beta (build 16G8c) So Apple is aware of the bug, and possibly not completely ignoring it. I'll also note that my bug report (radar) has been marked as "DUPLICATE OF 31898264 (OPEN)". (For what it's worth, among other things the current implementation relies on the officially deprecated os.popen() which has nothing to do with this problem but I guess this could be taken as an opportunity to change.) I have already filed a radar, and I hope this will get fixed at Apple, but it's a bug we need to live with for a while one way or the other. This indeed appears to be a bug in osascript, the scriptlet still works when using the AppleScript Editor application, which means the AppleScript environment itself and browser scripting support still work. The alternative to filing a RADAR is to just use the open command instead of osascript (basically what's suggested in msg293950 but directly using subprocess.check_call() instead of involving osascript).įor 3.7 it might be useful to drop usage of osascript altogether although that would result in some loss of functionality (/usr/bin/open cannot control if the URL should open in a new window or not). We should check whether the osascript regression is fixed in the most recent 10.12.6 Developer Preview and, if not, open a RADAR (Apple bug report).Īuthor: Ronald Oussoren (ronaldoussoren) * I don't think it's backward incompatible change, especially between 10.12.4 and 10.12.5 which would completely broke default behavior. ![]() This seems to be a bug in the `osascript` application in the latest macOS 10.12.5: Script = 'do shell script "open %s"' % url.replace('"', '%22') Perhaps this implies a macOS bug or deliberate behaviour change? (I couldn't find anything obviously appropriate in the list of security fixes for 10.12.5.)Ĭhanging lines 594 and 623 in webbrowser.py (python 2.7.13) to avoid the broken 'open location' seems to solve the problem in idle. The same behaviour also happens under Apple's system Python 2.7.10. Behaviour first noticed under Jupyter notebook - see This behaviour is identical under 3.6.1 and 2.7.13 (untested elsewhere) I believe this worked correctly under previous macOS versions (but I don't currently have access to any such machines). Specifically:Ġ:33: execution error: " " doesn’t understand the “open location” message. On the newly-released macOS Sierra 10.12.5, the default web browser which is meant to returned by webbrowser.get() gives an error. Default webbrowser fails on macOS Sierra 10.12.5Īndrew.Jaffe, Kevin Ballard, Rudi Grams, alangpierce, dasm, ehuss, glyph, ned.deily, ronaldoussoren, tgechoĬreated on 19:44 by Andrew.Jaffe, last changed 14:58 by admin.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |