pyobjc-dev — CVS commit notices go here

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

[Glyph L. <gl...@tw...>]

> On Sep 11, 2016, at 3:12 AM, Andrew Jaffe <a.h...@gm...> wrote:
> 
> 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).

This is expected, and desired, even.  Don't install packages into your system Python.  Make a virtualenv and install pyobjc there, or do a `pip install --user`.  That should work fine.

-glyph

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

[Andrew J. <a.h...@gm...>]

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]
  modulegraph (0.10.4) - Latest: 0.12.1 [sdist]
  py2app (0.7.3) - Latest: 0.10 [sdist]
  pyobjc-core (2.5.1) - Latest: 3.1.1 [sdist]
  pyobjc-framework-Accounts (2.5.1) - Latest: 3.1.1 [sdist]
    <a bunch more pyobjc-framework-* (2.5.1) - Latest: 3.1.1 [sdist]>
  pyOpenSSL (0.13.1) - Latest: 16.1.0 [wheel]
  xattr (0.6.4) - Latest: 0.8.0 [sdist]

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

p.s. none of these issues arise with Python3/pip3, of course.

On 22/07/2016 14:46, Ronald Oussoren wrote:
> Hi,
>
> I’m slowly working my way through the SDK headers for macOS 10.12 during idle time at EuroPython2016, from the frameworks with small diffs to those with larger diffs.
>
> There are at the moment about 26 frameworks I haven’t looked at at all, and another 10 where I know I have to do some more work. The rest should have up to date metadata on my machine, but haven’t been tested on macOS 10.12 yet (and that won’t change until I get around to actually installing a VM running 10.12).
>
> All of this was done using the headers in the Xcode 8 beta 2, I haven’t looked at the incremental changes to the SDK in beta 3 yet (and likely won’t until I have made a pass through all frameworks).  That said, the diffs from beta 2 to later beta’s and the final release should be fairly small (he wrote hopefully).
>
> What needs to be done to get proper support for 10.12:
>
> * Finish updating the metadata.  I suspect that this is a couple of days work, I have worked may way through the diffs of a fairly large number of frameworks, but haven’t looked at the more complicated ones yet (such as Foundation and AppKit). Also, a fairly large subset of the frameworks I have looked at didn’t have any significant updates compared to 10.11 (but some of them still had large textual diffs due to restructuring of header files).
>
> * Install a 10.12 VM and run tests there. This will likely result in more work, there’s already a pull request about NSSecureCoder warnings on 10.12 that needs looking into and there’s bound to be more issues.
>
> * Do the build and test dance on older OSX releases.
>    The annoying bit for that: there’s a know issue with building on OSX 10.7, see issue #100. I haven’t been able to look into that yet
>    because I don’t have an VM with 10.7 on my laptop and haven’t been able to install 10.7 there yet. I probably have such a VM on
>    an external disk somewhere, but I’m not sure about that.
>
> When all that is done I can do a release that includes 10.12 support, with some luck around the time of the 10.12 release itself. I’ll definitely push the metadata updates to bitbucket once I’ve finished looking through the 10.12 SDK diffs.
>
> In the longer run I want to provide wheels for PyObjC, but that requires more work. In particular, I only want to do that after automating more of the release work because I’ve noticed that I’m already postponing doing new releases due to the amount of work and don’t want to make things worse in that regard.
>
> BTW. I’ll likely won’t work on metadata updates during the EP2016 sprints, my current plan is to keep the tradition of working on PEP 447 alive and try to actually get it accepted this year.
>
> Ronald
>
> PS. “A couple of days work” probably means that it will take me several calendar weeks to actually finish the work because I have limited time to work on this and don’t want to spent all that time on this rather tedious work.
>
> [#100]: https://bitbucket.org/ronaldoussoren/pyobjc/issues/100/cannot-find-interface-declaration-for
> ------------------------------------------------------------------------------
> What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
> patterns at an interface-level. Reveals which users, apps, and protocols are
> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> J-Flow, sFlow and other flows. Make informed decisions using capacity planning
> reports.http://sdm.link/zohodev2dev
> _______________________________________________
> Pyobjc-dev mailing list
> Pyo...@li...
> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev
>

Re: [Pyobjc-dev] Getting unexpected NSTaggedDate when pulling birthday properties from AddressBook?

[Ken T. <ke...@co...>]

On Aug 13, 2016, at 7:56 PM, Ramon Felciano <fel...@ya...> wrote:
> 
> I am testing out pyobjc to perform some scripting on the Mac address book. I'm trying to extend the provided exportBook.py script (https://pythonhosted.org/pyobjc/examples/AddressBook/Scripts/exportBook/index.html) to include several date fields such as birthdate. It looked to me like the introspection model should allow me to simply add in additional field names:
> 
> FIELD_NAMES=(
> 	('Last Name',  AddressBook.kABLastNameProperty),
> 	('First Name', AddressBook.kABFirstNameProperty),
> 	('E-mail',     AddressBook.kABEmailProperty),
> 	('Birthday',   AddressBook.kABBirthdayProperty),
> )
> 
> However the encodeField function returns an attribute error:
> -----------------
>     return value.encode('utf-8')
> AttributeError: '__NSTaggedDate' object has no attribute 'encode'
> -----------------
> 
> I'm not an Apple developer but some poking around on Google, StackExchange, etc suggests that NSTaggedDate isn't typically a returned data type, and the kABBirthdayProperty is supposed to be an NSDate property. This is making me wonder if something when wrong with my pyobjc installation -- can anyone suggest how best to debug this further?

First, NSTaggedDate is a private subclass of NSDate.  (In fact, it's a way of encoding a date into the pointer itself and the pointer doesn't point to a real, heap-allocated object.)

But the problem is not specific to NSTaggedDate.  It would happen with any NSDate:

$ python
Python 2.7.10 (default, Oct 23 2015, 19:19:21) 
[GCC 4.2.1 Compatible Apple LLVM 7.0.0 (clang-700.0.59.5)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> from Foundation import *
>>> d = NSDate.date()
>>> d.encode('utf-8')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
AttributeError: '__NSDate' object has no attribute 'encode'

The problem is that the sample script assumes all of the properties are string objects.  It's not correct for properties which are date objects or other kinds of objects.

You could check if the object is an NSDate and use an NSDateFormatter to build a string representation of the date object and then encode that into UTF-8.  Or, for a quick-and-dirty approach, you could just ask the object (whatever type it is) for its description() and then encode that (i.e. return value.description().encode('utf-8')).

Regards,
Ken

[Pyobjc-dev] Getting unexpected NSTaggedDate when pulling birthday properties from AddressBook?

[Ramon F. <fel...@ya...>]

Hello --

I am testing out pyobjc to perform some scripting on the Mac address book.
I'm trying to extend the provided exportBook.py script (
https://pythonhosted.org/pyobjc/examples/AddressBook/Scripts/exportBook/index.html)
to include several date fields such as birthdate. It looked to me like the
introspection model should allow me to simply add in additional field names:

FIELD_NAMES=(
('Last Name',  AddressBook.kABLastNameProperty),
('First Name', AddressBook.kABFirstNameProperty),
('E-mail',     AddressBook.kABEmailProperty),
('Birthday',   AddressBook.kABBirthdayProperty),
)

However the encodeField function returns an attribute error:
-----------------
    return value.encode('utf-8')
AttributeError: '__NSTaggedDate' object has no attribute 'encode'
-----------------

I'm not an Apple developer but some poking around on Google, StackExchange,
etc suggests that NSTaggedDate isn't typically a returned data type, and
the kABBirthdayProperty is supposed to be an NSDate property. This is
making me wonder if something when wrong with my pyobjc installation -- can
anyone suggest how best to debug this further?

Thanks in advance,

Ramon

Re: [Pyobjc-dev] compilation issues on Py3.5, os x 10.10.5

[Diez B. R. <de...@we...>]

Ok, I tried to locate the setup.py, but for the through pip download acquired pyobjc-core-3.1.1 (which I presume is the right one?), I don’t find the necessary code part.

I find similar ones, and could try patching these, but maybe it would be better if you told me what exactly you used, so I can recreate that environment more faithfully. 

Cheers,

Diez

> On 07 Aug 2016, at 13:16, Ronald Oussoren <ron...@ma...> wrote:
> 
>> 
>> On 07 Aug 2016, at 12:54, Ronald Oussoren <ron...@ma... <mailto:ron...@ma...>> wrote:
>> 
>>> 
>>> On 07 Aug 2016, at 11:22, Ronald Oussoren <ron...@ma... <mailto:ron...@ma...>> wrote:
>>> 
>>>> 
>>>> On 02 Aug 2016, at 12:13, Diez B. Roggisch <de...@we... <mailto:de...@we...>> wrote:
>>>> 
>>>> Hi,
>>>> 
>>>> back at work, I tried your below suggestion.
>>>> 
>>>> 
>>>> It falis with 
>>>> 
>>>>     running build_ext
>>>>     building 'CoreFoundation._inlines' extension
>>>>     creating build/temp.macosx-10.6-intel-3.5/Modules
>>>>     /usr/bin/clang -fno-strict-aliasing -Wsign-compare -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -arch i386 -arch x86_64 -g -Ibuild/temp.macosx-10.6-intel-3.5/pyobjc-include -I/Library/Frameworks/Python.framework/Versions/3.5/include/python3.5m -c Modules/_CoreFoundation_inlines.m -o build/temp.macosx-10.6-intel-3.5/Modules/_CoreFoundation_inlines.o -DPyObjC_BUILD_RELEASE=1010
>>>>     In file included from Modules/_CoreFoundation_inlines.m:2:
>>>>     /Library/Frameworks/Python.framework/Versions/3.5/include/python3.5m/Python.h:25:10: fatal error: 'stdio.h' file not found
>>>>     #include <stdio.h>
>>>>              ^
>>>>     1 error generated.
>>>>     error: command '/usr/bin/clang' failed with exit status 1
>>> 
>>> That’s annoying. I don’t understand why the build does not use the SDK inside the Xcode.app package on your machine.
>> 
>> I might be onto something. Did you install the command-line tools package? I installed both Xcode 7.2 and the command-line tools (using “xcode-select —install”) and that gives me the same error.  The same VM did work properly before I installed the command-line tools.
>> 
>> I don’t know yet how to work around this problem, the compiler command-lines are the same on both machines. 
> 
> The patch below fixes the issue for me. I haven’t checked yet if this does the right thing on any system other than one running Xcode 7.2 with the command tools installed.
> 
> --- pyobjc_setup.py.orig	2016-08-07 04:03:55.000000000 -0700
> +++ pyobjc_setup.py	2016-08-07 04:13:22.000000000 -0700
> @@ -284,6 +284,9 @@
>      except (ImportError, NameError):
>          pass
>  
> +
> +
> +
>      cc = oldcc = get_config_var('CC').split()[0]
>      cc = _find_executable(cc)
>      if cc is not None and os.path.basename(cc).startswith('gcc'):
> @@ -377,6 +380,16 @@
>      if 'clang' in get_config_var('CC'):
>          cflags.append('-Wno-deprecated-declarations')
>  
> +    CFLAGS = get_config_var('CFLAGS')
> +    if '-isysroot' not in CFLAGS and os.path.exists('/usr/include/stdio.h'):
> +        # We're likely on a system with de Xcode Command Line Tools.
> +        # Explicitly use an SDK
> +        data = os.popen('xcodebuild -version -sdk macosx Path').read()
> +        data = data.strip()
> +        if data:
> +            cflags.append('-isysroot')
> +            cflags.append(data)
> +
>      #if os_level != '10.4':
>      #    if os.path.exists('/usr/include/stdio.h'):
>      #        # only tweak the SDK when using the command-line tools
> 
>> 
>> Ronald
>> 
>> 
>>> 
>>> Ronald
>>> 
>>>> 
>>>> Cheers,
>>>> 
>>>> Diez
>>>> 
>>>>> On 30 Jul 2016, at 10:01, Ronald Oussoren <ron...@ma... <mailto:ron...@ma...>> wrote:
>>>>> 
>>>>>> 
>>>>>> On 30 Jul 2016, at 09:44, Ronald Oussoren <ron...@ma... <mailto:ron...@ma...>> wrote:
>>>>>> 
>>>>>>> 
>>>>>>> On 28 Jul 2016, at 15:43, Diez B. Roggisch <de...@we... <mailto:de...@we...>> wrote:
>>>>>>> 
>>>>>>> Hi,
>>>>>>> 
>>>>>>> I get the problem quoted below after trying to install pyobjc on my 10.10.5 System, Xcode version 7.2 into a vanilla Python3.5
>>>>>>> 
>>>>>>> Googling resulted in http://stackoverflow.com/questions/37525929/python-pyobjc-idtopythonprotocolnsurlsessionstreamdelegate-error <http://stackoverflow.com/questions/37525929/python-pyobjc-idtopythonprotocolnsurlsessionstreamdelegate-error>, which again on a vanilla Python 3.5 succeeds installing, but gives the second error below.
>>>>>>> 
>>>>>>> Any suggestions are welcome.
>>>>>> 
>>>>>> For some reason PyObjC thinks it is building with the OSX 10.10 SDK, while it is building with an older SDK. Because of this it tries to reference a symbol that isn’t present in the SDK that is used.   The “-isysroot /“ flag in the output below explains the behavior, setup.py cannot deduce the SDK used from the sysroot parameter and therefore assumes the SDK version matches the OSX version.
>>>>> 
>>>>> I just noticed some old code in the setup.py files for PyObjC that could cause this error. I’ll be testing on older OSX releases once I finish my work on 10.12 support and will try to remove or fix that old code when I do so.
>>>>> 
>>>>> Could you check if you have a file named “/usr/include/stdio.h” on your system? If so, please try building without this file (basically: move or rename it, then build PyObjC, then restore the file). 
>>>>> 
>>>>> Ronald
>>>> 
>>>> ------------------------------------------------------------------------------
>>>> _______________________________________________
>>>> Pyobjc-dev mailing list
>>>> Pyo...@li... <mailto:Pyo...@li...>
>>>> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev <https://lists.sourceforge.net/lists/listinfo/pyobjc-dev>
>>> 
>>> ------------------------------------------------------------------------------
>>> _______________________________________________
>>> Pyobjc-dev mailing list
>>> Pyo...@li... <mailto:Pyo...@li...>
>>> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev <https://lists.sourceforge.net/lists/listinfo/pyobjc-dev>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> Pyobjc-dev mailing list
>> Pyo...@li... <mailto:Pyo...@li...>
>> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev <https://lists.sourceforge.net/lists/listinfo/pyobjc-dev>

Re: [Pyobjc-dev] compilation issues on Py3.5, os x 10.10.5

[Diez B. R. <de...@we...>]

Hi Ronald,


>> I might be onto something. Did you install the command-line tools package? I installed both Xcode 7.2 and the command-line tools (using “xcode-select —install”) and that gives me the same error.  The same VM did work properly before I installed the command-line tools.
>> 
>> I don’t know yet how to work around this problem, the compiler command-lines are the same on both machines. 


I did install commandline tools, as a large part of daily development comprises C++ work.

I will try & use your patch, and give feedback on the results soon.

Cheers,

Diez



> 
> The patch below fixes the issue for me. I haven’t checked yet if this does the right thing on any system other than one running Xcode 7.2 with the command tools installed.
> 
> --- pyobjc_setup.py.orig	2016-08-07 04:03:55.000000000 -0700
> +++ pyobjc_setup.py	2016-08-07 04:13:22.000000000 -0700
> @@ -284,6 +284,9 @@
>      except (ImportError, NameError):
>          pass
>  
> +
> +
> +
>      cc = oldcc = get_config_var('CC').split()[0]
>      cc = _find_executable(cc)
>      if cc is not None and os.path.basename(cc).startswith('gcc'):
> @@ -377,6 +380,16 @@
>      if 'clang' in get_config_var('CC'):
>          cflags.append('-Wno-deprecated-declarations')
>  
> +    CFLAGS = get_config_var('CFLAGS')
> +    if '-isysroot' not in CFLAGS and os.path.exists('/usr/include/stdio.h'):
> +        # We're likely on a system with de Xcode Command Line Tools.
> +        # Explicitly use an SDK
> +        data = os.popen('xcodebuild -version -sdk macosx Path').read()
> +        data = data.strip()
> +        if data:
> +            cflags.append('-isysroot')
> +            cflags.append(data)
> +
>      #if os_level != '10.4':
>      #    if os.path.exists('/usr/include/stdio.h'):
>      #        # only tweak the SDK when using the command-line tools
> 
>> 
>> Ronald
>> 
>> 
>>> 
>>> Ronald
>>> 
>>>> 
>>>> Cheers,
>>>> 
>>>> Diez
>>>> 
>>>>> On 30 Jul 2016, at 10:01, Ronald Oussoren <ron...@ma... <mailto:ron...@ma...>> wrote:
>>>>> 
>>>>>> 
>>>>>> On 30 Jul 2016, at 09:44, Ronald Oussoren <ron...@ma... <mailto:ron...@ma...>> wrote:
>>>>>> 
>>>>>>> 
>>>>>>> On 28 Jul 2016, at 15:43, Diez B. Roggisch <de...@we... <mailto:de...@we...>> wrote:
>>>>>>> 
>>>>>>> Hi,
>>>>>>> 
>>>>>>> I get the problem quoted below after trying to install pyobjc on my 10.10.5 System, Xcode version 7.2 into a vanilla Python3.5
>>>>>>> 
>>>>>>> Googling resulted in http://stackoverflow.com/questions/37525929/python-pyobjc-idtopythonprotocolnsurlsessionstreamdelegate-error <http://stackoverflow.com/questions/37525929/python-pyobjc-idtopythonprotocolnsurlsessionstreamdelegate-error>, which again on a vanilla Python 3.5 succeeds installing, but gives the second error below.
>>>>>>> 
>>>>>>> Any suggestions are welcome.
>>>>>> 
>>>>>> For some reason PyObjC thinks it is building with the OSX 10.10 SDK, while it is building with an older SDK. Because of this it tries to reference a symbol that isn’t present in the SDK that is used.   The “-isysroot /“ flag in the output below explains the behavior, setup.py cannot deduce the SDK used from the sysroot parameter and therefore assumes the SDK version matches the OSX version.
>>>>> 
>>>>> I just noticed some old code in the setup.py files for PyObjC that could cause this error. I’ll be testing on older OSX releases once I finish my work on 10.12 support and will try to remove or fix that old code when I do so.
>>>>> 
>>>>> Could you check if you have a file named “/usr/include/stdio.h” on your system? If so, please try building without this file (basically: move or rename it, then build PyObjC, then restore the file). 
>>>>> 
>>>>> Ronald
>>>> 
>>>> ------------------------------------------------------------------------------
>>>> _______________________________________________
>>>> Pyobjc-dev mailing list
>>>> Pyo...@li... <mailto:Pyo...@li...>
>>>> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev <https://lists.sourceforge.net/lists/listinfo/pyobjc-dev>
>>> 
>>> ------------------------------------------------------------------------------
>>> _______________________________________________
>>> Pyobjc-dev mailing list
>>> Pyo...@li... <mailto:Pyo...@li...>
>>> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev <https://lists.sourceforge.net/lists/listinfo/pyobjc-dev>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> Pyobjc-dev mailing list
>> Pyo...@li... <mailto:Pyo...@li...>
>> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev <https://lists.sourceforge.net/lists/listinfo/pyobjc-dev>
> ------------------------------------------------------------------------------
> _______________________________________________
> Pyobjc-dev mailing list
> Pyo...@li... <mailto:Pyo...@li...>
> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev <https://lists.sourceforge.net/lists/listinfo/pyobjc-dev>

Re: [Pyobjc-dev] compilation issues on Py3.5, os x 10.10.5

[Ronald O. <ron...@ma...>]

> On 07 Aug 2016, at 12:54, Ronald Oussoren <ron...@ma...> wrote:
> 
>> 
>> On 07 Aug 2016, at 11:22, Ronald Oussoren <ron...@ma... <mailto:ron...@ma...>> wrote:
>> 
>>> 
>>> On 02 Aug 2016, at 12:13, Diez B. Roggisch <de...@we... <mailto:de...@we...>> wrote:
>>> 
>>> Hi,
>>> 
>>> back at work, I tried your below suggestion.
>>> 
>>> 
>>> It falis with 
>>> 
>>>     running build_ext
>>>     building 'CoreFoundation._inlines' extension
>>>     creating build/temp.macosx-10.6-intel-3.5/Modules
>>>     /usr/bin/clang -fno-strict-aliasing -Wsign-compare -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -arch i386 -arch x86_64 -g -Ibuild/temp.macosx-10.6-intel-3.5/pyobjc-include -I/Library/Frameworks/Python.framework/Versions/3.5/include/python3.5m -c Modules/_CoreFoundation_inlines.m -o build/temp.macosx-10.6-intel-3.5/Modules/_CoreFoundation_inlines.o -DPyObjC_BUILD_RELEASE=1010
>>>     In file included from Modules/_CoreFoundation_inlines.m:2:
>>>     /Library/Frameworks/Python.framework/Versions/3.5/include/python3.5m/Python.h:25:10: fatal error: 'stdio.h' file not found
>>>     #include <stdio.h>
>>>              ^
>>>     1 error generated.
>>>     error: command '/usr/bin/clang' failed with exit status 1
>> 
>> That’s annoying. I don’t understand why the build does not use the SDK inside the Xcode.app package on your machine.
> 
> I might be onto something. Did you install the command-line tools package? I installed both Xcode 7.2 and the command-line tools (using “xcode-select —install”) and that gives me the same error.  The same VM did work properly before I installed the command-line tools.
> 
> I don’t know yet how to work around this problem, the compiler command-lines are the same on both machines. 

The patch below fixes the issue for me. I haven’t checked yet if this does the right thing on any system other than one running Xcode 7.2 with the command tools installed.

--- pyobjc_setup.py.orig	2016-08-07 04:03:55.000000000 -0700
+++ pyobjc_setup.py	2016-08-07 04:13:22.000000000 -0700
@@ -284,6 +284,9 @@
     except (ImportError, NameError):
         pass
 
+
+
+
     cc = oldcc = get_config_var('CC').split()[0]
     cc = _find_executable(cc)
     if cc is not None and os.path.basename(cc).startswith('gcc'):
@@ -377,6 +380,16 @@
     if 'clang' in get_config_var('CC'):
         cflags.append('-Wno-deprecated-declarations')
 
+    CFLAGS = get_config_var('CFLAGS')
+    if '-isysroot' not in CFLAGS and os.path.exists('/usr/include/stdio.h'):
+        # We're likely on a system with de Xcode Command Line Tools.
+        # Explicitly use an SDK
+        data = os.popen('xcodebuild -version -sdk macosx Path').read()
+        data = data.strip()
+        if data:
+            cflags.append('-isysroot')
+            cflags.append(data)
+
     #if os_level != '10.4':
     #    if os.path.exists('/usr/include/stdio.h'):
     #        # only tweak the SDK when using the command-line tools

> 
> Ronald
> 
> 
>> 
>> Ronald
>> 
>>> 
>>> Cheers,
>>> 
>>> Diez
>>> 
>>>> On 30 Jul 2016, at 10:01, Ronald Oussoren <ron...@ma... <mailto:ron...@ma...>> wrote:
>>>> 
>>>>> 
>>>>> On 30 Jul 2016, at 09:44, Ronald Oussoren <ron...@ma... <mailto:ron...@ma...>> wrote:
>>>>> 
>>>>>> 
>>>>>> On 28 Jul 2016, at 15:43, Diez B. Roggisch <de...@we... <mailto:de...@we...>> wrote:
>>>>>> 
>>>>>> Hi,
>>>>>> 
>>>>>> I get the problem quoted below after trying to install pyobjc on my 10.10.5 System, Xcode version 7.2 into a vanilla Python3.5
>>>>>> 
>>>>>> Googling resulted in http://stackoverflow.com/questions/37525929/python-pyobjc-idtopythonprotocolnsurlsessionstreamdelegate-error <http://stackoverflow.com/questions/37525929/python-pyobjc-idtopythonprotocolnsurlsessionstreamdelegate-error>, which again on a vanilla Python 3.5 succeeds installing, but gives the second error below.
>>>>>> 
>>>>>> Any suggestions are welcome.
>>>>> 
>>>>> For some reason PyObjC thinks it is building with the OSX 10.10 SDK, while it is building with an older SDK. Because of this it tries to reference a symbol that isn’t present in the SDK that is used.   The “-isysroot /“ flag in the output below explains the behavior, setup.py cannot deduce the SDK used from the sysroot parameter and therefore assumes the SDK version matches the OSX version.
>>>> 
>>>> I just noticed some old code in the setup.py files for PyObjC that could cause this error. I’ll be testing on older OSX releases once I finish my work on 10.12 support and will try to remove or fix that old code when I do so.
>>>> 
>>>> Could you check if you have a file named “/usr/include/stdio.h” on your system? If so, please try building without this file (basically: move or rename it, then build PyObjC, then restore the file). 
>>>> 
>>>> Ronald
>>> 
>>> ------------------------------------------------------------------------------
>>> _______________________________________________
>>> Pyobjc-dev mailing list
>>> Pyo...@li... <mailto:Pyo...@li...>
>>> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev <https://lists.sourceforge.net/lists/listinfo/pyobjc-dev>
>> 
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> Pyobjc-dev mailing list
>> Pyo...@li... <mailto:Pyo...@li...>
>> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev <https://lists.sourceforge.net/lists/listinfo/pyobjc-dev>
> ------------------------------------------------------------------------------
> _______________________________________________
> Pyobjc-dev mailing list
> Pyo...@li... <mailto:Pyo...@li...>
> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev <https://lists.sourceforge.net/lists/listinfo/pyobjc-dev>

Re: [Pyobjc-dev] compilation issues on Py3.5, os x 10.10.5

[Ronald O. <ron...@ma...>]

> On 07 Aug 2016, at 11:22, Ronald Oussoren <ron...@ma...> wrote:
> 
>> 
>> On 02 Aug 2016, at 12:13, Diez B. Roggisch <de...@we... <mailto:de...@we...>> wrote:
>> 
>> Hi,
>> 
>> back at work, I tried your below suggestion.
>> 
>> 
>> It falis with 
>> 
>>     running build_ext
>>     building 'CoreFoundation._inlines' extension
>>     creating build/temp.macosx-10.6-intel-3.5/Modules
>>     /usr/bin/clang -fno-strict-aliasing -Wsign-compare -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -arch i386 -arch x86_64 -g -Ibuild/temp.macosx-10.6-intel-3.5/pyobjc-include -I/Library/Frameworks/Python.framework/Versions/3.5/include/python3.5m -c Modules/_CoreFoundation_inlines.m -o build/temp.macosx-10.6-intel-3.5/Modules/_CoreFoundation_inlines.o -DPyObjC_BUILD_RELEASE=1010
>>     In file included from Modules/_CoreFoundation_inlines.m:2:
>>     /Library/Frameworks/Python.framework/Versions/3.5/include/python3.5m/Python.h:25:10: fatal error: 'stdio.h' file not found
>>     #include <stdio.h>
>>              ^
>>     1 error generated.
>>     error: command '/usr/bin/clang' failed with exit status 1
> 
> That’s annoying. I don’t understand why the build does not use the SDK inside the Xcode.app package on your machine.

I might be onto something. Did you install the command-line tools package? I installed both Xcode 7.2 and the command-line tools (using “xcode-select —install”) and that gives me the same error.  The same VM did work properly before I installed the command-line tools.

I don’t know yet how to work around this problem, the compiler command-lines are the same on both machines. 

Ronald


> 
> Ronald
> 
>> 
>> Cheers,
>> 
>> Diez
>> 
>>> On 30 Jul 2016, at 10:01, Ronald Oussoren <ron...@ma... <mailto:ron...@ma...>> wrote:
>>> 
>>>> 
>>>> On 30 Jul 2016, at 09:44, Ronald Oussoren <ron...@ma... <mailto:ron...@ma...>> wrote:
>>>> 
>>>>> 
>>>>> On 28 Jul 2016, at 15:43, Diez B. Roggisch <de...@we... <mailto:de...@we...>> wrote:
>>>>> 
>>>>> Hi,
>>>>> 
>>>>> I get the problem quoted below after trying to install pyobjc on my 10.10.5 System, Xcode version 7.2 into a vanilla Python3.5
>>>>> 
>>>>> Googling resulted in http://stackoverflow.com/questions/37525929/python-pyobjc-idtopythonprotocolnsurlsessionstreamdelegate-error <http://stackoverflow.com/questions/37525929/python-pyobjc-idtopythonprotocolnsurlsessionstreamdelegate-error>, which again on a vanilla Python 3.5 succeeds installing, but gives the second error below.
>>>>> 
>>>>> Any suggestions are welcome.
>>>> 
>>>> For some reason PyObjC thinks it is building with the OSX 10.10 SDK, while it is building with an older SDK. Because of this it tries to reference a symbol that isn’t present in the SDK that is used.   The “-isysroot /“ flag in the output below explains the behavior, setup.py cannot deduce the SDK used from the sysroot parameter and therefore assumes the SDK version matches the OSX version.
>>> 
>>> I just noticed some old code in the setup.py files for PyObjC that could cause this error. I’ll be testing on older OSX releases once I finish my work on 10.12 support and will try to remove or fix that old code when I do so.
>>> 
>>> Could you check if you have a file named “/usr/include/stdio.h” on your system? If so, please try building without this file (basically: move or rename it, then build PyObjC, then restore the file). 
>>> 
>>> Ronald
>> 
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> Pyobjc-dev mailing list
>> Pyo...@li... <mailto:Pyo...@li...>
>> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev
> 
> ------------------------------------------------------------------------------
> _______________________________________________
> Pyobjc-dev mailing list
> Pyo...@li... <mailto:Pyo...@li...>
> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev <https://lists.sourceforge.net/lists/listinfo/pyobjc-dev>

Re: [Pyobjc-dev] compilation issues on Py3.5, os x 10.10.5

[Ronald O. <ron...@ma...>]

> On 02 Aug 2016, at 12:13, Diez B. Roggisch <de...@we...> wrote:
> 
> Hi,
> 
> back at work, I tried your below suggestion.
> 
> 
> It falis with 
> 
>     running build_ext
>     building 'CoreFoundation._inlines' extension
>     creating build/temp.macosx-10.6-intel-3.5/Modules
>     /usr/bin/clang -fno-strict-aliasing -Wsign-compare -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -arch i386 -arch x86_64 -g -Ibuild/temp.macosx-10.6-intel-3.5/pyobjc-include -I/Library/Frameworks/Python.framework/Versions/3.5/include/python3.5m -c Modules/_CoreFoundation_inlines.m -o build/temp.macosx-10.6-intel-3.5/Modules/_CoreFoundation_inlines.o -DPyObjC_BUILD_RELEASE=1010
>     In file included from Modules/_CoreFoundation_inlines.m:2:
>     /Library/Frameworks/Python.framework/Versions/3.5/include/python3.5m/Python.h:25:10: fatal error: 'stdio.h' file not found
>     #include <stdio.h>
>              ^
>     1 error generated.
>     error: command '/usr/bin/clang' failed with exit status 1

That’s annoying. I don’t understand why the build does not use the SDK inside the Xcode.app package on your machine.

Ronald

> 
> Cheers,
> 
> Diez
> 
>> On 30 Jul 2016, at 10:01, Ronald Oussoren <ron...@ma... <mailto:ron...@ma...>> wrote:
>> 
>>> 
>>> On 30 Jul 2016, at 09:44, Ronald Oussoren <ron...@ma... <mailto:ron...@ma...>> wrote:
>>> 
>>>> 
>>>> On 28 Jul 2016, at 15:43, Diez B. Roggisch <de...@we... <mailto:de...@we...>> wrote:
>>>> 
>>>> Hi,
>>>> 
>>>> I get the problem quoted below after trying to install pyobjc on my 10.10.5 System, Xcode version 7.2 into a vanilla Python3.5
>>>> 
>>>> Googling resulted in http://stackoverflow.com/questions/37525929/python-pyobjc-idtopythonprotocolnsurlsessionstreamdelegate-error <http://stackoverflow.com/questions/37525929/python-pyobjc-idtopythonprotocolnsurlsessionstreamdelegate-error>, which again on a vanilla Python 3.5 succeeds installing, but gives the second error below.
>>>> 
>>>> Any suggestions are welcome.
>>> 
>>> For some reason PyObjC thinks it is building with the OSX 10.10 SDK, while it is building with an older SDK. Because of this it tries to reference a symbol that isn’t present in the SDK that is used.   The “-isysroot /“ flag in the output below explains the behavior, setup.py cannot deduce the SDK used from the sysroot parameter and therefore assumes the SDK version matches the OSX version.
>> 
>> I just noticed some old code in the setup.py files for PyObjC that could cause this error. I’ll be testing on older OSX releases once I finish my work on 10.12 support and will try to remove or fix that old code when I do so.
>> 
>> Could you check if you have a file named “/usr/include/stdio.h” on your system? If so, please try building without this file (basically: move or rename it, then build PyObjC, then restore the file). 
>> 
>> Ronald
> 
> ------------------------------------------------------------------------------
> _______________________________________________
> Pyobjc-dev mailing list
> Pyo...@li...
> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev

Re: [Pyobjc-dev] compilation issues on Py3.5, os x 10.10.5

[Diez B. R. <de...@we...>]

Hi,

back at work, I tried your below suggestion.


It falis with 

    running build_ext
    building 'CoreFoundation._inlines' extension
    creating build/temp.macosx-10.6-intel-3.5/Modules
    /usr/bin/clang -fno-strict-aliasing -Wsign-compare -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -arch i386 -arch x86_64 -g -Ibuild/temp.macosx-10.6-intel-3.5/pyobjc-include -I/Library/Frameworks/Python.framework/Versions/3.5/include/python3.5m -c Modules/_CoreFoundation_inlines.m -o build/temp.macosx-10.6-intel-3.5/Modules/_CoreFoundation_inlines.o -DPyObjC_BUILD_RELEASE=1010
    In file included from Modules/_CoreFoundation_inlines.m:2:
    /Library/Frameworks/Python.framework/Versions/3.5/include/python3.5m/Python.h:25:10: fatal error: 'stdio.h' file not found
    #include <stdio.h>
             ^
    1 error generated.
    error: command '/usr/bin/clang' failed with exit status 1

Cheers,

Diez

> On 30 Jul 2016, at 10:01, Ronald Oussoren <ron...@ma...> wrote:
> 
>> 
>> On 30 Jul 2016, at 09:44, Ronald Oussoren <ron...@ma... <mailto:ron...@ma...>> wrote:
>> 
>>> 
>>> On 28 Jul 2016, at 15:43, Diez B. Roggisch <de...@we... <mailto:de...@we...>> wrote:
>>> 
>>> Hi,
>>> 
>>> I get the problem quoted below after trying to install pyobjc on my 10.10.5 System, Xcode version 7.2 into a vanilla Python3.5
>>> 
>>> Googling resulted in http://stackoverflow.com/questions/37525929/python-pyobjc-idtopythonprotocolnsurlsessionstreamdelegate-error <http://stackoverflow.com/questions/37525929/python-pyobjc-idtopythonprotocolnsurlsessionstreamdelegate-error>, which again on a vanilla Python 3.5 succeeds installing, but gives the second error below.
>>> 
>>> Any suggestions are welcome.
>> 
>> For some reason PyObjC thinks it is building with the OSX 10.10 SDK, while it is building with an older SDK. Because of this it tries to reference a symbol that isn’t present in the SDK that is used.   The “-isysroot /“ flag in the output below explains the behavior, setup.py cannot deduce the SDK used from the sysroot parameter and therefore assumes the SDK version matches the OSX version.
> 
> I just noticed some old code in the setup.py files for PyObjC that could cause this error. I’ll be testing on older OSX releases once I finish my work on 10.12 support and will try to remove or fix that old code when I do so.
> 
> Could you check if you have a file named “/usr/include/stdio.h” on your system? If so, please try building without this file (basically: move or rename it, then build PyObjC, then restore the file). 
> 
> Ronald

Re: [Pyobjc-dev] compilation issues on Py3.5, os x 10.10.5

[Diez B. R. <de...@we...>]

Hi Ronald,

> For some reason PyObjC thinks it is building with the OSX 10.10 SDK, while it is building with an older SDK. Because of this it tries to reference a symbol that isn’t present in the SDK that is used.   The “-isysroot /“ flag in the output below explains the behavior, setup.py cannot deduce the SDK used from the sysroot parameter and therefore assumes the SDK version matches the OSX version.
> 
> Are you using the 3.5 installer from www.python.org <http://www.python.org/>?

Yes, I  do. Wiped & re-installed explicitly before attempting to install.

I will try your suggestion about /usr/include/stdio.h on monday (it’s my work-machine), and report back.

Cheers,

Diez

Re: [Pyobjc-dev] compilation issues on Py3.5, os x 10.10.5

[Ronald O. <ron...@ma...>]

> On 30 Jul 2016, at 09:44, Ronald Oussoren <ron...@ma...> wrote:
> 
>> 
>> On 28 Jul 2016, at 15:43, Diez B. Roggisch <de...@we... <mailto:de...@we...>> wrote:
>> 
>> Hi,
>> 
>> I get the problem quoted below after trying to install pyobjc on my 10.10.5 System, Xcode version 7.2 into a vanilla Python3.5
>> 
>> Googling resulted in http://stackoverflow.com/questions/37525929/python-pyobjc-idtopythonprotocolnsurlsessionstreamdelegate-error <http://stackoverflow.com/questions/37525929/python-pyobjc-idtopythonprotocolnsurlsessionstreamdelegate-error>, which again on a vanilla Python 3.5 succeeds installing, but gives the second error below.
>> 
>> Any suggestions are welcome.
> 
> For some reason PyObjC thinks it is building with the OSX 10.10 SDK, while it is building with an older SDK. Because of this it tries to reference a symbol that isn’t present in the SDK that is used.   The “-isysroot /“ flag in the output below explains the behavior, setup.py cannot deduce the SDK used from the sysroot parameter and therefore assumes the SDK version matches the OSX version.

I just noticed some old code in the setup.py files for PyObjC that could cause this error. I’ll be testing on older OSX releases once I finish my work on 10.12 support and will try to remove or fix that old code when I do so.

Could you check if you have a file named “/usr/include/stdio.h” on your system? If so, please try building without this file (basically: move or rename it, then build PyObjC, then restore the file). 

Ronald

Re: [Pyobjc-dev] compilation issues on Py3.5, os x 10.10.5

[Ronald O. <ron...@ma...>]

> On 28 Jul 2016, at 15:43, Diez B. Roggisch <de...@we...> wrote:
> 
> Hi,
> 
> I get the problem quoted below after trying to install pyobjc on my 10.10.5 System, Xcode version 7.2 into a vanilla Python3.5
> 
> Googling resulted in http://stackoverflow.com/questions/37525929/python-pyobjc-idtopythonprotocolnsurlsessionstreamdelegate-error <http://stackoverflow.com/questions/37525929/python-pyobjc-idtopythonprotocolnsurlsessionstreamdelegate-error>, which again on a vanilla Python 3.5 succeeds installing, but gives the second error below.
> 
> Any suggestions are welcome.

For some reason PyObjC thinks it is building with the OSX 10.10 SDK, while it is building with an older SDK. Because of this it tries to reference a symbol that isn’t present in the SDK that is used.   The “-isysroot /“ flag in the output below explains the behavior, setup.py cannot deduce the SDK used from the sysroot parameter and therefore assumes the SDK version matches the OSX version.

Are you using the 3.5 installer from www.python.org?

Ronald


> 
> Cheers,
> 
> Diez
> 
> 
> Error message for normal install:
> 
>     running build_ext
>     building 'CoreFoundation._inlines' extension
>     creating build/temp.macosx-10.6-intel-3.5/Modules
>     /usr/bin/clang -fno-strict-aliasing -Wsign-compare -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -arch i386 -arch x86_64 -g -Ibuild/temp.macosx-10.6-intel-3.5/pyobjc-include -I/Library/Frameworks/Python.framework/Versions/3.5/include/python3.5m -c Modules/_CoreFoundation_inlines.m -o build/temp.macosx-10.6-intel-3.5/Modules/_CoreFoundation_inlines.o -DPyObjC_BUILD_RELEASE=1010 -isysroot /
>     /usr/bin/clang -bundle -undefined dynamic_lookup -arch i386 -arch x86_64 -g build/temp.macosx-10.6-intel-3.5/Modules/_CoreFoundation_inlines.o -o build/lib.macosx-10.6-intel-3.5/CoreFoundation/_inlines.cpython-35m-darwin.so -framework CoreFoundation -isysroot /
>     building 'CoreFoundation._CoreFoundation' extension
>     /usr/bin/clang -fno-strict-aliasing -Wsign-compare -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -arch i386 -arch x86_64 -g -Ibuild/temp.macosx-10.6-intel-3.5/pyobjc-include -I/Library/Frameworks/Python.framework/Versions/3.5/include/python3.5m -c Modules/_CoreFoundation.m -o build/temp.macosx-10.6-intel-3.5/Modules/_CoreFoundation.o -DPyObjC_BUILD_RELEASE=1010 -isysroot /
>     /usr/bin/clang -bundle -undefined dynamic_lookup -arch i386 -arch x86_64 -g build/temp.macosx-10.6-intel-3.5/Modules/_CoreFoundation.o -o build/lib.macosx-10.6-intel-3.5/CoreFoundation/_CoreFoundation.cpython-35m-darwin.so -framework CoreFoundation -isysroot /
>     building 'Foundation._inlines' extension
>     /usr/bin/clang -fno-strict-aliasing -Wsign-compare -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -arch i386 -arch x86_64 -g -Ibuild/temp.macosx-10.6-intel-3.5/pyobjc-include -I/Library/Frameworks/Python.framework/Versions/3.5/include/python3.5m -c Modules/_Foundation_inlines.m -o build/temp.macosx-10.6-intel-3.5/Modules/_Foundation_inlines.o -DPyObjC_BUILD_RELEASE=1010 -isysroot /
>     /usr/bin/clang -bundle -undefined dynamic_lookup -arch i386 -arch x86_64 -g build/temp.macosx-10.6-intel-3.5/Modules/_Foundation_inlines.o -o build/lib.macosx-10.6-intel-3.5/Foundation/_inlines.cpython-35m-darwin.so -framework Foundation -isysroot /
>     building 'Foundation._Foundation' extension
>     /usr/bin/clang -fno-strict-aliasing -Wsign-compare -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -arch i386 -arch x86_64 -g -Ibuild/temp.macosx-10.6-intel-3.5/pyobjc-include -I/Library/Frameworks/Python.framework/Versions/3.5/include/python3.5m -c Modules/_Foundation.m -o build/temp.macosx-10.6-intel-3.5/Modules/_Foundation.o -DPyObjC_BUILD_RELEASE=1010 -isysroot /
>     In file included from Modules/_Foundation.m:15:
>     Modules/_Foundation_protocols.m:14:28: error: cannot find protocol declaration for 'NSProgressReporting'
>         p = PyObjC_IdToPython(@protocol(NSProgressReporting)); Py_XDECREF(p);
>                                ^
>     Modules/_Foundation_protocols.m:15:28: error: cannot find protocol declaration for 'NSURLSessionStreamDelegate'
>         p = PyObjC_IdToPython(@protocol(NSURLSessionStreamDelegate)); Py_XDECREF(p);
>                                ^
>     2 errors generated.
>     error: command '/usr/bin/clang' failed with exit status 1
> 
> 
> 
> Error message for 3.0.4:
> 
>  28 15:42:29 client2087.office.ableton.com <http://client2087.office.ableton.com/> NotoriousWIG[27812] <Notice>: 2016-07-28 15:42:29.169 NotoriousWIG[27812:4040159] NotoriousWIG Error
> Jul 28 15:42:31 client2087.office.ableton.com <http://client2087.office.ableton.com/> NotoriousWIG[27812] <Notice>: Traceback (most recent call last):
> Jul 28 15:42:31 client2087.office.ableton.com <http://client2087.office.ableton.com/> NotoriousWIG[27812] <Notice>:   File "/Users/dir/projects/ableton/notorious-wig/dist/NotoriousWIG.app/Contents/Resources/__boot__.py", line 102, in <module>
> Jul 28 15:42:31 client2087.office.ableton.com <http://client2087.office.ableton.com/> NotoriousWIG[27812] <Notice>:     _run()
> Jul 28 15:42:31 client2087.office.ableton.com <http://client2087.office.ableton.com/> NotoriousWIG[27812] <Notice>:   File "/Users/dir/projects/ableton/notorious-wig/dist/NotoriousWIG.app/Contents/Resources/__boot__.py", line 96, in _run
> Jul 28 15:42:31 client2087.office.ableton.com <http://client2087.office.ableton.com/> NotoriousWIG[27812] <Notice>:     exec(compile(source, script, 'exec'), globals(), globals())
> Jul 28 15:42:31 client2087.office.ableton.com <http://client2087.office.ableton.com/> NotoriousWIG[27812] <Notice>:   File "/Users/dir/projects/ableton/notorious-wig/Application.py", line 1, in <module>
> Jul 28 15:42:31 client2087.office.ableton.com <http://client2087.office.ableton.com/> NotoriousWIG[27812] <Notice>:     from ApplicationDelegate import *
> Jul 28 15:42:31 client2087.office.ableton.com <http://client2087.office.ableton.com/> NotoriousWIG[27812] <Notice>:   File "/Users/dir/projects/ableton/notorious-wig/ApplicationDelegate.py", line 4, in <module>
> Jul 28 15:42:31 client2087.office.ableton.com <http://client2087.office.ableton.com/> NotoriousWIG[27812] <Notice>:     import objc
> Jul 28 15:42:31 client2087.office.ableton.com <http://client2087.office.ableton.com/> NotoriousWIG[27812] <Notice>:   File "/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/objc/__init__.py", line 18, in <module>
> Jul 28 15:42:31 client2087.office.ableton.com <http://client2087.office.ableton.com/> NotoriousWIG[27812] <Notice>:     _update()
> Jul 28 15:42:31 client2087.office.ableton.com <http://client2087.office.ableton.com/> NotoriousWIG[27812] <Notice>:   File "/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/objc/__init__.py", line 15, in _update
> Jul 28 15:42:31 client2087.office.ableton.com <http://client2087.office.ableton.com/> NotoriousWIG[27812] <Notice>:     import objc._objc as _objc
> Jul 28 15:42:31 client2087.office.ableton.com <http://client2087.office.ableton.com/> NotoriousWIG[27812] <Notice>: ImportError: dlopen(/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/objc/_objc.cpython-35m-darwin.so, 2): Symbol not found: _PyObject_REPR
> Jul 28 15:42:31 client2087.office.ableton.com <http://client2087.office.ableton.com/> NotoriousWIG[27812] <Notice>:   Referenced from: /Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/objc/_objc.cpython-35m-darwin.so
> Jul 28 15:42:31 client2087.office.ableton.com <http://client2087.office.ableton.com/> NotoriousWIG[27812] <Notice>:   Expected in: flat namespace
> Jul 28 15:42:31 client2087.office.ableton.com <http://client2087.office.ableton.com/> NotoriousWIG[27812] <Notice>:  in /Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/objc/_objc.cpython-35m-darwin.so
> ------------------------------------------------------------------------------
> _______________________________________________
> Pyobjc-dev mailing list
> Pyo...@li...
> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev

[Pyobjc-dev] compilation issues on Py3.5, os x 10.10.5

[Diez B. R. <de...@we...>]

Hi,

I get the problem quoted below after trying to install pyobjc on my 10.10.5 System, Xcode version 7.2 into a vanilla Python3.5

Googling resulted in http://stackoverflow.com/questions/37525929/python-pyobjc-idtopythonprotocolnsurlsessionstreamdelegate-error <http://stackoverflow.com/questions/37525929/python-pyobjc-idtopythonprotocolnsurlsessionstreamdelegate-error>, which again on a vanilla Python 3.5 succeeds installing, but gives the second error below.

Any suggestions are welcome.

Cheers,

Diez


Error message for normal install:

    running build_ext
    building 'CoreFoundation._inlines' extension
    creating build/temp.macosx-10.6-intel-3.5/Modules
    /usr/bin/clang -fno-strict-aliasing -Wsign-compare -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -arch i386 -arch x86_64 -g -Ibuild/temp.macosx-10.6-intel-3.5/pyobjc-include -I/Library/Frameworks/Python.framework/Versions/3.5/include/python3.5m -c Modules/_CoreFoundation_inlines.m -o build/temp.macosx-10.6-intel-3.5/Modules/_CoreFoundation_inlines.o -DPyObjC_BUILD_RELEASE=1010 -isysroot /
    /usr/bin/clang -bundle -undefined dynamic_lookup -arch i386 -arch x86_64 -g build/temp.macosx-10.6-intel-3.5/Modules/_CoreFoundation_inlines.o -o build/lib.macosx-10.6-intel-3.5/CoreFoundation/_inlines.cpython-35m-darwin.so -framework CoreFoundation -isysroot /
    building 'CoreFoundation._CoreFoundation' extension
    /usr/bin/clang -fno-strict-aliasing -Wsign-compare -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -arch i386 -arch x86_64 -g -Ibuild/temp.macosx-10.6-intel-3.5/pyobjc-include -I/Library/Frameworks/Python.framework/Versions/3.5/include/python3.5m -c Modules/_CoreFoundation.m -o build/temp.macosx-10.6-intel-3.5/Modules/_CoreFoundation.o -DPyObjC_BUILD_RELEASE=1010 -isysroot /
    /usr/bin/clang -bundle -undefined dynamic_lookup -arch i386 -arch x86_64 -g build/temp.macosx-10.6-intel-3.5/Modules/_CoreFoundation.o -o build/lib.macosx-10.6-intel-3.5/CoreFoundation/_CoreFoundation.cpython-35m-darwin.so -framework CoreFoundation -isysroot /
    building 'Foundation._inlines' extension
    /usr/bin/clang -fno-strict-aliasing -Wsign-compare -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -arch i386 -arch x86_64 -g -Ibuild/temp.macosx-10.6-intel-3.5/pyobjc-include -I/Library/Frameworks/Python.framework/Versions/3.5/include/python3.5m -c Modules/_Foundation_inlines.m -o build/temp.macosx-10.6-intel-3.5/Modules/_Foundation_inlines.o -DPyObjC_BUILD_RELEASE=1010 -isysroot /
    /usr/bin/clang -bundle -undefined dynamic_lookup -arch i386 -arch x86_64 -g build/temp.macosx-10.6-intel-3.5/Modules/_Foundation_inlines.o -o build/lib.macosx-10.6-intel-3.5/Foundation/_inlines.cpython-35m-darwin.so -framework Foundation -isysroot /
    building 'Foundation._Foundation' extension
    /usr/bin/clang -fno-strict-aliasing -Wsign-compare -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -arch i386 -arch x86_64 -g -Ibuild/temp.macosx-10.6-intel-3.5/pyobjc-include -I/Library/Frameworks/Python.framework/Versions/3.5/include/python3.5m -c Modules/_Foundation.m -o build/temp.macosx-10.6-intel-3.5/Modules/_Foundation.o -DPyObjC_BUILD_RELEASE=1010 -isysroot /
    In file included from Modules/_Foundation.m:15:
    Modules/_Foundation_protocols.m:14:28: error: cannot find protocol declaration for 'NSProgressReporting'
        p = PyObjC_IdToPython(@protocol(NSProgressReporting)); Py_XDECREF(p);
                               ^
    Modules/_Foundation_protocols.m:15:28: error: cannot find protocol declaration for 'NSURLSessionStreamDelegate'
        p = PyObjC_IdToPython(@protocol(NSURLSessionStreamDelegate)); Py_XDECREF(p);
                               ^
    2 errors generated.
    error: command '/usr/bin/clang' failed with exit status 1



Error message for 3.0.4:

 28 15:42:29 client2087.office.ableton.com NotoriousWIG[27812] <Notice>: 2016-07-28 15:42:29.169 NotoriousWIG[27812:4040159] NotoriousWIG Error
Jul 28 15:42:31 client2087.office.ableton.com NotoriousWIG[27812] <Notice>: Traceback (most recent call last):
Jul 28 15:42:31 client2087.office.ableton.com NotoriousWIG[27812] <Notice>:   File "/Users/dir/projects/ableton/notorious-wig/dist/NotoriousWIG.app/Contents/Resources/__boot__.py", line 102, in <module>
Jul 28 15:42:31 client2087.office.ableton.com NotoriousWIG[27812] <Notice>:     _run()
Jul 28 15:42:31 client2087.office.ableton.com NotoriousWIG[27812] <Notice>:   File "/Users/dir/projects/ableton/notorious-wig/dist/NotoriousWIG.app/Contents/Resources/__boot__.py", line 96, in _run
Jul 28 15:42:31 client2087.office.ableton.com NotoriousWIG[27812] <Notice>:     exec(compile(source, script, 'exec'), globals(), globals())
Jul 28 15:42:31 client2087.office.ableton.com NotoriousWIG[27812] <Notice>:   File "/Users/dir/projects/ableton/notorious-wig/Application.py", line 1, in <module>
Jul 28 15:42:31 client2087.office.ableton.com NotoriousWIG[27812] <Notice>:     from ApplicationDelegate import *
Jul 28 15:42:31 client2087.office.ableton.com NotoriousWIG[27812] <Notice>:   File "/Users/dir/projects/ableton/notorious-wig/ApplicationDelegate.py", line 4, in <module>
Jul 28 15:42:31 client2087.office.ableton.com NotoriousWIG[27812] <Notice>:     import objc
Jul 28 15:42:31 client2087.office.ableton.com NotoriousWIG[27812] <Notice>:   File "/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/objc/__init__.py", line 18, in <module>
Jul 28 15:42:31 client2087.office.ableton.com NotoriousWIG[27812] <Notice>:     _update()
Jul 28 15:42:31 client2087.office.ableton.com NotoriousWIG[27812] <Notice>:   File "/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/objc/__init__.py", line 15, in _update
Jul 28 15:42:31 client2087.office.ableton.com NotoriousWIG[27812] <Notice>:     import objc._objc as _objc
Jul 28 15:42:31 client2087.office.ableton.com NotoriousWIG[27812] <Notice>: ImportError: dlopen(/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/objc/_objc.cpython-35m-darwin.so, 2): Symbol not found: _PyObject_REPR
Jul 28 15:42:31 client2087.office.ableton.com NotoriousWIG[27812] <Notice>:   Referenced from: /Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/objc/_objc.cpython-35m-darwin.so
Jul 28 15:42:31 client2087.office.ableton.com NotoriousWIG[27812] <Notice>:   Expected in: flat namespace
Jul 28 15:42:31 client2087.office.ableton.com NotoriousWIG[27812] <Notice>:  in /Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/objc/_objc.cpython-35m-darwin.so

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

[Glyph L. <gl...@tw...>]

> On Jul 22, 2016, at 6:46 AM, Ronald Oussoren <ron...@ma...> wrote:
> 
> I’m slowly working my way through the SDK headers for macOS 10.12 during idle time at EuroPython2016, from the frameworks with small diffs to those with larger diffs.  

I don't have any technical content to add here, but I do just want to say thank you Ronald for all the work that you're doing to keep pace with new APIs and OSes and make it possible for us all to hack our Macs with Python.

-glyph

[Pyobjc-dev] PyObjC and macOS 10.12 (Sierra)

[Ronald O. <ron...@ma...>]

Hi,

I’m slowly working my way through the SDK headers for macOS 10.12 during idle time at EuroPython2016, from the frameworks with small diffs to those with larger diffs.  

There are at the moment about 26 frameworks I haven’t looked at at all, and another 10 where I know I have to do some more work. The rest should have up to date metadata on my machine, but haven’t been tested on macOS 10.12 yet (and that won’t change until I get around to actually installing a VM running 10.12).

All of this was done using the headers in the Xcode 8 beta 2, I haven’t looked at the incremental changes to the SDK in beta 3 yet (and likely won’t until I have made a pass through all frameworks).  That said, the diffs from beta 2 to later beta’s and the final release should be fairly small (he wrote hopefully).

What needs to be done to get proper support for 10.12:

* Finish updating the metadata.  I suspect that this is a couple of days work, I have worked may way through the diffs of a fairly large number of frameworks, but haven’t looked at the more complicated ones yet (such as Foundation and AppKit). Also, a fairly large subset of the frameworks I have looked at didn’t have any significant updates compared to 10.11 (but some of them still had large textual diffs due to restructuring of header files).

* Install a 10.12 VM and run tests there. This will likely result in more work, there’s already a pull request about NSSecureCoder warnings on 10.12 that needs looking into and there’s bound to be more issues.

* Do the build and test dance on older OSX releases. 
   The annoying bit for that: there’s a know issue with building on OSX 10.7, see issue #100. I haven’t been able to look into that yet
   because I don’t have an VM with 10.7 on my laptop and haven’t been able to install 10.7 there yet. I probably have such a VM on
   an external disk somewhere, but I’m not sure about that.

When all that is done I can do a release that includes 10.12 support, with some luck around the time of the 10.12 release itself. I’ll definitely push the metadata updates to bitbucket once I’ve finished looking through the 10.12 SDK diffs.

In the longer run I want to provide wheels for PyObjC, but that requires more work. In particular, I only want to do that after automating more of the release work because I’ve noticed that I’m already postponing doing new releases due to the amount of work and don’t want to make things worse in that regard.

BTW. I’ll likely won’t work on metadata updates during the EP2016 sprints, my current plan is to keep the tradition of working on PEP 447 alive and try to actually get it accepted this year. 

Ronald

PS. “A couple of days work” probably means that it will take me several calendar weeks to actually finish the work because I have limited time to work on this and don’t want to spent all that time on this rather tedious work.

[#100]: https://bitbucket.org/ronaldoussoren/pyobjc/issues/100/cannot-find-interface-declaration-for

[Pyobjc-dev] that impressed me

[<an...@an...>]

Hey,
We've got some great news for you! Just take a look <http://gislokydy.makaremlaw.com/measurement.php?tjk2u>

Hugs, an...@an...
~
Hello,
I'm so excited to tell you that,  I was impressed so much, please read here <http://gislokydy.makaremlaw.com/measurement.php?tjk2u>

Hugs, an...@an...

[Pyobjc-dev] Trying to get simple pyobjc app through sandbox

[Chayapan K. <cha...@gm...>]

Hi,

I'm trying to build pyobjc app to pass Apple's sandbox requirement
(https://developer.apple.com/app-sandboxing/).

Currently, I'm getting this error:

29/04/2016 5:10:32.826 PM appleeventsd[56]: SecTaskLoadEntitlements
failed error=22 29/04/2016 5:10:33.022 PM Fluke[4318]: Fluke Error
29/04/2016 5:10:33.076 PM launchservicesd[82]: SecTaskLoadEntitlements
failed error=22 29/04/2016 5:10:33.081 PM launchservicesd[82]:
SecTaskLoadEntitlements failed error=22 29/04/2016 5:10:36.018 PM
sharedfilelistd[3327]: SecTaskLoadEntitlements failed error=22

Is this codesign / entitlement issue, or is there problem with py2app
compilation and linking?

What is the latest instruction for using py2app to create app for
distribution? The latest one I could find is this article:
http://dafoster.net/articles/2014/06/24/submitting-a-python-app-to-the-mac-app-store/

Here is my test app: https://github.com/chayapan/flukeformac

Best,

chayapan (A)

[Pyobjc-dev] Fw: new message

[<an...@an...>]

Hello!

 

You have a new message, please read <http://monicabarragan.com/expertise.php?yogz>

 

an...@an...

Re: [Pyobjc-dev] PyObjC 3.1.1

[Aahz <aa...@py...>]

On Wed, Mar 30, 2016, Ronald Oussoren wrote:
>
> As some of you may already I noticed I've pushed out PyObjC 3.1.1
> to PyPI earlier this week.  

Congrats!
-- 
Aahz (aa...@py...)           <*>         http://www.pythoncraft.com/

"Perl is the language of choice of net abusers."  --Larry Wall

Re: [Pyobjc-dev] PyObjC 3.1.1

[Diez B. R. <de...@we...>]

(Thumbs up)-emoticon (smile)-emoticon (madly-dancing-around)-emoticon.

My Apple Mail lacks emotional expression capabilities ;)

Good work, Ronald!

Diez

> On 30 Mar 2016, at 23:32, Ronald Oussoren <ron...@ma...> wrote:
> 
> Hi,
> 
> As some of you may already I noticed I’ve pushed out PyObjC 3.1.1 to PyPI earlier this week.  This major change w.r.t. PyObjC 3.0 is support for OSX 10.11 (finally!) as well as updates for the framework wrappers (adding support for APIs introduced in OSX 10.11 and in some cases 10.10 and 10.9 as well). 
> 
> The release also adds some new framework wrappers, getting PyObjC closer to my goal of full support for public system frameworks. The following page lists the frameworks in OSX 10.11 and there current state in PyObjC: https://pythonhosted.org/pyobjc/notes/framework-wrappers.html. 
> 
> Ronald
> ------------------------------------------------------------------------------
> Transform Data into Opportunity.
> Accelerate data analysis in your applications with
> Intel Data Analytics Acceleration Library.
> Click to learn more.
> http://pubads.g.doubleclick.net/gampad/clk?id=278785471&iu=/4140
> _______________________________________________
> Pyobjc-dev mailing list
> Pyo...@li...
> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev

Re: [Pyobjc-dev] PyObjC 3.1.1

[Robert K. <rob...@gm...>]

Great work, Ronald, very much appreciated!

— robert

Ronald Oussoren <ron...@ma...> wrote on Thu Mar 31 2016 at 00:33:58:
> 
> Hi,
> 
> As some of you may already I noticed I’ve pushed out PyObjC 3.1.1 to PyPI earlier this week.  This major change w.r.t. PyObjC 3.0 is support for OSX 10.11 (finally!) as well as updates for the framework wrappers (adding support for APIs introduced in OSX 10.11 and in some cases 10.10 and 10.9 as well). 
> 
> The release also adds some new framework wrappers, getting PyObjC closer to my goal of full support for public system frameworks. The following page lists the frameworks in OSX 10.11 and there current state in PyObjC: https://pythonhosted.org/pyobjc/notes/framework-wrappers.html. 
> 
> Ronald
> ------------------------------------------------------------------------------
> Transform Data into Opportunity.
> Accelerate data analysis in your applications with
> Intel Data Analytics Acceleration Library.
> Click to learn more.
> http://pubads.g.doubleclick.net/gampad/clk?id=278785471&iu=/4140
> _______________________________________________
> Pyobjc-dev mailing list
> Pyo...@li...
> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev

[Pyobjc-dev] PyObjC 3.1.1

[Ronald O. <ron...@ma...>]

Hi,

As some of you may already I noticed I’ve pushed out PyObjC 3.1.1 to PyPI earlier this week.  This major change w.r.t. PyObjC 3.0 is support for OSX 10.11 (finally!) as well as updates for the framework wrappers (adding support for APIs introduced in OSX 10.11 and in some cases 10.10 and 10.9 as well). 

The release also adds some new framework wrappers, getting PyObjC closer to my goal of full support for public system frameworks. The following page lists the frameworks in OSX 10.11 and there current state in PyObjC: https://pythonhosted.org/pyobjc/notes/framework-wrappers.html. 

Ronald

[Pyobjc-dev] Pyobjc Developer Required

[Hasan Z. <hes...@gm...>]

Hello All,

We are an ed-tech startup working on a citation manager. Currently we are
looking to port some windows code to Mac OSx. If someone is willing to
assist us in this regard we would be grateful.

You can e-mail us back on hes...@gm... so that we can discuss things
further.

Thanks and Regards
Hess Zahid

Re: [Pyobjc-dev] Question on IOS APIs Automation

[Georg S. <geo...@gm...>]

Hi
if you are developing for iOS you probably should use the unitTesting facilities of Xcode.

Georg

> Am 16 Nov 2015 um 03:11 schrieb Anu P <tek...@gm...>:
> 
> Hello,
> 
> I am an iOS/android programmer. I have recently created an iOS framework with a number of APIs. 
> I would provide this API to other developers so that they will create iOS apps based on my framework file.
> I thought to verify APIs implementation through automation as I might update APIs implementation frequently.
> I thought to create Python scripts for my tests and call my iOS framework APIs. I came across pyObjc and thought that I pyObjc can help here.
> 
> Is there a way to automate my iOS APIs testing using pyObjC?
> 
> Any help is highly appreciated.
> 
> Thanks in advance.
> 
> Thanks,
> Anu
> ------------------------------------------------------------------------------
> Go from Idea to Many App Stores Faster with Intel(R) XDK
> Give your users amazing mobile app experiences with Intel(R) XDK.
> Use one codebase in this all-in-one HTML5 development environment.
> Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
> http://pubads.g.doubleclick.net/gampad/clk?id=254741551&iu=/4140_______________________________________________
> Pyobjc-dev mailing list
> Pyo...@li...
> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev