Re: [Pythonmac-SIG] PyObjC - Apple sample code

st to figure out how to get those addressed with the PyPA community. -glyph > On Apr 28, 2017, at 4:20 AM, Ben Byram-Wigfield wrote: > > I ran the installer package for the latest python 2.7, and then used > easy_install to install PyObjC. > I get the same errors on two separat

Re: [Pythonmac-SIG] Uninstalling

> On Jul 20, 2017, at 3:24 AM, Piet van Oostrum wrote: > > Normally you should never touch anything in /usr/bin or /usr/lib. That is > Apple territory. You can't any more. $ touch /usr/bin/just-testing touch: /usr/bin/just-testing: Operation not permitted $ sudo touch /usr/bin/just-testing Pa

Re: [Pythonmac-SIG] Failure on pip upgrade attempt

PYTHONPATH itself is a bit of an anachronism :). It's the past, virtualenvs are the future! https://orbifold.xyz/pythonpath.html <https://orbifold.xyz/pythonpath.html> (If you're using PyObjC and avoiding virtualenvs for that reason, check out https://github.com/glyph/v

Re: [Pythonmac-SIG] [ANN] PyObjC 5.0

hpakovski/MASShortcut> built and bundled with my application. -glyph P.S.: speaking of build gymnastics, does anyone on this list happen to have a way to use CocoaPods or something similar to pull in open source Cocoa frameworks to a PyObjC application?_

Re: [Pythonmac-SIG] [ANN] PyObjC 5.0

> On Sep 21, 2018, at 4:50 AM, Ronald Oussoren wrote: > > > >> On 21 Sep 2018, at 05:59, Glyph > <mailto:gl...@twistedmatrix.com>> wrote: >> >> On Sep 18, 2018, at 1:22 PM, Ronald Oussoren via Pythonmac-SIG >> mailto:pythonmac-si

[Pythonmac-SIG] ctypes MemoryError when attempting to launch notarized app

I adjusted my code-signing to use the new, stricter requirements imposed by app notarization. I managed to get it successfully notarized, but the app is now non-functional as a result: at startup, I get: Traceback (most recent call last): File "my.app/Contents/Resources/__boot__.py", line 93,

[Pythonmac-SIG] py2app apps codesigned with "--options runtime", i.e. any notorizable app, fails to launch with ctypes error (was Re: [Pyobjc-dev] ctypes MemoryError when attempting to launch notarize

> On Oct 28, 2018, at 2:27 AM, Ronald Oussoren wrote: > > > >> On 28 Oct 2018, at 06:27, Glyph wrote: >> >> I adjusted my code-signing to use the new, stricter requirements imposed by >> app notarization. I managed to get it successfully notarized, but

Re: [Pythonmac-SIG] py2app apps codesigned with "--options runtime", i.e. any notorizable app, fails to launch with ctypes error (was Re: [Pyobjc-dev] ctypes MemoryError when attempting to launch nota

> On Oct 28, 2018, at 11:20 AM, Glyph wrote: > > > >> On Oct 28, 2018, at 2:27 AM, Ronald Oussoren > <mailto:ronaldousso...@mac.com>> wrote: > >>> >>> Curiously, this is the same traceback that comes from >>> https://forum.k

Re: [Pythonmac-SIG] py2app apps codesigned with "--options runtime", i.e. any notorizable app, fails to launch with ctypes error (was Re: [Pyobjc-dev] ctypes MemoryError when attempting to launch nota

> On Oct 28, 2018, at 1:48 PM, Ronald Oussoren wrote: > > > >> On 28 Oct 2018, at 19:47, Glyph wrote: >> >> >> >>> On Oct 28, 2018, at 11:20 AM, Glyph wrote: >>> >>> >>> >>>> On Oct 28, 2018, at

[Pythonmac-SIG] notarization works! (was Re: not that)

> On Oct 28, 2018, at 2:57 PM, Glyph wrote: > >> I wonder what the “hardened runtime” option actually does and enforces. In >> 3.7 the line in ctypes/__init__.py that causes the exception is a call that >> creates a dummy C function, and likely triggers the first al

Re: [Pythonmac-SIG] [ANN] PyObjC 5.0

> On Sep 21, 2018, at 4:50 AM, Ronald Oussoren wrote: > >> P.S.: speaking of build gymnastics, does anyone on this list happen to have >> a way to use CocoaPods or something similar to pull in open source Cocoa >> frameworks to a PyObjC application? > > I haven’t looked into this yet. I gue

Re: [Pythonmac-SIG] [Pyobjc-dev] notarization works! (was Re: not that)

On Sun, Oct 28, 2018, at 11:58 PM, Ronald Oussoren wrote: > > >> On 29 Oct 2018, at 00:56, Glyph wrote: >> >> >> >>> On Oct 28, 2018, at 2:57 PM, Glyph wrote:>>> >>>> I wonder what the “hardened runtime” option actually doe

Re: [Pythonmac-SIG] ANN: PyObjC 11.0

Thanks Ronald! Congratulations! Definitely been looking forward to this one. > On Jan 14, 2025, at 12:50 PM, Ronald Oussoren via Pythonmac-SIG > wrote: > > I'm happy to announce the 11.0 release of PyObjC, slightly delayed from the > normal major release in October. > > This release has two m

[Pythonmac-SIG] Re: Do we want to keep pythonmac-sig?

> On May 16, 2025, at 6:52 PM, Matthew Dixon Cowles wrote: > > Jack, > >> I just got a mail from the Python mailman server admin that they >> will shortly be upgrading the mailman server, and the question is >> whether to keep the Pythonmac-SIG mailing list alive or archive it. > >> Personally

Re: [Pythonmac-SIG] PyObjC and macOS 10.12 (Sierra)

> On Sep 13, 2016, at 3:35 PM, Andrew Jaffe wrote: > > Aha! > > $ ls -lt /Library/Python/2.7/site-packages/ > total 0 > -rwxr-xr-x 1 root wheel 157 31 Jul 02:36 Extras.pth* > -rw-r--r-- 1 root wheel 119 31 Jul 02:36 README > $ more /Library/Python/2.7/site-packages/Extras.pth > /Sy

Re: [Pythonmac-SIG] PyObjC and macOS 10.12 (Sierra)

> On Sep 13, 2016, at 12:05 PM, Jack Jansen wrote: > > I think > /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages > is a very old location for storing Python packages. Recently things have been > installed in /Library/Python/2.7/site-packages. > > Could it be tha

Re: [Pythonmac-SIG] PyObjC and macOS 10.12 (Sierra)

> On Sep 13, 2016, at 3:05 PM, Andrew Jaffe wrote: > > But this is the framework (non-apple!) build!… "framework build" refers to the way that Python is built. Apple's python, Python.org's python, and Homebrew's python are all framework builds. So, to be clear: this is python.org python? >

Re: [Pythonmac-SIG] PyObjC and macOS 10.12 (Sierra)

> On Sep 20, 2016, at 10:29 AM, Andrew Jaffe wrote: > > On 17/09/2016 18:59, Glyph Lefkowitz wrote: >> >>> On Sep 17, 2016, at 9:27 AM, Ned Deily wrote: >>> >>> On 2016-09-13 19:33, Glyph Lefkowitz wrote: >>>>> On Sep 13, 2016, at 3:35

Re: [Pythonmac-SIG] [Pyobjc-dev] PyObjC and macOS 10.12 (Sierra)

Homebrew? If it's a VM, then system integrity is less of a concern; have you tried just blanket disabling SIP to see if that improves the situation? I've had some luck with other tools (dtrace, mostly) working in that configuration. (I had to totally disable SIP though, disabling o

Re: [Pythonmac-SIG] PyObjC and macOS 10.12 (Sierra)

> On Sep 17, 2016, at 9:27 AM, Ned Deily wrote: > > On 2016-09-13 19:33, Glyph Lefkowitz wrote: >>> On Sep 13, 2016, at 3:35 PM, Andrew Jaffe >> <mailto:a.h.ja...@gmail.com>> wrote: >>> >>> Aha! >>> >>> $ ls -lt /Library/Pyt

Re: [Pythonmac-SIG] PyObjC and macOS 10.12 (Sierra)

> On Oct 12, 2016, at 11:49 AM, Andrew Jaffe wrote: > > Not me. If I understand correctly, Glyph -- who undoubtedly understand the > situation better than I do -- still thinks that there's no actual bug here, > since we shouldn't be using the framework build thi

Re: [Pythonmac-SIG] PyObjC and macOS 10.12 (Sierra)

> On Sep 21, 2016, at 01:52, Andrew Jaffe wrote: > > That would work, and in fact I don't really need PyObjC (sorry, Ronald!) but > I've got my whole setup working with the "global" python.org > framework build, so I am used to that... and the Sierra > status quo does see

Re: [Pythonmac-SIG] PyObjC and macOS 10.12 (Sierra)

> On Oct 6, 2016, at 2:56 AM, Andrew Jaffe wrote: > > On 17/09/2016 18:59, Glyph Lefkowitz wrote: >> >>> On Sep 17, 2016, at 9:27 AM, Ned Deily wrote: >>> >>> On 2016-09-13 19:33, Glyph Lefkowitz wrote: >>>>> On Sep 13, 2016, at 3:35

Re: [Pythonmac-SIG] PyObjC and macOS 10.12 (Sierra)

> On Oct 7, 2016, at 1:36 AM, Andrew Jaffe wrote: > > On 06/10/2016 20:26, Glyph Lefkowitz wrote: >>> On Oct 6, 2016, at 2:56 AM, Andrew Jaffe wrote: >>> On 17/09/2016 18:59, Glyph Lefkowitz wrote: >>>>> On Sep 17, 2016, at 9:27 AM, Ned Deily wrote:

Re: [Pythonmac-SIG] PyObjC 3.2 released

ze that was possible before. Hopefully none of my code will be affected as a result :-). Is there any chance that now this release is done, wheel builds might be on the horizon? :) -glyph ___ Pythonmac-SIG maillist - Pythonmac-SIG@python.org https:

Re: [Pythonmac-SIG] PyObjC 3.2 released

> On Dec 6, 2016, at 10:36 AM, Ronald Oussoren wrote: > > >> On 6 Dec 2016, at 19:19, Glyph Lefkowitz wrote: >> >> >>> On Dec 6, 2016, at 8:59 AM, Ronald Oussoren wrote: >>> >>> Hi, >>> >>> I’ve pushed PyObjC 3.2 t

Re: [Pythonmac-SIG] PyObjC 3.2 released

> On Dec 6, 2016, at 12:17 PM, Ronald Oussoren wrote: > >> >> On 6 Dec 2016, at 20:30, Glyph Lefkowitz > <mailto:gl...@twistedmatrix.com>> wrote: >> >> >>> On Dec 6, 2016, at 10:36 AM, Ronald Oussoren >> <mailto:ronaldousso...@ma

Re: [Pythonmac-SIG] PyObjC 3.2.1 released

upload 2.7/3.5 wheels for that as well? It would just complete the set :-). Thanks again; this is fabulous, -glyph ___ Pythonmac-SIG maillist - Pythonmac-SIG@python.org https://mail.python.org/mailman/listinfo/pythonmac-sig unsubscribe: https://mail.python.org/mailman/options/Pythonmac-SIG

Re: [Pythonmac-SIG] [Pyobjc-dev] PyObjC 3.2 released

> On Dec 6, 2016, at 12:55 PM, Ronald Oussoren wrote: > > >> On 6 Dec 2016, at 21:43, Glyph Lefkowitz > <mailto:gl...@twistedmatrix.com>> wrote: >> >> >>> Anyways, there may be a 3.2.1 release by the end of the week, I just >>> noti

Re: [Pythonmac-SIG] PyObjC 3.2 released

> On Dec 7, 2016, at 12:21 AM, Ronald Oussoren wrote: > > >> On 7 Dec 2016, at 00:28, Glyph Lefkowitz > <mailto:gl...@twistedmatrix.com>> wrote: >> >> Was this intentionally off-list? (Feel free to forward my reply back to the >> list

Re: [Pythonmac-SIG] PyObjC 3.2 released

> On Dec 8, 2016, at 3:37 AM, Ronald Oussoren wrote: > > >> On 8 Dec 2016, at 00:40, Glyph Lefkowitz > <mailto:gl...@twistedmatrix.com>> wrote: >>> >>> >>> Last time I checked systems like Homebrew only build 64-bit binaries (on

Re: [Pythonmac-SIG] PyObjC and macOS 10.12 (Sierra)

> On Dec 13, 2016, at 8:37 AM, Christopher Barker wrote: > > Personally, I have avoided all this mess the last couple years by using conda > (miniconda install). It does a nice job of keeping entirely separate from the > system ( or any other) python, and it can manage non-python libs as well,

Re: [Pythonmac-SIG] PyObjC and macOS 10.12 (Sierra)

st from a "will they link and run" perspective. And many CoreFoundation APIs definitely work without an app bundle, so, not completely useless :-). -glyph ___ Pythonmac-SIG maillist - Pythonmac-SIG@python.org https://mail.pyt

Re: [Pythonmac-SIG] py2app release delayed

> On Dec 18, 2016, at 12:39 PM, Ronald Oussoren wrote: > > 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 th

Re: [Pythonmac-SIG] apple-Python and TLS 1.0

> On Jan 10, 2017, at 9:21 AM, Kevin Ollivier wrote: > > Hi Jack, > > No, I think you're spot on, this is a big problem. Actually, 2.7.9-2.7.12, > even the Python.org ones, are already somewhat broken because they use > Apple's ancient OpenSSL version. All the ciphers supported by that versio

Re: [Pythonmac-SIG] apple-Python and TLS 1.0

ittle command-line expertise to be able to get something like Homebrew to behave properly would be able to get on-screen instructions and prompts that would help them get set up with a correct command linee. -glyph ___ Pythonmac-SIG maillist - Pythonmac-SIG@python.org https://mail.python.org/mailman/listinfo/pythonmac-sig unsubscribe: https://mail.python.org/mailman/options/Pythonmac-SIG

Re: [Pythonmac-SIG] py2app 0.12 and modulegraph 0.14 released

s are serious enough to not delay the release any more. On > to the next release… Thanks for the release, Ronald! Looking forward to some of those fixes, and good luck on the next batch :-). -glyph ___ Pythonmac-SIG maillist - Pythonmac-SIG@pyth