kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/devel/py-pyobjc-framework-Collaboration/distinfo

7 lines
495 B
Text
Raw Normal View History

py-pyobjc: updated to 5.1.2 Version 5.1.2 Fix compile error on macOS 10.9 or earlier Calling completion handler failed due to incomplete runtime info PyObjC’s metadata system didn’t automaticly set the call signature for blocks passed into a method implemented in Python. This causes problems when the ObjC or Swift block does not have signature information in the ObjC/blocks runtime. Use MAP_JIT when allocating memory for the executable stubs for Python methods. With the “restricted” runtime you’ll have to add the “com.apple.security.cs.allow-jit” entitlement to use this flag, in earlier versions you’d have to use a different entitlement: “com.apple.security.cs.allow-unsigned-executable-memory”. The MAP_JIT flag is only used on macOS 10.14 or later. Ensure that PyObjC can be built using /usr/bin/python on macOS 10.14 This failed due the problems with header files in the SDK included with Xcode 10. Version 5.1.1 Update metadata for Xcode 10.1 Version 5.1 Xcode 10 “GM” contains one difference from the last beta: the constant MLComputeUnitsCPUAndGPU in the CoreML bindings. Add a proxy for C’s “FILE*” type on Python 3. This is not necessary on Python 2 because the default IO stack on Python 2 already uses FILE* internally. This proxy type is very minimal and shouldn’t not be used for general I/O. Bindings are up-to-date w.r.t. Xcode 10.1 (beta) Updated the support code for framework wrappers to be able to emit deprecation warnings on the first import of a deprecated constants (functions and methods will only raise a deprecation warning when called). This is just an infrastructure change, the actual framework bindings do not yet contain the information used to emit deprecation warnings. Add metadata for deprecation warnings to the “Contacts” framework Import ABCs from collections.abc instead of collections because the latter is deprecated. Instances of most builtin value types and sequences (int, float, str, unicode, tuple, list, set, frozenset and dict) can now be written to archives that require secureCoding. Version 5.0 Version 5.0 of PyObjC primarily adds support for macOS 10.14 (mojave), and also adds support for a couple of older frameworks that weren’t supported before.
2019-01-08 13:08:39 +01:00
$NetBSD: distinfo,v 1.6 2019/01/08 12:08:40 adam Exp $
The PyObjC project aims to provide a bridge between the Python and Objective-C programming languages. The bridge is intended to be fully bidirectional, allowing the Python programmer to take full advantage of the power provided by various Objective-C based toolkits and the Objective-C programmer transparent access to Python based functionality.
2015-04-25 12:40:48 +02:00
py-pyobjc: updated to 5.1.2 Version 5.1.2 Fix compile error on macOS 10.9 or earlier Calling completion handler failed due to incomplete runtime info PyObjC’s metadata system didn’t automaticly set the call signature for blocks passed into a method implemented in Python. This causes problems when the ObjC or Swift block does not have signature information in the ObjC/blocks runtime. Use MAP_JIT when allocating memory for the executable stubs for Python methods. With the “restricted” runtime you’ll have to add the “com.apple.security.cs.allow-jit” entitlement to use this flag, in earlier versions you’d have to use a different entitlement: “com.apple.security.cs.allow-unsigned-executable-memory”. The MAP_JIT flag is only used on macOS 10.14 or later. Ensure that PyObjC can be built using /usr/bin/python on macOS 10.14 This failed due the problems with header files in the SDK included with Xcode 10. Version 5.1.1 Update metadata for Xcode 10.1 Version 5.1 Xcode 10 “GM” contains one difference from the last beta: the constant MLComputeUnitsCPUAndGPU in the CoreML bindings. Add a proxy for C’s “FILE*” type on Python 3. This is not necessary on Python 2 because the default IO stack on Python 2 already uses FILE* internally. This proxy type is very minimal and shouldn’t not be used for general I/O. Bindings are up-to-date w.r.t. Xcode 10.1 (beta) Updated the support code for framework wrappers to be able to emit deprecation warnings on the first import of a deprecated constants (functions and methods will only raise a deprecation warning when called). This is just an infrastructure change, the actual framework bindings do not yet contain the information used to emit deprecation warnings. Add metadata for deprecation warnings to the “Contacts” framework Import ABCs from collections.abc instead of collections because the latter is deprecated. Instances of most builtin value types and sequences (int, float, str, unicode, tuple, list, set, frozenset and dict) can now be written to archives that require secureCoding. Version 5.0 Version 5.0 of PyObjC primarily adds support for macOS 10.14 (mojave), and also adds support for a couple of older frameworks that weren’t supported before.
2019-01-08 13:08:39 +01:00
SHA1 (pyobjc-framework-Collaboration-5.1.2.tar.gz) = f71e18f9e58fd330dd670b050469f0d353c8c0a4
RMD160 (pyobjc-framework-Collaboration-5.1.2.tar.gz) = 4291dcc9e0b5d7a47466f3d71a98b6ffc9774bf2
SHA512 (pyobjc-framework-Collaboration-5.1.2.tar.gz) = 71456c090837e53f9f98ac0a29a24b1885900ad6d81ac210f6b334a09933d8d4fc82063f6253178cbb49d2f3183f6552c880983190a472ba4aa2afbc74765cea
Size (pyobjc-framework-Collaboration-5.1.2.tar.gz) = 12557 bytes
Reference in a new issue Copy permalink