pyobjc-dev — CVS commit notices go here

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

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

PyObjC is not supported on iOS.  AFAIK there is or used to be a port to iOS, but I have no idea if that still exists or how well it works.

Ronald

> On 17 Nov 2015, at 05:45, Anu P <tek...@gm...> wrote:
> 
> Hello,
> 
> Please help me to get answer.
> 
> Anu
> 
> On Sun, Nov 15, 2015 at 6:11 PM, Anu P <tek...@gm... <mailto:tek...@gm...>> wrote:
> 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
> 
> ------------------------------------------------------------------------------
> _______________________________________________
> Pyobjc-dev mailing list
> Pyo...@li...
> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev

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

[Anu P <tek...@gm...>]

Hello,

Please help me to get answer.

Anu

On Sun, Nov 15, 2015 at 6:11 PM, Anu P <tek...@gm...> wrote:

> 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
>

[Pyobjc-dev] Question on IOS APIs Automation

[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

[Pyobjc-dev] zlib not available

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

Hi,

I’m just trying to get a plugins I use for my app to use Python3. I installed Python 3.5 (standard installer) and pyobjc (python3.5 -m easy_install -U pyobjc). Then I make a plugin bundle with `python3.5 setup.py py2app`. 
When I then load the plugin I get a 
zipimport.ZipImportError: can't decompress data; zlib not available

Can someone help me with this?

Thanks
Georg

[Pyobjc-dev] pyrun_string exception handling

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

Hi,

I have and ObjC app that embeds some python scripting using PyRun_SimpleString(). This all works fine. 
For simple scripts it is easy to catch exceptions, just wrap the PyRun_SimpleString() call in a @try/@catch. But if a script adds some UI and throws an exception in a button callback, it is outside of the try block and crashes the app. Is there a way to attach an exception handler to the python environment? 

And what is the best way to extract the most information from the exception (traceback...) from outside of the python environment? For now I added a try block in [NSApplication sentEvent:] but that gives me only the "error message" but not the python back trace.

Thanks in advance.

Georg

Re: [Pyobjc-dev] Need some help creating/dealing with struct types

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

Ronald Oussoren <ron...@ma...> wrote on Thu Aug 20 2015 at 21:38:55:
> Could you file a ticket at my bitbucket repository? I want to provide wrappers for all frameworks, but that takes a lot of time and a ticket helps me to prioritise.


Done: https://bitbucket.org/ronaldoussoren/pyobjc/issues/135/wrap-security-frameworks <https://bitbucket.org/ronaldoussoren/pyobjc/issues/135/wrap-security-frameworks>

– robert

Re: [Pyobjc-dev] Need some help creating/dealing with struct types

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

> On 19 Aug 2015, at 09:00, Robert Klep <rob...@gm...> wrote:
> 
> All,
> 
> My goal is to call [SFAuthorization authorizationWithFlags:rights:environment:] <https://developer.apple.com/library/prerelease/mac/documentation/Security/Reference/SecurityFoundationFramework/Classes/SFAuthorization_Class/index.html#//apple_ref/occ/clm/SFAuthorization/authorizationWithFlags:rights:environment:> from PyObjC. My main issue is with the `rights` argument, a pointer to AuthorizationRights <https://developer.apple.com/library/prerelease/mac/documentation/Security/Reference/authorization_ref/index.html#//apple_ref/swift/tdef/c:@T@AuthorizationRights>.

The rights argument is a pass by reference argument. The easiest way to use them is to tell this to PyObjC, something like:

   objc.registerMetadataForSelector(b’SFAuthorization’, b’authorizationWithFlags:rights:environment:’, {
      ‘arguments’: {
        3: { ‘type_modifier’: b’n’ },
        4: { ‘type_modifier’: b’n’ },
      }
   })

That said, AuthorizationRights is an alias for AuthorisationItemSet and that is a struct with an embedded pointer to a buffer and that’s something that PyObjC doesn’t really support at the moment.

Could you file a ticket at my bitbucket repository? I want to provide wrappers for all frameworks, but that takes a lot of time and a ticket helps me to prioritise.

Ronald

> 
> I initially found this issue: Add ctypes support <https://bitbucket.org/ronaldoussoren/pyobjc/issues/23/add-ctypes-support>, which uses ctypes to create AuthorizationRights. However, even though the issue was solved, I have no idea how to get it working (PyObjC 3.0.4 on OSX 10.10.4).
> 
> Specifically, I'm using this:
> 
> auth = SFAuthorization.authorizationWithFlags_rights_environment_(
>   19,
>   ctypes.pointer(authorization_rights),
>   None)
> 
> Which results in an error similar to the one mentioned in the issue:
> 
>   ValueError: depythonifying 'pointer', got 'LP_AuthorizationRights'
> 
> I also looked at objc.createStructType() <https://pythonhosted.org/pyobjc/metadata/manual.html#objc.createStructType> to use instead of ctypes, but got stuck on the `typestr` argument (I can't find any documentation on it; I assumed it might be similar to Objective-C method signatures, but those aren't very well documented either).
> 
> Any help would be greatly appreciated!
> 
> – robert
> 
> ------------------------------------------------------------------------------
> _______________________________________________
> Pyobjc-dev mailing list
> Pyo...@li...
> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev

[Pyobjc-dev] Need some help creating/dealing with struct types

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

All,

My goal is to call [SFAuthorization authorizationWithFlags:rights:environment:] <https://developer.apple.com/library/prerelease/mac/documentation/Security/Reference/SecurityFoundationFramework/Classes/SFAuthorization_Class/index.html#//apple_ref/occ/clm/SFAuthorization/authorizationWithFlags:rights:environment:> from PyObjC. My main issue is with the `rights` argument, a pointer to AuthorizationRights <https://developer.apple.com/library/prerelease/mac/documentation/Security/Reference/authorization_ref/index.html#//apple_ref/swift/tdef/c:@T@AuthorizationRights>.

I initially found this issue: Add ctypes support <https://bitbucket.org/ronaldoussoren/pyobjc/issues/23/add-ctypes-support>, which uses ctypes to create AuthorizationRights. However, even though the issue was solved, I have no idea how to get it working (PyObjC 3.0.4 on OSX 10.10.4).

Specifically, I'm using this:

auth = SFAuthorization.authorizationWithFlags_rights_environment_(
  19,
  ctypes.pointer(authorization_rights),
  None)

Which results in an error similar to the one mentioned in the issue:

  ValueError: depythonifying 'pointer', got 'LP_AuthorizationRights'

I also looked at objc.createStructType() <https://pythonhosted.org/pyobjc/metadata/manual.html#objc.createStructType> to use instead of ctypes, but got stuck on the `typestr` argument (I can't find any documentation on it; I assumed it might be similar to Objective-C method signatures, but those aren't very well documented either).

Any help would be greatly appreciated!

– robert

Re: [Pyobjc-dev] problems installing pyobjc

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

This isn’t a pyobjc-issue, but a pip/SSL setup thing.

Here you find a few possible solutions:

  http://stackoverflow.com/questions/25981703/pip-install-fails-with-connection-error-ssl-certificate-verify-failed-certi <http://stackoverflow.com/questions/25981703/pip-install-fails-with-connection-error-ssl-certificate-verify-failed-certi>

HTH,

Diez

> On 05 Aug 2015, at 16:55, Danny Rubin <dan...@ic...> wrote:
> 
> I am running MacOS 10.10.3
> I downloaded pyobjc-3.0.4
> When I try to install using ‘sudo python setup.py install’   I get the following errors:
> 
> 
> Download error on https://pypi.python.org/simple/pyobjc-framework-StoreKit/: <https://pypi.python.org/simple/pyobjc-framework-StoreKit/:> [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:581) -- Some packages may not be found!
> Couldn't find index page for 'pyobjc-framework-StoreKit' (maybe misspelled?)
> Scanning index of all packages (this may take a while)
> Reading https://pypi.python.org/simple/ <https://pypi.python.org/simple/>
> Download error on https://pypi.python.org/simple/: <https://pypi.python.org/simple/:> [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:581) -- Some packages may not be found!
> No local packages or download links found for pyobjc-framework-StoreKit==3.0.4
> error: Could not find suitable distribution for Requirement.parse('pyobjc-framework-StoreKit==3.0.4')
> 
> Any idea what might be causing this error and how I can fix it?
> thank you in advance
> Danny
> 
> 
> 
> ------------------------------------------------------------------------------
> _______________________________________________
> Pyobjc-dev mailing list
> Pyo...@li...
> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev

[Pyobjc-dev] problems installing pyobjc

[Danny R. <dan...@ic...>]

I am running MacOS 10.10.3
I downloaded pyobjc-3.0.4
When I try to install using ‘sudo python setup.py install’   I get the following errors:


Download error on https://pypi.python.org/simple/pyobjc-framework-StoreKit/: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:581) -- Some packages may not be found!
Couldn't find index page for 'pyobjc-framework-StoreKit' (maybe misspelled?)
Scanning index of all packages (this may take a while)
Reading https://pypi.python.org/simple/
Download error on https://pypi.python.org/simple/: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:581) -- Some packages may not be found!
No local packages or download links found for pyobjc-framework-StoreKit==3.0.4
error: Could not find suitable distribution for Requirement.parse('pyobjc-framework-StoreKit==3.0.4')

Any idea what might be causing this error and how I can fix it?
thank you in advance
Danny

Re: [Pyobjc-dev] framework bindings for OSX 10.11

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

I have thought about this (or rather, about just patching the SDK headers directly) and this might work, but I don’t know how much crap I’d run into with this.

I have to do manual work anyway to verify the extracted information and write test cases, and for now I’ll just do everything by hand. To limit the amount of work I’ve started a local Mercurial repository containing the current SDK headers, I’ll use that to detect changes and update the metadata.

To be honest the metadata extractor tools haven’t brought what I’d hoped: I basically end up having to do a lot of work between OSX releases just to keep those tools working and would have had to spent less time if I just had started with manually maintained bindings in the first place.

I don’t really like this because I’ll have to do a lot of boring grunt work, but working on the tooling sucks as well.  I still hope to have finished the work on the 10.11 bindings by the time 10.11 is released, and hopefully can start doing more fun work afterwards (such as hacking on asyncio support in PyObjC).

Ronald

> On 23 Jul 2015, at 19:10, Ian McCullough <ip...@po...> wrote:
> 
> Just curious, have you considered making a deep copy of the headers and simply find/replacing all the nonnull stuff out of it, and then using the resulting headers?
> 
> Ian
> 
> 
> On Thu, Jul 23, 2015 at 9:14 AM, Ronald Oussoren <ron...@ma... <mailto:ron...@ma...>> wrote:
> 
> > On 21 Jul 2015, at 18:31, Ronald Oussoren <ron...@ma... <mailto:ron...@ma...>> wrote:
> >
> >
> >> On 21 Jul 2015, at 17:01, Ronald Oussoren <ron...@ma... <mailto:ron...@ma...>> wrote:
> >>
> >> Hi,
> >>
> >> I was stupid enough to start working on the framework bindings for OSX 10.11, and guess what: the tool for generating the metadata doesn’t work with the 10.11 headers due to unexpected breakage in libclang (for some reason the type attribute of some nodes no longer revers to the actual type but some “UNEXPOSED” node instead).   The headers for 10.10 work fine with the same compiler… Sigh….
> >>
> >> I’ll see if I can work around this problem, but this does mean that generating the 10.11 bindings will take longer than I had hoped. And that’s already way longer than it should be, but I have plans to reduce the amount of work needed.
> >>
> >> Back to fighting with tools,
> >
> > I have found why I run into problems, but haven’t found a solution yet. The problem is that there are implicit __nonnull attributes on values (or types) and that attribute type is not exposed through libclang (or maybe there’s just a problem with the python bindings to libclang, but the former seems more likely).
> >
> > Now just to find a way around this…
> 
> I haven’t found a way around this and have decided not to spent more time fighting libclang for now.  For now I’ll just maintain the bindings completely by hand. I’ve done some restructuring on my machine that should make this easier, at least once I’ve done a pass through the beta3 headers for all frameworks that already have bindings.
> 
> This sucks, but I don’t think I’ll find a better solution without hacking on libclang and that’s not something I’m willing to do at the moment (and even then it wouldn’t help, I could only use the result when the resulting patch would be used in the libclang that shipped with Xcode).
> 
> Maybe I should “just” write my own Objective-C parser in Python later on ;-)
> 
> 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...
> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev

Re: [Pyobjc-dev] framework bindings for OSX 10.11

[Ian M. <ip...@po...>]

Just curious, have you considered making a deep copy of the headers and
simply find/replacing all the nonnull stuff out of it, and then using the
resulting headers?

Ian


On Thu, Jul 23, 2015 at 9:14 AM, Ronald Oussoren <ron...@ma...>
wrote:

>
> > On 21 Jul 2015, at 18:31, Ronald Oussoren <ron...@ma...>
> wrote:
> >
> >
> >> On 21 Jul 2015, at 17:01, Ronald Oussoren <ron...@ma...>
> wrote:
> >>
> >> Hi,
> >>
> >> I was stupid enough to start working on the framework bindings for OSX
> 10.11, and guess what: the tool for generating the metadata doesn’t work
> with the 10.11 headers due to unexpected breakage in libclang (for some
> reason the type attribute of some nodes no longer revers to the actual type
> but some “UNEXPOSED” node instead).   The headers for 10.10 work fine with
> the same compiler… Sigh….
> >>
> >> I’ll see if I can work around this problem, but this does mean that
> generating the 10.11 bindings will take longer than I had hoped. And that’s
> already way longer than it should be, but I have plans to reduce the amount
> of work needed.
> >>
> >> Back to fighting with tools,
> >
> > I have found why I run into problems, but haven’t found a solution yet.
> The problem is that there are implicit __nonnull attributes on values (or
> types) and that attribute type is not exposed through libclang (or maybe
> there’s just a problem with the python bindings to libclang, but the former
> seems more likely).
> >
> > Now just to find a way around this…
>
> I haven’t found a way around this and have decided not to spent more time
> fighting libclang for now.  For now I’ll just maintain the bindings
> completely by hand. I’ve done some restructuring on my machine that should
> make this easier, at least once I’ve done a pass through the beta3 headers
> for all frameworks that already have bindings.
>
> This sucks, but I don’t think I’ll find a better solution without hacking
> on libclang and that’s not something I’m willing to do at the moment (and
> even then it wouldn’t help, I could only use the result when the resulting
> patch would be used in the libclang that shipped with Xcode).
>
> Maybe I should “just” write my own Objective-C parser in Python later on
> ;-)
>
> Ronald
>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Pyobjc-dev mailing list
> Pyo...@li...
> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev
>

Re: [Pyobjc-dev] framework bindings for OSX 10.11

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

> On 21 Jul 2015, at 18:31, Ronald Oussoren <ron...@ma...> wrote:
> 
> 
>> On 21 Jul 2015, at 17:01, Ronald Oussoren <ron...@ma...> wrote:
>> 
>> Hi,
>> 
>> I was stupid enough to start working on the framework bindings for OSX 10.11, and guess what: the tool for generating the metadata doesn’t work with the 10.11 headers due to unexpected breakage in libclang (for some reason the type attribute of some nodes no longer revers to the actual type but some “UNEXPOSED” node instead).   The headers for 10.10 work fine with the same compiler… Sigh….
>> 
>> I’ll see if I can work around this problem, but this does mean that generating the 10.11 bindings will take longer than I had hoped. And that’s already way longer than it should be, but I have plans to reduce the amount of work needed.
>> 
>> Back to fighting with tools,
> 
> I have found why I run into problems, but haven’t found a solution yet. The problem is that there are implicit __nonnull attributes on values (or types) and that attribute type is not exposed through libclang (or maybe there’s just a problem with the python bindings to libclang, but the former seems more likely).
> 
> Now just to find a way around this…

I haven’t found a way around this and have decided not to spent more time fighting libclang for now.  For now I’ll just maintain the bindings completely by hand. I’ve done some restructuring on my machine that should make this easier, at least once I’ve done a pass through the beta3 headers for all frameworks that already have bindings.

This sucks, but I don’t think I’ll find a better solution without hacking on libclang and that’s not something I’m willing to do at the moment (and even then it wouldn’t help, I could only use the result when the resulting patch would be used in the libclang that shipped with Xcode).

Maybe I should “just” write my own Objective-C parser in Python later on ;-)

Ronald

Re: [Pyobjc-dev] framework bindings for OSX 10.11

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

> On 21 Jul 2015, at 17:01, Ronald Oussoren <ron...@ma...> wrote:
> 
> Hi,
> 
> I was stupid enough to start working on the framework bindings for OSX 10.11, and guess what: the tool for generating the metadata doesn’t work with the 10.11 headers due to unexpected breakage in libclang (for some reason the type attribute of some nodes no longer revers to the actual type but some “UNEXPOSED” node instead).   The headers for 10.10 work fine with the same compiler… Sigh….
> 
> I’ll see if I can work around this problem, but this does mean that generating the 10.11 bindings will take longer than I had hoped. And that’s already way longer than it should be, but I have plans to reduce the amount of work needed.
> 
> Back to fighting with tools,

I have found why I run into problems, but haven’t found a solution yet. The problem is that there are implicit __nonnull attributes on values (or types) and that attribute type is not exposed through libclang (or maybe there’s just a problem with the python bindings to libclang, but the former seems more likely).

Now just to find a way around this...

Ronald

[Pyobjc-dev] Program shutdown order issue

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

Hi,

In issue #124 <https://bitbucket.org/ronaldoussoren/pyobjc/issues/124/odd-crash-when-deallocating-oc_pythonarray <https://bitbucket.org/ronaldoussoren/pyobjc/issues/124/odd-crash-when-deallocating-oc_pythonarray>> it appears that there is a race condition when cleanly existing an application.

The application launching stub basically does:

   Py_Initialize();

   PyRun_….(); /* Actually run the main python script which starts a (Cocoa) eventloop */

   Py_Finalize();

The race condition occurs during (or after) the last line: some background process of the Cocoa frameworks still has a reference to a Python object and tries to use it. When you’re unlucky this happens when the interpreter is already marked as unitialized and you get a crash when PyObjC tries to call into the interpreter.

Does anyone know of a way to run code *after* Cocoa’s house keeping code is idle?  The alternative would be to not call Py_Finalize(), but then the interpreter doesn’t shut down cleanly and that can have unwanted side effects as well (such as files not being closed cleanly, which might leave buffers unflushed).

Ronald

Re: [Pyobjc-dev] Loading Classes from Private Frameworks with objc.lookUpClass

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

Hi

I usually use NSClassFromString().

Georg

> Am 06.05.2015 um 12:42 schrieb Ronald Oussoren <ron...@ma...>:
> 
> 
>> On 06 May 2015, at 10:06, Robert Klep <rob...@gm...> wrote:
>> 
>> Hey Eric,
>> 
>> I think that MVMailBundle is implemented by the Mail application itself, so you can only look it up within that context (ie running as a plug-in inside Mail). It's not clear to me if you're doing that.
>> 
>> FWIW, my Mail plug-in actually uses `objc.runtime.MVMailBundle` instead of using `objc.lookUpClass()` for that particular class (can't remember why; at some point I switched from using lookUpClass() to using objc.runtime), although I do look up other (Mail-only) classes using it.
> 
> objc.runtime is deprecated, and IIRC I removed it in PyObjC 3.0
> 
> Ronald
> 
>> 
>> – robert
>> 
>> Eric Fernance <er...@di...> wrote on Wed May 06 2015 at 09:13:25:
>>> Hi Folks,
>>> 
>>> I feel like I’ve been banging my head against a wall and looking for a couple of pointers.
>>> 
>>> I have seen examples of writing mail.app plugins where the private class is loaded using objc.lookUpClass.  For some reason I seem completely unable to get this to work.
>>> 
>>> I have tested from the command line using a variety of class names and any of the classes from public frameworks seem to load just fine (i.e NSOjbect etc).  When I try to load the MVMailBundle class using:
>>> 
>>> objc.lookUpClass('MVMailBundle’)
>>> 
>>> I receive an error: objc.nosuchclass_error: MVMailBundle
>>> 
>>> System details are: Mac OSX 10.10.2
>>> Python: 2.7
>>> PyObjC: PyObjC 3.0.4 
>>> 
>>> Is there somewhere that I need to switch on or enable the support for loading classes from private frameworks?
>>> 
>>> Any guidance would be really appreciated.
>>> 
>>> Cheers,
>>> Eric.
>>> 
>>> ------------------------------------------------------------------------------
>>> One dashboard for servers and applications across Physical-Virtual-Cloud 
>>> Widest out-of-the-box monitoring support with 50+ applications
>>> Performance metrics, stats and reports that give you Actionable Insights
>>> Deep dive visibility with transaction tracing using APM Insight.
>>> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y_______________________________________________
>>> Pyobjc-dev mailing list
>>> Pyo...@li...
>>> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev
>> 
>> ------------------------------------------------------------------------------
>> One dashboard for servers and applications across Physical-Virtual-Cloud 
>> Widest out-of-the-box monitoring support with 50+ applications
>> Performance metrics, stats and reports that give you Actionable Insights
>> Deep dive visibility with transaction tracing using APM Insight.
>> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y_______________________________________________
>> Pyobjc-dev mailing list
>> Pyo...@li...
>> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev
> 
> ------------------------------------------------------------------------------
> One dashboard for servers and applications across Physical-Virtual-Cloud 
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y_______________________________________________
> Pyobjc-dev mailing list
> Pyo...@li...
> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev

Re: [Pyobjc-dev] Loading Classes from Private Frameworks with objc.lookUpClass

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

Ronald Oussoren <ron...@ma...> wrote on Wed May 06 2015 at 13:07:26:
>> FWIW, my Mail plug-in actually uses `objc.runtime.MVMailBundle` instead of using `objc.lookUpClass()` for that particular class (can't remember why; at some point I switched from using lookUpClass() to using objc.runtime), although I do look up other (Mail-only) classes using it.
> 
> objc.runtime is deprecated, and IIRC I removed it in PyObjC 3.0


Good to know, thanks.

– robert

Re: [Pyobjc-dev] Loading Classes from Private Frameworks with objc.lookUpClass

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

> On 06 May 2015, at 10:06, Robert Klep <rob...@gm...> wrote:
> 
> Hey Eric,
> 
> I think that MVMailBundle is implemented by the Mail application itself, so you can only look it up within that context (ie running as a plug-in inside Mail). It's not clear to me if you're doing that.
> 
> FWIW, my Mail plug-in actually uses `objc.runtime.MVMailBundle` instead of using `objc.lookUpClass()` for that particular class (can't remember why; at some point I switched from using lookUpClass() to using objc.runtime), although I do look up other (Mail-only) classes using it.

objc.runtime is deprecated, and IIRC I removed it in PyObjC 3.0

Ronald

> 
> – robert
> 
> Eric Fernance <er...@di... <mailto:er...@di...>> wrote on Wed May 06 2015 at 09:13:25:
>> Hi Folks,
>> 
>> I feel like I’ve been banging my head against a wall and looking for a couple of pointers.
>> 
>> I have seen examples of writing mail.app plugins where the private class is loaded using objc.lookUpClass.  For some reason I seem completely unable to get this to work.
>> 
>> I have tested from the command line using a variety of class names and any of the classes from public frameworks seem to load just fine (i.e NSOjbect etc).  When I try to load the MVMailBundle class using:
>> 
>> objc.lookUpClass('MVMailBundle’)
>> 
>> I receive an error: objc.nosuchclass_error: MVMailBundle
>> 
>> System details are: Mac OSX 10.10.2
>> Python: 2.7
>> PyObjC: PyObjC 3.0.4 
>> 
>> Is there somewhere that I need to switch on or enable the support for loading classes from private frameworks?
>> 
>> Any guidance would be really appreciated.
>> 
>> Cheers,
>> Eric.
>> 
>> ------------------------------------------------------------------------------
>> One dashboard for servers and applications across Physical-Virtual-Cloud 
>> Widest out-of-the-box monitoring support with 50+ applications
>> Performance metrics, stats and reports that give you Actionable Insights
>> Deep dive visibility with transaction tracing using APM Insight.
>> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y_______________________________________________ <http://ad.doubleclick.net/ddm/clk/290420510;117567292;y_______________________________________________>
>> Pyobjc-dev mailing list
>> Pyo...@li...
>> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev
> 
> ------------------------------------------------------------------------------
> One dashboard for servers and applications across Physical-Virtual-Cloud 
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y_______________________________________________
> Pyobjc-dev mailing list
> Pyo...@li...
> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev

Re: [Pyobjc-dev] Loading Classes from Private Frameworks with objc.lookUpClass

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

> On 06 May 2015, at 08:11, Eric Fernance <er...@di...> wrote:
> 
> Hi Folks,
> 
> I feel like I’ve been banging my head against a wall and looking for a couple of pointers.
> 
> I have seen examples of writing mail.app plugins where the private class is loaded using objc.lookUpClass.  For some reason I seem completely unable to get this to work.
> 
> I have tested from the command line using a variety of class names and any of the classes from public frameworks seem to load just fine (i.e NSOjbect etc).  When I try to load the MVMailBundle class using:
> 
> objc.lookUpClass('MVMailBundle’)
> 
> I receive an error: objc.nosuchclass_error: MVMailBundle
> 
> System details are: Mac OSX 10.10.2
> Python: 2.7
> PyObjC: PyObjC 3.0.4 
> 
> Is there somewhere that I need to switch on or enable the support for loading classes from private frameworks?

You need to ensure that the private framework is loaded, otherwise the class won’t be available.

Ronald
> 
> Any guidance would be really appreciated.
> 
> Cheers,
> Eric.
> 
> ------------------------------------------------------------------------------
> One dashboard for servers and applications across Physical-Virtual-Cloud 
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y_______________________________________________
> Pyobjc-dev mailing list
> Pyo...@li...
> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev

Re: [Pyobjc-dev] Loading Classes from Private Frameworks with objc.lookUpClass

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

Hey Eric,

I think that MVMailBundle is implemented by the Mail application itself, so you can only look it up within that context (ie running as a plug-in inside Mail). It's not clear to me if you're doing that.

FWIW, my Mail plug-in actually uses `objc.runtime.MVMailBundle` instead of using `objc.lookUpClass()` for that particular class (can't remember why; at some point I switched from using lookUpClass() to using objc.runtime), although I do look up other (Mail-only) classes using it.

– robert

Eric Fernance <er...@di...> wrote on Wed May 06 2015 at 09:13:25:
> Hi Folks,
> 
> I feel like I’ve been banging my head against a wall and looking for a couple of pointers.
> 
> I have seen examples of writing mail.app plugins where the private class is loaded using objc.lookUpClass.  For some reason I seem completely unable to get this to work.
> 
> I have tested from the command line using a variety of class names and any of the classes from public frameworks seem to load just fine (i.e NSOjbect etc).  When I try to load the MVMailBundle class using:
> 
> objc.lookUpClass('MVMailBundle’)
> 
> I receive an error: objc.nosuchclass_error: MVMailBundle
> 
> System details are: Mac OSX 10.10.2
> Python: 2.7
> PyObjC: PyObjC 3.0.4 
> 
> Is there somewhere that I need to switch on or enable the support for loading classes from private frameworks?
> 
> Any guidance would be really appreciated.
> 
> Cheers,
> Eric.
> 
> ------------------------------------------------------------------------------
> One dashboard for servers and applications across Physical-Virtual-Cloud 
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y_______________________________________________
> Pyobjc-dev mailing list
> Pyo...@li...
> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev

[Pyobjc-dev] Loading Classes from Private Frameworks with objc.lookUpClass

[Eric F. <er...@di...>]

Hi Folks,

I feel like I’ve been banging my head against a wall and looking for a couple of pointers.

I have seen examples of writing mail.app plugins where the private class is loaded using objc.lookUpClass.  For some reason I seem completely unable to get this to work.

I have tested from the command line using a variety of class names and any of the classes from public frameworks seem to load just fine (i.e NSOjbect etc).  When I try to load the MVMailBundle class using:

objc.lookUpClass('MVMailBundle’)

I receive an error: objc.nosuchclass_error: MVMailBundle

System details are: Mac OSX 10.10.2
Python: 2.7
PyObjC: PyObjC 3.0.4 

Is there somewhere that I need to switch on or enable the support for loading classes from private frameworks?

Any guidance would be really appreciated.

Cheers,
Eric.

Re: [Pyobjc-dev] pyobjc & py2app & OSX version

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

> On 23 Mar 2015, at 13:38, Karsten Wolf <kar...@go...> wrote:
> 
> Hello,
> 
> is it now possible to create pyobjc/py2app applications for system versions lower than the compiling system?
> 
> The problem is that customer A (who needs the py2app programs) is on 10.6 and customer B urges me to upgrade to 10.7 for vpn/network reasons.
> 
> Is that solvable without maintaining (and permanently rebooting) 2 systems?

It is, although you still have to test to be sure.  Providing tested binaries for PyObjC is on my wishlist, and has been for quite some time.  With those binaries it would be a trivial task.

In general it should be possible to build an application needs to be deployed on on older OSX release by setting the deployment target appropriately[1] when building the C code. The hard part is making sure that the build process doesn’t pick up unwanted dependencies, especially when using autoconf. PyObjC, and Python itself, should be safe in that regard.

Ronald

[1] Ignoring PPC, Apple’s toolchain doesn’t support that with recent enough releases of Xcode.


> 
> -karsten
> 
> 
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming The Go Parallel Website, sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for all
> things parallel software development, from weekly thought leadership blogs to
> news, videos, case studies, tutorials and more. Take a look and join the 
> conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> Pyobjc-dev mailing list
> Pyo...@li...
> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev

[Pyobjc-dev] pyobjc & py2app & OSX version

[Karsten W. <kar...@go...>]

Hello,

is it now possible to create pyobjc/py2app applications for system versions lower than the compiling system?

The problem is that customer A (who needs the py2app programs) is on 10.6 and customer B urges me to upgrade to 10.7 for vpn/network reasons.

Is that solvable without maintaining (and permanently rebooting) 2 systems?

-karsten

[Pyobjc-dev] Generating skeletons for PyCharm code completion

[Ian M. <ip...@po...>]

So I had an idea, and I wanted to see if anyone else had any thoughts on it:

I use PyCharm for all my python development. It has pretty good code
completion for the core python API and has what's called "skeletons" for
other, external modules. These skeletons are discussed in limited detail
here: https://www.jetbrains.com/pycharm/help/using-python-skeletons.html

In short, these skeletons are valid python files with stubs for all the
functions in the module, and ideally, with type annotations for parameters
and return types. This facilitates not only code completion, but allows for
a useful (if not complete) amount of static analysis. Within the libraries
for which skeletons exist, they have proven to be incredible productivity
accelerators.

For me, working with PyObjC has been harder than working with other python
modules because (I assume because of the lazy nature of PyObjC modules)
PyCharm doesn't have, and doesn't seem to generate skeletons for PyObjC
modules. It looks like their generator looks for exported symbols in the
modules, and since it seems that everything for PyObjC is handled
dynamically, the generator doesn't find anything.

That roadblock aside, it seems like with the rich metadata already required
for the bridge, it should be possible to generate skeletons from the PyObjC
modules that would facilitate code-completion and static analysis in IDEs
that support it.

I was planning to hack on this for a little while over my impending
vacation, but I figured I'd put out this message to see if anyone else had
looked into this, or had thoughts on the subject. Sure would be nice to be
able to work with code completion and static analysis for PyObjC modules.

Regards,
Ian

Re: [Pyobjc-dev] Moving PyObjC and py2app forward

[Greg E. <gre...@ca...>]

Ronald Oussoren wrote:
> 
> A site like kickstarter also appears to 
> require you to work on a specific product (a gadget, new software, …) 
> and not ongoing development of an existing project.

Patreon might be a better option for something like PyObjC:

https://www.patreon.com/

-- 
Greg