Mailman 3 December 2016 - Pythonmac-SIG

py2app release delayed
by Ronald Oussoren Jan. 11, 2017

Jan. 11, 2017

Hi, I had hoped to release a new version of py2app today, but didn’t due to problems with macholib that resulted in broken application bundles. The good news is that I found the cause of that breakage and reverted the patch that caused it. I did fix a number of bugs on the tracker last week (the number of open issues decreased from 94 to 72), and implemented a useful new feature: support for “@loader_path” in shared libraries, which is used in wheels processed with delocate <https://github.com/matthew-brett/delocate/blob/master/delocate/delocating.py <https://github.com/matthew-brett/delocate/blob/master/delocate/delocating.py>> such as the wheels for Pillow. Because this is turning into a fairly large release I’d appreciate if people could test the code in the repository with their applications. To install first install altgraph-0.13, then install modulegraph, macholib and py2app from their bitbucket repositories (https://bitbucket.org/ronaldoussoren/modulegraph <https://bitbucket.org/ronaldoussoren/modulegraph>, https://bitbucket.org/ronaldoussoren/macholib <https://bitbucket.org/ronaldoussoren/macholib> and https://bitbucket.org/ronaldoussoren/py2app <https://bitbucket.org/ronaldoussoren/py2app>). There’s still a fairly large number of open issues for py2app, but those will have to wait for a later time (which hopefully be a lot sooner than the time it took me to get from the previous release to this point). Ronald

4 10

Re: [Pythonmac-SIG] PyObjC and macOS 10.12 (Sierra)
by Andrew Jaffe Dec. 16, 2016

Dec. 16, 2016

Dear Chris and Glyph, > > On Sunday, September 11, 2016, Andrew Jaffe <a.h.jaffe(a)gmail.com> wrote: > Dear Ronald, > > Thanks, as usual, for all this. > > I have upgraded to the GM version of 10.12 on the beta track. I use the python.org framework builds of python. > > When I do "pip list --outdated", I get a long list: …. > If I do the usual "pip --upgrade" for these, it fails, seemingly because of permissions (Apologies, but I don't have access to the messages anymore): it is clearly trying to delete these versions which seem to live in /System/Library/Frameworks/Python.framework/Versions/2.7/. This fails, of course, due to permissions (and system integrity protection). > > You can, in fact, do the upgrade with the "--ignore-installed" flag in pip (although there's still a problem with pyobjc-framework-Message). > > So: are these errors expected? Is it something in my particular setup? Or the beta program? Is "--ignore-installed" the correct solution? > > Thanks, > > Andrew > >> On 13 Sep 2016, at 16:13, Christopher Barker <pythonchb(a)gmail.com> wrote: >> >> If you are dealing with stuff in /System, then you are dealing with the Ape installed Python, not the Python.org build. >> >> It's easy for "pip" and python to get out of sync. >> >> Try "which pip" to see which pip you are running. >> >> This is why I recommend encoding pip via: >> >> python -m pip [args] [I tried to comment via the gmane newsgroup version of the lists and my messages never appeared so I hope this works…] Just to be clear, I am indeed using the framework pip, which is part of why this is so confusing. In the past, as far as I know, it’s never tried to have anything to do with /System. Again, I don’t know if it’s something about macOS 10.12 Sierra, or my particular setup that is the problem. Also, to be clear, there are no PYTHON* or other environment variables that would affect the python path. Here is a failing session… (Aside: I understand that "pyobjc-framework-Message” is actually a bad example: it is the only package that even —-ignore-installed actually fails on, because it has the "--single-version-externally-managed” problem which is a different kettle of fish. But I think the above error message is the same as the one that I would get for any of the other packages in question. Note that pip2 install works fine for packages other than those in my original list.) $ command which pip2 /Library/Frameworks/Python.framework/Versions/2.7/bin/pip2 $ pip2 install --upgrade pyobjc-framework-Message Collecting pyobjc-framework-Message Using cached pyobjc-framework-Message-3.1.1.tar.gz Requirement already up-to-date: pyobjc-core>=3.1.1 in /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages (from pyobjc-framework-Message) Requirement already up-to-date: pyobjc-framework-Cocoa>=3.1.1 in /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages (from pyobjc-framework-Message) Installing collected packages: pyobjc-framework-Message Found existing installation: pyobjc-framework-Message 2.5.1 Uninstalling pyobjc-framework-Message-2.5.1: Exception: Traceback (most recent call last): File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/pip/basecommand.py", line 215, in main status = self.run(options, args) File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/pip/commands/install.py", line 317, in run prefix=options.prefix_path, File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/pip/req/req_set.py", line 736, in install requirement.uninstall(auto_confirm=True) File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/pip/req/req_install.py", line 742, in uninstall paths_to_remove.remove(auto_confirm) File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/pip/req/req_uninstall.py", line 115, in remove renames(path, new_path) File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/pip/utils/__init__.py", line 267, in renames shutil.move(old, new) File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/shutil.py", line 299, in move copytree(src, real_dst, symlinks=True) File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/shutil.py", line 208, in copytree raise Error, errors Error: [('/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/PyObjC/Message/__init__.py', '/var/folders/bk/zdhpxqj14y5fzcvlpybb4b640000gn/T/pip-Gd3OiE-uninstall/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/PyObjC/Message/__init__.py', "[Errno 1] Operation not permitted: '/var/folders/bk/zdhpxqj14y5fzcvlpybb4b640000gn/T/pip-Gd3OiE-uninstall/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/PyObjC/Message/__init__.py'"), ('/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/PyObjC/Message/__init__.pyc', '/var/folders/bk/zdhpxqj14y5fzcvlpybb4b640000gn/T/pip-Gd3OiE-uninstall/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/PyObjC/Message/__init__.pyc', "[Errno 1] Operation not permitted: '/var/folders/bk/zdhpxqj14y5fzcvlpybb4b640000gn/T/pip-Gd3OiE-uninstall/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/PyObjC/Message/__init__.pyc'"), ('/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/PyObjC/Message/_metadata.py', '/var/folders/bk/zdhpxqj14y5fzcvlpybb4b640000gn/T/pip-Gd3OiE-uninstall/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/PyObjC/Message/_metadata.py', "[Errno 1] Operation not permitted: '/var/folders/bk/zdhpxqj14y5fzcvlpybb4b640000gn/T/pip-Gd3OiE-uninstall/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/PyObjC/Message/_metadata.py'"), ('/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/PyObjC/Message/_metadata.pyc', '/var/folders/bk/zdhpxqj14y5fzcvlpybb4b640000gn/T/pip-Gd3OiE-uninstall/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/PyObjC/Message/_metadata.pyc', "[Errno 1] Operation not permitted: '/var/folders/bk/zdhpxqj14y5fzcvlpybb4b640000gn/T/pip-Gd3OiE-uninstall/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/PyObjC/Message/_metadata.pyc'"), ('/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/PyObjC/Message', '/var/folders/bk/zdhpxqj14y5fzcvlpybb4b640000gn/T/pip-Gd3OiE-uninstall/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/PyObjC/Message', "[Errno 1] Operation not permitted: '/var/folders/bk/zdhpxqj14y5fzcvlpybb4b640000gn/T/pip-Gd3OiE-uninstall/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/PyObjC/Message'”)]

9 36

Re: [Pythonmac-SIG] [Pyobjc-dev] PyObjC and macOS 10.12 (Sierra)
by Christopher Barker Dec. 16, 2016

Dec. 16, 2016

Sorry -- looks like I took this offline by accident. I really prefer mailing list to be set with reply-to to the list.... So I"ll leave more the the thread than I usually do. If your mail client collapses old quotes, you may want to expand them... On Thu, Dec 15, 2016 at 9:27 AM, Ronald Oussoren <ronaldoussoren(a)mac.com> wrote: > > On 15 Dec 2016, at 17:34, Christopher Barker <pythonchb(a)gmail.com> wrote: > > > On Thu, Dec 15, 2016 at 12:59 AM Ronald Oussoren <ronaldoussoren(a)mac.com> > wrote: > >> >> > Frameworks have the nice feature that everything related to the >> framework is stored in a single location, with proscribed location for that >> location. >> >> Yeah, I really like the approach -- the *nix habit of scattering stuff >> all over the place is really ugly. >> >> > This is especially useful when doing side-by-side installation of >> Python 2 and Python 3, those naturally get different locations for their >> binaries which avoids conflicts when installing scripts into both of them. >> >> >> In the conda case -- conda is managing the whole environment for you >> instead -- kinda like a monster Framework, I suppose, >> >> Putting a Framework inside a Conda environment is kinda weird-- and I >> think the conda folks wanted to keep things as consistent across platforms >> as possible. >> > > How does conda deal with having both Python2 and Python3? Or is that out > of scope? From what I’ve seen and heard at conferences the scientific > users of python seem to move to Python 3 at a high speed. > > conda controls python itself in isolated environments, so a given environment can be python 2 or python 3. and you can have any number of environments hanging around. It doesn't support python2 and pyton3 is the same environment though -- which is a pity. > >> > Building python.app + the launcher script outside of a framework should >> be easy, but I don’t understand why you’d want to do so as this will give >> you yet another way to deploy python on macOS. >> >> There are already multiple ways to deploy python on macOS ;-) >> > > I know, but that’s no reason to make it worse. > FAir enough -- but having an easy way to build a non-framework python that supports GUIs would be nice -- and then all teh "unixey" builds could use that -- so no net increase ;-) > And in Conda's case, there are good reasons for it. But having the python > binary in conda work for GUI apps would be a very good thing. > > I have never gotten an answer from the conda folks as to why they did the > app bundle the way they did -- I suspect it was simply the first way they > came up with that seemed to work. > > And apparently there are only a few people trying to use conda for GUI > apps on the Mac -- no not much motivation for change. ( and what they have > mostly works) > > > > BTW. In the longer run I’d love to see a binary distribution that’s just > a Python.app with everything bundled inside, that would reduce the friction > of installing python even further. > > > Installing Python isn't where the real friction is -- it's installing > third party packages that provides the friction. > > A GUI wrapper around pip et al might be a nice thing, though -- so folks > could have a Mac-ish way to deal with dependencies. > > > The main launcher of the app bundle could be a launcher for IDLE, > possibly enhanced with a menu for installing symlinks to bundled > executables/scripts into /usr/local/bin. > > I don't think that's a good idea -- IDLE has pretty limited usefulness. > I'd rather see Python installed on such a way as to enable smooth command > line usage, other IDEs, etc. > That shouldn’t be a problem, it would basically switch the current setup > around: we now have a Python.framework containing a Python.app, and would > end up with a Python.app containing a Python.framework (or a shared library > install, doesn’t really matter). Other tools could still use the python > installation inside the app bundle. > I guess a few well-placed symlinks would make is all work fine. I mentioned IDLE because that is the primary GUI shipped with the CPython > distribution and a GUI that’s there is better than one that isn’t ;-). > well, yes and no -- I'd rather folks would need to choose an IDE -- an easy way to choose IDLE would be good, though. > Which burying it an app might be fine for -- much like the framework > build. But the "Python" app could be a GUI tool for managing the python > install -- the symlink thing, package management, etc. maybe a front end > for py2app? an easy way to bring up a (iPython?) console…. > If only I had the time to spend serious time on this… I think a > Python.app with a useful GUI could be a worthwhile project, but > realistically speaking I don’t have time to work on this. > I know the feeling -- not much general interest in the Mac as platform at all :-( -- except and a version of Unix. I have a hard time keeping my current projects alive, I’m currently working > my way through a couple of years of backlog in the py2app tracker and > that’s just fixing smallish issues with the current code base (recipes that > no longer work, supporting newer versions of python). Py2app itself also > needs some serious attention: the code is a distutils extension and as such > is basically untestable using unittests. Furthermore distutils/setupools > extensions themselves are more of a legacy feature, the world is slowly > moving away from setuptools. I have some vague plans about the redesign of > the py2app interface using a structured configuration format > (YAML/TOML/JSON/…), but haven’t had time yet to make those plans more > concrete. > For what it's worth, I'd rather see this than a MacPython GUI ... > > >> Is there an easy way to have one App bundle with multiple "launchers". Or >> is that a Franework with multiple apps…. >> > > The application bundle has 1 main entry point that’s launched when you > start the app. The app could contain embedded application bundles for other > functionality, the “Xcode -> Open Developer Tool” menu in Xcode is an > example of that. > > ahh -- so our MacPython GUI could launch IDLE, or an iPython console (Or notebook), or ... slick! Now we just need someone to write it ..... >> In practice though, pretty much anyone doing real work with Python is >> going to need the command line at some point -- so I always just bite the >> bullet and start newbies off that way. >> > > The unix command-line is too powerful as a toolset to ignore, but IMHO it > should be possible to have a useful environment that doesn’t need the > command-line to do useful work (says someone who tends to live on the > command-line, and most of the time doesn’t even use a graphical text > editor). > > Anyway -- thanks for the PyObj updated an wheels! -CHB -- Christopher Barker, PhD Python Language Consulting - Teaching - Scientific Software Development - Desktop GUI and Web Development - wxPython, numpy, scipy, Cython

1 0

Pythonmac-SIG Digest, Vol 147, Issue 16
by Jim Holliman Dec. 15, 2016

Dec. 15, 2016

Send Pythonmac-SIG mailing list submissions to pythonmac-sig(a)python.org To subscribe or unsubscribe via the World Wide Web, visit https://mail.python.org/mailman/listinfo/pythonmac-sig or, via email, send a message with subject or body 'help' to pythonmac-sig-request(a)python.org You can reach the person managing the list at pythonmac-sig-owner(a)python.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Pythonmac-SIG digest..."

1 0

Re: [Pythonmac-SIG] Phantom Dock menu entries for tkinter dialogs on Mac
by Mark Lutz Dec. 13, 2016

Dec. 13, 2016

Ah; thanks for checking. I should have tested under Tk 8.6, but was following the stock recommendation at python.org to use ActiveState's 8.5 (as most of the target audience will), and python.org's installers (which don't support Tk 8.6, but may soon?). Will upgrade and have a look. Hopefully, 8.6 will clear up a few other AS 8.5 oddities too - weirdly slow Text scrolls, windows losing focus on popups, and the like - though it largely works well enough to qualify as compelling, and better than the version shipped with the box. Cheers, --Mark Lutz, http://learning-python.com > -----Original Message----- > From: Kevin Walzer <kw(a)codebykevin.com> > To: pythonmac-sig(a)python.org > Subject: Re: [Pythonmac-SIG] Phantom Dock menu entries for tkinter dialogs > on Mac > Date: Tue, 13 Dec 2016 06:50:53 -0500 > > On 12/6/16 9:43 PM, Mark Lutz wrote: > > A simple demo of the problem is attached below: every "destroy" popup > > lingers on in the launcher's Dock menu after it's closed (whether by > > the red "X" or the widget.destroy() callback), and remains in the Dock > > menu until the main window is closed (by widget.quit() or otherwise). > > This happens whether the script is run by click or command line. > > I can't reproduce this using Tkinter built against Tk 8.6.6. There were > a lot of issues with menus, the event loop, and so on that have been > fixed--I don't recall seeing this exact issue but I did see similar > things with "ghost windows" hanging around in a system menu after being > destroyed. You may want to update your installation of Tk. > > --Kevin > > -- > Kevin Walzer > Code by Kevin/Mobile Code by Kevin > http://www.codebykevin.com > http://www.wtmobilesoftware.com > > _______________________________________________ > Pythonmac-SIG maillist - Pythonmac-SIG(a)python.org > https://mail.python.org/mailman/listinfo/pythonmac-sig > unsubscribe: https://mail.python.org/mailman/options/Pythonmac-SIG >

1 0

Need help with Python Library link error in OS X 10.11.6
by Manohar K Chintala Dec. 13, 2016

Dec. 13, 2016

Hello Team, I am setting up Appium for mobile test automation on new Mac with OS X 10.11.6 and as part of that I had to run following command. brew install --HEAD libimobiledevice and following error message was displayed at the end of this command run ************************************************************** checking consistency of all components of python development environment... no configure: error: Could not link test program to Python. Maybe the main Python library has been installed in some non-standard library path. If so, pass it to configure, via the LDFLAGS environment variable. Example: ./configure LDFLAGS="-L/usr/non-standard-path/python/lib" ============================================================================ ERROR! You probably have to install the development version of the Python package for your distribution. The exact name of this package varies among them. ============================================================================ ******************************************************************* I tried to run following command ./configure PYTHON_LDFLAGS="-lpython3.4m" as suggested however it failed as it couldn't find "configure" in current user's folder. I also searched in other file system to locate "configure" but couldn't find it. I need to revolve this Python lib link issue and need suggestions on how to do it. Things I need help on: 1. Where can I find "configure" to run the suggested LDFLAGS command. If it is not available in my Mac, what is the next step for me. 2. Do I need to install any Python builds to get rid of this error and be able to run brew install --HEAD libimobiledevice command successfully. Thank you Regards Manohar

3 2

Re: [Pythonmac-SIG] Examples of vendoring python 3 with py2app
by Cosimo Lupo Dec. 13, 2016

Dec. 13, 2016

Thank you all for the replies. I've tried using py2app with a framework python 3.5.2 from Python.org and can confirm it correctly bundles everything up in the generated app. I somehow was under the impression that I had to do something special about it, but it turns out it is much easier than I thought! Thanks again :) Cosimo On 13 December 2016 at 16:21, Christopher Barker <pythonchb(a)gmail.com> wrote: > Have tried it? Back in the day, py2app would embed the entire python > runtime if you ran it with a non-Apple python. > > I haven't tried it with py3, but it may "just work" > > You'll know, 'cause you will get a big bundle :-). And you can, of course > look inside and see what's there. > > -CHB > > > On Tue, Dec 13, 2016 at 2:28 AM Cosimo Lupo <cosimo.lupo(a)daltonmaag.com> > wrote: > >> >> >> >> >> >> >> >> >> >> >> Hello list, >> >> >> >> >> >> Apologies if this is not the right place to ask about this. >> >> >> >> >> >> I would like to distribute a self-contained OSX app of an application of >> mine written in Python 3. I've used py2app in the past to ship apps written >> in Python 2.7, that linked to the system Python framework. >> >> >> Now I'm wondering if I could if and how I could "vendor" Python 3.5 >> inside my py2app-generated app. >> >> >> >> >> >> In the py2app docs I could not find information as to how to embed the >> python 3.5 interpreter and stdlib alongside the generated .app bundle. >> >> >> >> >> >> Could anyone point me in the right direction, and/or link to existing >> open source apps that do this? >> >> >> >> >> >> Thank you for your help. >> >> >> >> >> >> -- >> >> >> Cosimo Lupo >> >> >> >> >> >> >> _______________________________________________ >> >> Pythonmac-SIG maillist - Pythonmac-SIG(a)python.org >> >> https://mail.python.org/mailman/listinfo/pythonmac-sig >> >> unsubscribe: https://mail.python.org/mailman/options/Pythonmac-SIG >> >>

1 0

Phantom Dock menu entries for tkinter dialogs on Mac
by Mark Lutz Dec. 13, 2016

Dec. 13, 2016

When using Tk on a Mac (Python 3.5, ActiveState Tk 8.5, Mac 10.11), why does the Python launcher retain Dock right-click menu entries for every Toplevel window that has been closed? This doesn't happen for common dialogs, but does for every custom dialog the closes with a widget.destroy(). It also happens for IDLE dialogs that are not withdrawn/redrawn, so it seems fairly pervasive. A simple demo of the problem is attached below: every "destroy" popup lingers on in the launcher's Dock menu after it's closed (whether by the red "X" or the widget.destroy() callback), and remains in the Dock menu until the main window is closed (by widget.quit() or otherwise). This happens whether the script is run by click or command line. Any ideas? The phantom Dock menu entries are useless (and even buggy) for modal dialogs that have been dismissed. Thanks, --Mark Lutz, http://learning-python.com -------- from tkinter import * def destroyer(): popup = Toplevel() popup.title('destroyer') Button(popup, text='Destroy', command=popup.destroy, width=40).pack() def quitter(): popup = Toplevel() popup.title('quitter') Button(popup, text='Quit', command=popup.quit, width=40).pack() root = Tk() root.title('root') Button(root, text='destroyer', command=destroyer, width=40).pack() Button(root, text='quitter', command=quitter, width=40).pack() root.mainloop() --------

2 1

Examples of vendoring python 3 with py2app
by Cosimo Lupo Dec. 13, 2016

Dec. 13, 2016

Hello list, Apologies if this is not the right place to ask about this. I would like to distribute a self-contained OSX app of an application of mine written in Python 3. I've used py2app in the past to ship apps written in Python 2.7, that linked to the system Python framework. Now I'm wondering if I could if and how I could "vendor" Python 3.5 inside my py2app-generated app. In the py2app docs I could not find information as to how to embed the python 3.5 interpreter and stdlib alongside the generated .app bundle. Could anyone point me in the right direction, and/or link to existing open source apps that do this? Thank you for your help. -- Cosimo Lupo

3 3

PyObjC 3.2.1 released
by Ronald Oussoren Dec. 13, 2016

Dec. 13, 2016

Hi, I’ve just pushed PyObjC 3.2.1 to PyPI. This fixes a number of small issues in PyObjC 3.2, but the primary new feature is that there are now wheels on PyPI. I’ve tested the wheels on OSX 10.12 with the Python.org <http://python.org/> “intel” installers (the default download option for the OSX installers) and Homebrew. The wheels should also work fine with older OSX releases. Ronald

4 4