[Pythonmac-SIG] PyObjC 9.1b1

PyObjC 9.1 is one of the rare times that I'm publishing explicit beta releases. PyObjC 9.1b1 is available on PyPI ("pip install pyobjc-9.1b1"). This release contains the usual SDK updates (macOS 13.3) and minor bugfixes, but more importantly it contains some major changes to pyobjc-core. Becaus

Re: [Pythonmac-SIG] PyObjC and Criollo HTTP server

Yep, that’s it. Just for posterity here’s the successful proof of concept. import objc from Foundation import NSLog, NSRunLoop CRApplication = objc.lookUpClass("CRApplication") objc.registerMetaDataForSelector( b'CRRouter', b'get:block:', { 'arguments': {

Re: [Pythonmac-SIG] PyObjC and Criollo HTTP server

> On 9 Jan 2020, at 00:23, Rand Dvorak wrote: > > I got it working. Basically I have a main.py file in Resources that get > loaded and run by PyRun_SimpleFile in applicationDidFinishLaunching. Control > is then passed to the python interpreter. Notice the infinite loop at the > bottom whic

Re: [Pythonmac-SIG] PyObjC and Criollo HTTP server

I got it working. Basically I have a main.py file in Resources that get loaded and run by PyRun_SimpleFile in applicationDidFinishLaunching. Control is then passed to the python interpreter. Notice the infinite loop at the bottom which is needed because the interpreter finishes executing the

Re: [Pythonmac-SIG] PyObjC and Criollo HTTP server

Here’s what I’ve got so far. I don’t know much about the metadata, but I did try gen_bridge_metadata to try and decipher it, but I think it doesn’t generate it correctly either. import objc CRApplication = objc.lookUpClass("CRApplication") objc.registerMetaDataForSelector( b'CRHTTPSer

Re: [Pythonmac-SIG] PyObjC and Criollo HTTP server

What is the type of ‘server’? And I just noticed the metadata block is a bit of, the callable is argument 3 instead of 2. Ronald -- On the road, hence brief. > On 8 Jan 2020, at 17:18, Rand Dvorak wrote: > > Same result: > > File "main.py", line 40, in > server.get_block_("/", hel

Re: [Pythonmac-SIG] PyObjC and Criollo HTTP server

Same result: File "main.py", line 40, in server.get_block_("/", helloHandler) TypeError: Argument 3 is a block, but no signature available > On Jan 8, 2020, at 03:20, Ronald Oussoren wrote: > > Please change “get_block_” to “get:block:” in the call to > objc.registerMetadataForSelector

Re: [Pythonmac-SIG] PyObjC and Criollo HTTP server : SOLVED

Turns out the instance of server is indeed a CRHTTPServer, but the class that need the metadata registered is CRRouter. > On Jan 8, 2020, at 15:41, Ronald Oussoren wrote: > > What is the type of ‘server’? > > And I just noticed the metadata block is a bit of, the callable is argument 3 > in

Re: [Pythonmac-SIG] PyObjC and Criollo HTTP server

Same results with this code: import objc CRApplication = objc.lookUpClass("CRApplication") objc.registerMetaDataForSelector( b'CRServer', b'get_block_', { 'arguments': { 2: { 'callable': { 'arguments':

Re: [Pythonmac-SIG] PyObjC and Criollo HTTP server

Please change “get_block_” to “get:block:” in the call to objc.registerMetadataForSelector. Ronald — Twitter: @ronaldoussoren Blog: https://blog.ronaldoussoren.net/ > On 8 Jan 2020, at 02:04, Rand Dvorak wrote: > > Same results with this code: > > import objc > CRApplication = objc.lookUpCl

Re: [Pythonmac-SIG] PyObjC and Criollo HTTP server

And given de example on https://criollo.io: - The class name is CRServer, not CRApplication - The selector is “get:block:” instead of “get_block:”, which also means the block is argument 3 instead of 2. >> objc.registerMetaDataForSelector( >> b'CRServer', >> b’get:block:', >> { >>

Re: [Pythonmac-SIG] PyObjC and Criollo HTTP server

Hi, You also need to remove the call to objc.selector. With correct metadata “blocks” are callables in Python code. Ronald — Twitter: @ronaldoussoren Blog: https://blog.ronaldoussoren.net/ > On 6 Jan 2020, at 23:59, Rand Dvorak wrote: > > Same result: > > Updated code: > > import objc > C

Re: [Pythonmac-SIG] PyObjC and Criollo HTTP server

I found the place in the code to try to understand what is happening, but am a little out of my depth In libffi_support.m case _C_ID: if (argtype[1] == '?') { /* Argument is a block */ if (argument == Py_None) {

Re: [Pythonmac-SIG] PyObjC and Criollo HTTP server

Same result: Updated code: import objc CRApplication = objc.lookUpClass("CRApplication") objc.registerMetaDataForSelector( b'CRApplication', b'get_block_', { 'arguments': { 2: { 'callable': { 'argumen

Re: [Pythonmac-SIG] PyObjC and Criollo HTTP server

So much for typing code in Mail.app…. “Retail” should be “retval”. Ronald — Twitter: @ronaldoussoren Blog: https://blog.ronaldoussoren.net/ > On 6 Jan 2020, at 15:27, Ronald Oussoren via Pythonmac-SIG > wrote: > > > >> On 6 Jan 2020, at 00:51, Rand Dvorak wrote: >> >> >> I am trying to

Re: [Pythonmac-SIG] PyObjC and Criollo HTTP server

> On 6 Jan 2020, at 00:51, Rand Dvorak wrote: > > > I am trying to implement a simple server in PyObjC for the Criollo HTTP > server. The server has a method to set route handlers by passing a block to > setup the route and then when it receives and HTTP request for the route it > calls th

[Pythonmac-SIG] PyObjC and Criollo HTTP server

I am trying to implement a simple server in PyObjC for the Criollo HTTP server. The server has a method to set route handlers by passing a block to setup the route and then when it receives and HTTP request for the route it calls the block. The block has the signature: typedef void(^CRRouteB

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

> On 29 Oct 2018, at 18:22, Glyph wrote: >>> >> >> Which package needs _cffi_backend? I can add a recipe for that to py2app to >> do this automagically. > > This may sound obvious, but: cffi :-). In my case, pyOpenSSL -> cryptography > -> cffi. I’ll look into adding a recipe for this to p

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 does and enforces. In 3.7 the line in ctypes/__init__.py that

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

> On 29 Oct 2018, at 07:58, Ronald Oussoren via Pyobjc-dev > wrote: > > MAP_JIT is a mmap flag that’s apparently introduced in 10.14. The slides at > https://developer.apple.com/videos/play/wwdc2018/702/ > mention this flag and > the h

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

> 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 does and enforces. >>> In 3.7 the line in ctypes/__init__.py that causes the exception is a call >>>

Re: [Pythonmac-SIG] [Pyobjc-dev] ctypes MemoryError when attempting to launch notarized app

> 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 the app is > now non-functional as a result: at startup, I get: > > Traceback (most recent call last):

[Pythonmac-SIG] PyObjC 4.2.2

Hi, I’ve pushed PyObjC 4.2.2 to PyPI. This is a very minor bug fix release that I’ve pushed out to clear the queue before WWDC. There is one new feature with this release: There are now two variants of the binary wheels for Python 3.6 and 3.7, both now have variants for the universal build for

[Pythonmac-SIG] PyObjC 4.0b1

Hi, I’ve uploaded a test release of PyObjC to PyPI: PyObjC 4.0b1. The major difference with the previous release on PyPI is support for APIs introduced in macOS 10.13, which is why this is a beta release. I’ll push out a final release once 10.13 is released. The beta also fixes a number of bug

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

Sorry, this just isn’t working for me. I’ve installed Python 3; I’ve reinstalled PyObjC using pip; and I’m still getting syntax errors when I run the script. line 177, in createMyOperatorTable Quartz.CGPDFOperatorTableSetCallback(myTable, b"Do", myOperator_Do) ValueError: depythonifying 'poi

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

> On 2 May 2017, at 13:47, Ben Byram-Wigfield wrote: > > I reinstalled python 2.7.13 from a fresh downloaded .pkg, and used pip to > reinstall PyObjC, but I still get the same errors. > Do the Quartz example scripts work on python 3 ? The example work with both python 3 and python 2.7. Ronal

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

I reinstalled python 2.7.13 from a fresh downloaded .pkg, and used pip to reinstall PyObjC, but I still get the same errors. Do the Quartz example scripts work on python 3 ? Ben > On 29 Apr 2017, at 05:57, Christopher Barker wrote: > > And you really don't want to use easy_install amymore, eit

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

And you really don't want to use easy_install amymore, either. Try pip. I see the appeal of an Apple-supplied python, but Apple has never properly supported it ever since OS-X 10.1. -CHB On Fri, Apr 28, 2017 at 5:19 PM Glyph wrote: > Relying on the system Python for this sort of stuff h

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

Relying on the system Python for this sort of stuff has always guaranteed you'd have an out-of-date version of all of your dependencies. The availability of wheels (thanks again Ronald!!!) for pyobjc means that you don't need the biggest impediment to users installing stuff, which is a C compil

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

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 separate Macs. What should I do to fix the installation? Does Apple not have plans to include (all of) the latest PyObjC? That’s rather sad. The reason I was attract

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

> On 27 Apr 2017, at 10:17, Ben Byram-Wigfield wrote: > > I tried the repository browser there, and the version of > parse_page_contents.py still doesn’t work for me. I’m using the latest > downloaded versions of python 2.7 and PyObjC. I also tried using the default > OS X versions. > The err

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

I tried the repository browser there, and the version of parse_page_contents.py still doesn’t work for me. I’m using the latest downloaded versions of python 2.7 and PyObjC. I also tried using the default OS X versions. The errors are in the attached file. Many thanks ERRORS USING LATEST DOWNLO

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

> On 22 Apr 2017, at 10:45, Ben Byram-Wigfield wrote: > > I’ve been looking at Apple’s Open Source website, where there is lots of > python sample code. But the examples I’ve tried don’t work. They all flag > syntax errors (usually about type conversion), or occasionally make the > python pro

[Pythonmac-SIG] PyObjC - Apple sample code

I’ve been looking at Apple’s Open Source website, where there is lots of python sample code. But the examples I’ve tried don’t work. They all flag syntax errors (usually about type conversion), or occasionally make the python process crash! Particularly, I’m looking at a script to parse the con

Re: [Pythonmac-SIG] [Pyobjc-dev] py2app release delayed

> On 10 Jan 2017, at 19:20, Ronald Oussoren wrote: > > >> On 10 Jan 2017, at 17:00, Barry Scott wrote: >> >> Ronald, >> >> Attached is a patch that cleans up the false positives by allows the recipes >> to tell build_app what is expected to be missing. >> >> I can turn into a pull request

Re: [Pythonmac-SIG] [Pyobjc-dev] py2app release delayed

> On 10 Jan 2017, at 17:00, Barry Scott wrote: > > Ronald, > > Attached is a patch that cleans up the false positives by allows the recipes > to tell build_app what is expected to be missing. > > I can turn into a pull request if you like the direction of this patch. I like the idea.. A pull

Re: [Pythonmac-SIG] [Pyobjc-dev] py2app release delayed

Ronald, Attached is a patch that cleans up the false positives by allows the recipes to tell build_app what is expected to be missing. I can turn into a pull request if you like the direction of this patch. Oh and the syntax errors in PyQt5 have been fixes for the 5.7.1 version. Barry py2app

Re: [Pythonmac-SIG] [Pyobjc-dev] py2app release delayed

Ronald, I have been testing against your hg repo for py2app d3f3d531abc1324b71b3b8c289877b28bed1d7c0. I have removed my PyQt5 and the pkg_resources hack for putz and tzlocal and every thing looks to be working well. This is looking very good. However I did notice some problems in the summary

Re: [Pythonmac-SIG] [Pyobjc-dev] py2app release delayed

> On 27 Dec 2016, at 19:36, Ronald Oussoren wrote: > > >> On 21 Dec 2016, at 00:02, Barry Scott > > wrote: >> >>> >>> On 18 Dec 2016, at 20:39, Ronald Oussoren >> > wrote: >>> >>> Hi, >>> >>> I had hoped to release a new version

Re: [Pythonmac-SIG] [Pyobjc-dev] py2app release delayed

On 27 Dec 2016, at 22:38, Chris Barker wrote:On Tue, Dec 27, 2016 at 11:36 AM, Ronald Oussoren wrote:As an aside to this: I’m considering to remove the site-packages.zip file from the app bundle and store everything outside off zipfiles. A lot of cod

Re: [Pythonmac-SIG] [Pyobjc-dev] py2app release delayed

On Tue, Dec 27, 2016 at 11:36 AM, Ronald Oussoren wrote: > As an aside to this: I’m considering to remove the site-packages.zip file > from the app bundle and store everything outside off zipfiles. A lot of > code works inside zipfiles, but there are too many exceptions and with the > transition

Re: [Pythonmac-SIG] [Pyobjc-dev] py2app release delayed

> On 21 Dec 2016, at 00:02, Barry Scott wrote: > >> >> On 18 Dec 2016, at 20:39, 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 bun

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

> On 15 Dec 2016, at 21:41, Cosimo Lupo wrote: > > +1 on having the official Python.org distribution be a standalone Python.app > that users could just drag-and-drop like with the rest of native non-AppStore > apps! A Python.app from python.org should be a long term plan

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

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

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

+1 on having the official Python.org distribution be a standalone Python.app that users could just drag-and-drop like with the rest of native non-AppStore apps! (I wish Apple shipped macOS with Python 3...) And thanks a lot Ronald for the PyObjC wheels on PyPi :D Cheers -- Cosimo Lupo

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

> On 15 Dec 2016, at 07:25, Christopher Barker wrote: > > On Wed, Dec 14, 2016 at 5:32 PM, Glyph Lefkowitz > wrote: > >> On Dec 14, 2016, at 9:44 AM, Chris Barker > > wrote: >> >> conda also has a non-framework build of Python -- n

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

On Wed, Dec 14, 2016 at 5:32 PM, Glyph Lefkowitz wrote: > > On Dec 14, 2016, at 9:44 AM, Chris Barker wrote: > > conda also has a non-framework build of Python -- not sure if that would > cause any issues with the wheels. > > > I am not up on all the technical specifics, but this suggests to me

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

> On Dec 14, 2016, at 9:44 AM, Chris Barker wrote: > > conda also has a non-framework build of Python -- not sure if that would > cause any issues with the wheels. I am not up on all the technical specifics, but this suggests to me that Conda would be generally unsuitable for use as a Mac nat

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

On Tue, Dec 13, 2016 at 11:16 AM, Glyph Lefkowitz wrote: > If we were to add s PyObjC build to conda-forge, the full stack should > "just work". > > And conda forge has s CI system set up to auto build for various python > versions > > http://conda-forge.github.io/#add_recipe > > > Why would

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)

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, so you don't need Brew. And it has environments that are like virtual

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

> On 14 Sep 2016, at 00:28, Glyph Lefkowitz wrote: > > >> 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

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 > > wrote: >>> >>> >>> Last time I checked systems like Homebrew only build 64-bit binaries (on >>> anything resembling modern hardware). It should be possible

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 > > wrote: >> >> Was this intentionally off-list? (Feel free to forward my reply back to the >> list if not). > > It wasn’t and I’ll continue the conversatio

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 > > wrote: >> >> >>> Anyways, there may be a 3.2.1 release by the end of the week, I just >>> noticed that building PyObjC on 10.12 doesn’t work when using py

Re: [Pythonmac-SIG] PyObjC 3.2.1 released

> On Dec 12, 2016, at 1:25 AM, Ronald Oussoren wrote: > > 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

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 > > wrote: >> >> >>> On Dec 6, 2016, at 10:36 AM, Ronald Oussoren >> > wrote: >>> >>> On 6 Dec 2016, at 19:19, Glyph Lef

Re: [Pythonmac-SIG] PyObjC 3.2.1 released

Hi Ronald, It's great to finally have precompiled wheels for PyObjC! Thanks so much! Cosimo ___ Pythonmac-SIG maillist - Pythonmac-SIG@python.org https://mail.python.org/mailman/listinfo/pythonmac-sig unsubscribe: https://mail.python.org/mailman/option

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 to PyPI (finally…). The major new feature in this >>> version is support fo

Re: [Pythonmac-SIG] PyObjC 3.2 released

> On Dec 6, 2016, at 8:59 AM, Ronald Oussoren wrote: > > Hi, > > I’ve pushed PyObjC 3.2 to PyPI (finally…). The major new feature in this > version is support for OSX 10.12 (Sierra) and the new APIs introduced in this > version of OSX. 🎉😃🎉 > There is also a backward incompatible change: the

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: > On 2016-09-13 19:33, Glyph Lefkowitz w

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 PM, Andrew Jaffe > wrote:

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 this way, but I'm not sure I > und

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-dev] PyObjC and macOS 10.12 (Sierra)

> On Oct 11, 2016, at 2:26 PM, Ronald Oussoren wrote: > > BTW. Has anyone experience with using LLDB on Sierra? I’m currently running > Sierra in a VM and for some reason LLDB doesn’t appear to work, in an SSH > session I cannot start programs at all and on the console a crashing bug in > the

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 >> > wrote: >>> >>> Aha! >>> >>> $ ls -lt /Library/Python/2.7/site-packages/ >>> total 0 >>> -rwxr-xr-x 1 root wheel 157

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 PM, Andrew Jaffe > wrote:

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: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-dev] PyObjC 3.2.1 released

> On 13 Dec 2016, at 04:02, Glyph Lefkowitz wrote: > > >> On Dec 12, 2016, at 1:25 AM, Ronald Oussoren > > wrote: >> >> 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 th

Re: [Pythonmac-SIG] PyObjC 3.2.1 released

Hi Ronald, On 12/12/2016 09:25, Ronald Oussoren wrote: 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 “i

[Pythonmac-SIG] PyObjC 3.2.1 released

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 “intel” installers (the default download option for the O

Re: [Pythonmac-SIG] PyObjC 3.2 released

> On 8 Dec 2016, at 23:55, Glyph Lefkowitz wrote: > >> >> On Dec 8, 2016, at 3:37 AM, Ronald Oussoren > > wrote: >> >> >>> On 8 Dec 2016, at 00:40, Glyph Lefkowitz >> > wrote: Last time I checked systems like Home

Re: [Pythonmac-SIG] PyObjC 3.2 released

> On 8 Dec 2016, at 00:40, Glyph Lefkowitz wrote: >> >> >> Last time I checked systems like Homebrew only build 64-bit binaries (on >> anything resembling modern hardware). It should be possible to support both >> i386/x86_64 python.org and homebrew using the same >> whe

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

> On 7 Dec 2016, at 01:49, Christopher Barker wrote: > > I haven't been involved for a while, but this gitHub org: > > https://github.com/MacPython > > Is doing a lot of wheel building, and I think they are using CIs to build and > test. > > Maybe they could ad

Re: [Pythonmac-SIG] PyObjC 3.2 released

> On 7 Dec 2016, at 00:28, Glyph Lefkowitz wrote: > > Was this intentionally off-list? (Feel free to forward my reply back to the > list if not). It wasn’t and I’ll continue the conversation on-list. > >> On Dec 6, 2016, at 2:31 PM, Ronald Oussoren > > wrote:

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

> On 6 Dec 2016, at 21:43, Glyph Lefkowitz wrote: > > >> Anyways, there may be a 3.2.1 release by the end of the week, I just noticed >> that building PyObjC on 10.12 doesn’t work when using python 2.7, I >> apparently only tested python 2.7 on older OSX releases :-( > > Thanks for saving me

Re: [Pythonmac-SIG] PyObjC 3.2 released

> On 6 Dec 2016, at 20:30, Glyph Lefkowitz wrote: > > >> 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 to PyPI

Re: [Pythonmac-SIG] PyObjC 3.2 released

> 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 to PyPI (finally…). The major new feature in this >> version is support for OSX 10.12 (Sierra) and the new APIs introduced in >> this version o

[Pythonmac-SIG] PyObjC 3.2 released

Hi, I’ve pushed PyObjC 3.2 to PyPI (finally…). The major new feature in this version is support for OSX 10.12 (Sierra) and the new APIs introduced in this version of OSX. There is also a backward incompatible change: the default method signature is calculated differently than before. This will

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

> On 25 Oct 2016, at 10:36, Andrew Jaffe wrote: > > On 12/10/2016 21:02, Ronald Oussoren wrote: > > > >> On 12 Oct 2016, at 21:09, Glyph Lefkowitz >> > wrote: > >> > >>> On Oct 12, 2016, at 11:49 AM, Andrew Jaffe >>> > wrote: > >>> >

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

On 12/10/2016 21:02, Ronald Oussoren wrote: > >> On 12 Oct 2016, at 21:09, Glyph Lefkowitz > > wrote: >> >>> On Oct 12, 2016, at 11:49 AM, Andrew Jaffe >> > wrote: >>> >>> Not me. If I understand correctly, Glyph -- who undoubtedly >>> un

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

> On 12 Oct 2016, at 08:08, Glyph Lefkowitz wrote: > > >> On Oct 11, 2016, at 2:26 PM, Ronald Oussoren > > wrote: >> >> BTW. Has anyone experience with using LLDB on Sierra? I’m currently running >> Sierra in a VM and for some reason LLDB doesn’t appear to work,

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

> On 12 Oct 2016, at 21:09, Glyph Lefkowitz wrote: > > >> 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

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

On 11/10/2016 22:26, Ronald Oussoren wrote: On 17 Sep 2016, at 19:59, Glyph Lefkowitz mailto:gl...@twistedmatrix.com>> wrote: On Sep 17, 2016, at 9:27 AM, Ned Deily mailto:n...@python.org>> wrote: On 2016-09-13 19:33, Glyph Lefkowitz wrote: On Sep 13, 2016, at 3:35 PM, Andrew Jaffe mailto:

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

> On 17 Sep 2016, at 19: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 PM, Andrew Jaffe >>> > wrote: Aha! $ ls -lt /Library/Pytho

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

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: On 2016-09-13 19:33, Glyph Lefkowitz wrote: On Sep 13, 2016, at 3:35 PM, Andrew Jaffe wrote: $ ls -lt /Library

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

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 PM, Andrew Jaffe mailto:a.h.ja...@gmail.com>> wrote: Aha! $ ls -lt /Library/Python/2.7/site-packages/ total 0 -rwxr-xr-x 1 root w

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

On 20/09/2016 20:54, Glyph Lefkowitz wrote: >> 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 PM, Andr

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

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 PM, Andrew Jaffe mailto:a.h.ja...@gmail.com>> wrote: Aha! $ ls -lt /Library/Python/2.7/site-packages/ total 0 -rwxr-xr-x 1 root w

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

On 2016-09-13 19:33, Glyph Lefkowitz wrote: >> 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

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

Hi, > On 13 Sep 2016, at 23:28, Glyph Lefkowitz wrote: > > >> 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 ar

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

OK, I’m still being dense: > On 13 Sep 2016, at 22:56, Jack Jansen wrote: > > It’s hardcoded in the Python executable, I’m afraid:-( > > Just tried “python -s -S -v”, and the Extras/lib/python is still in sys.path. > > That wasn’t a very smart move by the Apple engineers, I guess…. But this i

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

It’s hardcoded in the Python executable, I’m afraid:-( Just tried “python -s -S -v”, and the Extras/lib/python is still in sys.path. That wasn’t a very smart move by the Apple engineers, I guess…. What you could do (but this is getting rather hacky) is create a /Library/Python/2.7/site-packages

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

Hi, > On 13 Sep 2016, at 22:26, Jack Jansen wrote: > > You’re absolutely right (both on SIP and on > /Library/Frameworks/Python.framework probably being a python.org install), > sorry for the confusion. > > This seems to be due to the way Apple has done the “Extras” directory, and > adding

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

You’re absolutely right (both on SIP and on /Library/Frameworks/Python.framework probably being a python.org install), sorry for the confusion. This seems to be due to the way Apple has done the “Extras” directory, and adding things there to sys.path. See for example https://github.com/pypa/pi

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

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 that you’ve installed pyobjc a couple of OSX releases ago? And could i

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

Dear Chris and Glyph, > > On Sunday, September 11, 2016, Andrew Jaffe 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 lon

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

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: altgraph (0.10.2) - Latest: 0.12 [sdist] macholib (1.5.1) - Latest: 1.7 [sdist] m

  1   2   3   >