kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/devel/py-pyobjc/Makefile.common

102 lines
5.1 KiB
Text
Raw Normal View History

py-pyobjc: updated to 6.2 Version 6.2 The project has moved from Bitbucket to Github Remove most remnants of Python 2 support Clean up code quality issues found using flake8 Add pre-commit hook to run black on all Python code. Fix protocol conformance testing when explicitly implementing a protocol Before this bugfix a class explicitly conforming to a protocol could not implement any method that wasn’t declared in the protocol, the bridge would erroneously raise an exception when checking the additional method. Issue reported by Georg Seifert. Fix Python 3 issues in PyObjCTools.Conversion Reported by vinolin asokan. PyObjCTools.Conversio.propertyListFromPythonCollection didn’t recursively convert members of lists and tuples. PyObjCTools.Conversio.propertyListFromPythonCollection and PyObjCTools.Conversio.pythonCollectionFromPropertyList now support sets. Update metadata for Xcode 11.4 (beta 2) Added bindings for framework AutomaticAssessmentConfiguration.framework introduced in macOS 10.15.4 In some cases the compiler uses the type encoding “^{NSObject=#}” instead of “@”. Reported by Georg Seifert. Added bindings for the Metal framework (new in macOS 10.11) Most framework bindings now use the limited ABI for the included C extensions, reducing the number of wheels that are needed. The exception are the bindings for Cocoa, Quartz and libdispatch, those use functionality not available in the limited ABI. The bridge itself (pyobjc-core) still uses the full CPython API. The CoreAudio bindings also don’t use the limited ABI for now, those need more work to work with that ABI.
2020-05-23 09:03:41 +02:00
# $NetBSD: Makefile.common,v 1.10 2020/05/23 07:03:41 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
# used by devel/py-pyobjc-core/Makefile
py-pyobjc: updated to 4.1 Version 4.1: Protection agains buffer overflow and negative indexes in __getitem__ and __setitem__ for objc.varlist instances. Fix incorrect metadata for +[NSEvent addLocalMonitorForEventsMatchingMask:handler:] Fix incorrect and misleading error message in the exception that is raised when return a value from a block that should not return a value. Issue 223: Fix hard crash when executing help(Cocoa) Fetching the help for PyObjC framework wrappers isn’t very useful due to the sheer size of the output (4.5 million lines of output for help(Cocoa) at the moment), but shouldn’t cause a hard crash of the interpreter. Issue 218: Explictly cause an ImportError when reloading `objc._objc` Reloading the PyObjC core extension now raises an ImportError because this cannot work and used to raise a rather vague error. Updated metadata for Xcode 9.2 Added missing `MAC_OS_X_VERSION_*` constants Fix memory error in struct wrappers which resulted in a use-after-free error in the initializer for structs. Add bindings for frameworks Security, SecurityFoundation and and SecurityInterface. The bindings for the Security framework don’t expose a number of older APIs that were deprecated in macOS 10.7. Add bindings to libdispatch. These bindings require macOS 10.8 or later, libdispatch was available earlier but macOS 10.8 changed the API in such a way that wrapping became a lot easier.
2018-02-08 20:54:18 +01:00
# used by devel/py-pyobjc-framework-AVFoundation/Makefile
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
# used by devel/py-pyobjc-framework-AVKit/Makefile
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
# used by devel/py-pyobjc-framework-Accounts/Makefile
# used by devel/py-pyobjc-framework-AddressBook/Makefile
# used by devel/py-pyobjc-framework-AppleScriptKit/Makefile
# used by devel/py-pyobjc-framework-AppleScriptObjC/Makefile
py-pyobjc: updated to 4.1 Version 4.1: Protection agains buffer overflow and negative indexes in __getitem__ and __setitem__ for objc.varlist instances. Fix incorrect metadata for +[NSEvent addLocalMonitorForEventsMatchingMask:handler:] Fix incorrect and misleading error message in the exception that is raised when return a value from a block that should not return a value. Issue 223: Fix hard crash when executing help(Cocoa) Fetching the help for PyObjC framework wrappers isn’t very useful due to the sheer size of the output (4.5 million lines of output for help(Cocoa) at the moment), but shouldn’t cause a hard crash of the interpreter. Issue 218: Explictly cause an ImportError when reloading `objc._objc` Reloading the PyObjC core extension now raises an ImportError because this cannot work and used to raise a rather vague error. Updated metadata for Xcode 9.2 Added missing `MAC_OS_X_VERSION_*` constants Fix memory error in struct wrappers which resulted in a use-after-free error in the initializer for structs. Add bindings for frameworks Security, SecurityFoundation and and SecurityInterface. The bindings for the Security framework don’t expose a number of older APIs that were deprecated in macOS 10.7. Add bindings to libdispatch. These bindings require macOS 10.8 or later, libdispatch was available earlier but macOS 10.8 changed the API in such a way that wrapping became a lot easier.
2018-02-08 20:54:18 +01:00
# used by devel/py-pyobjc-framework-ApplicationServices/Makefile
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
# used by devel/py-pyobjc-framework-Automator/Makefile
# used by devel/py-pyobjc-framework-CFNetwork/Makefile
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
# used by devel/py-pyobjc-framework-CalendarStore/Makefile
# used by devel/py-pyobjc-framework-CloudKit/Makefile
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
# used by devel/py-pyobjc-framework-Cocoa/Makefile
# used by devel/py-pyobjc-framework-Collaboration/Makefile
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
# used by devel/py-pyobjc-framework-ColorSync/Makefile
# used by devel/py-pyobjc-framework-Contacts/Makefile
# used by devel/py-pyobjc-framework-ContactsUI/Makefile
py-pyobjc: updated to 6.2 Version 6.2 The project has moved from Bitbucket to Github Remove most remnants of Python 2 support Clean up code quality issues found using flake8 Add pre-commit hook to run black on all Python code. Fix protocol conformance testing when explicitly implementing a protocol Before this bugfix a class explicitly conforming to a protocol could not implement any method that wasn’t declared in the protocol, the bridge would erroneously raise an exception when checking the additional method. Issue reported by Georg Seifert. Fix Python 3 issues in PyObjCTools.Conversion Reported by vinolin asokan. PyObjCTools.Conversio.propertyListFromPythonCollection didn’t recursively convert members of lists and tuples. PyObjCTools.Conversio.propertyListFromPythonCollection and PyObjCTools.Conversio.pythonCollectionFromPropertyList now support sets. Update metadata for Xcode 11.4 (beta 2) Added bindings for framework AutomaticAssessmentConfiguration.framework introduced in macOS 10.15.4 In some cases the compiler uses the type encoding “^{NSObject=#}” instead of “@”. Reported by Georg Seifert. Added bindings for the Metal framework (new in macOS 10.11) Most framework bindings now use the limited ABI for the included C extensions, reducing the number of wheels that are needed. The exception are the bindings for Cocoa, Quartz and libdispatch, those use functionality not available in the limited ABI. The bridge itself (pyobjc-core) still uses the full CPython API. The CoreAudio bindings also don’t use the limited ABI for now, those need more work to work with that ABI.
2020-05-23 09:03:41 +02:00
# used by devel/py-pyobjc-framework-CoreAudio/Makefile
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
# used by devel/py-pyobjc-framework-CoreBluetooth/Makefile
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
# used by devel/py-pyobjc-framework-CoreData/Makefile
# used by devel/py-pyobjc-framework-CoreLocation/Makefile
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
# used by devel/py-pyobjc-framework-CoreML/Makefile
py-pyobjc: updated to 6.2 Version 6.2 The project has moved from Bitbucket to Github Remove most remnants of Python 2 support Clean up code quality issues found using flake8 Add pre-commit hook to run black on all Python code. Fix protocol conformance testing when explicitly implementing a protocol Before this bugfix a class explicitly conforming to a protocol could not implement any method that wasn’t declared in the protocol, the bridge would erroneously raise an exception when checking the additional method. Issue reported by Georg Seifert. Fix Python 3 issues in PyObjCTools.Conversion Reported by vinolin asokan. PyObjCTools.Conversio.propertyListFromPythonCollection didn’t recursively convert members of lists and tuples. PyObjCTools.Conversio.propertyListFromPythonCollection and PyObjCTools.Conversio.pythonCollectionFromPropertyList now support sets. Update metadata for Xcode 11.4 (beta 2) Added bindings for framework AutomaticAssessmentConfiguration.framework introduced in macOS 10.15.4 In some cases the compiler uses the type encoding “^{NSObject=#}” instead of “@”. Reported by Georg Seifert. Added bindings for the Metal framework (new in macOS 10.11) Most framework bindings now use the limited ABI for the included C extensions, reducing the number of wheels that are needed. The exception are the bindings for Cocoa, Quartz and libdispatch, those use functionality not available in the limited ABI. The bridge itself (pyobjc-core) still uses the full CPython API. The CoreAudio bindings also don’t use the limited ABI for now, those need more work to work with that ABI.
2020-05-23 09:03:41 +02:00
# used by devel/py-pyobjc-framework-CoreMedia/Makefile
py-pyobjc-framework-CoreServices: added version 5.1.2 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. This package contains wrappers for framework 'CoreSpotlight'.
2019-01-08 21:29:42 +01:00
# used by devel/py-pyobjc-framework-CoreServices/Makefile
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
# used by devel/py-pyobjc-framework-CoreSpotlight/Makefile
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
# used by devel/py-pyobjc-framework-CoreText/Makefile
# used by devel/py-pyobjc-framework-CoreWLAN/Makefile
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
# used by devel/py-pyobjc-framework-CryptoTokenKit/Makefile
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
# used by devel/py-pyobjc-framework-DictionaryServices/Makefile
# used by devel/py-pyobjc-framework-DiskArbitration/Makefile
# used by devel/py-pyobjc-framework-EventKit/Makefile
# used by devel/py-pyobjc-framework-ExceptionHandling/Makefile
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
# used by devel/py-pyobjc-framework-ExternalAccessory/Makefile
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
# used by devel/py-pyobjc-framework-FSEvents/Makefile
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
# used by devel/py-pyobjc-framework-FinderSync/Makefile
# used by devel/py-pyobjc-framework-GameCenter/Makefile
# used by devel/py-pyobjc-framework-GameController/Makefile
# used by devel/py-pyobjc-framework-GameKit/Makefile
# used by devel/py-pyobjc-framework-GameplayKit/Makefile
# used by devel/py-pyobjc-framework-IOSurface/Makefile
# used by devel/py-pyobjc-framework-ImageCaptureCore/Makefile
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
# used by devel/py-pyobjc-framework-InputMethodKit/Makefile
# used by devel/py-pyobjc-framework-InstallerPlugins/Makefile
# used by devel/py-pyobjc-framework-InstantMessage/Makefile
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
# used by devel/py-pyobjc-framework-Intents/Makefile
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
# used by devel/py-pyobjc-framework-LatentSemanticMapping/Makefile
# used by devel/py-pyobjc-framework-LaunchServices/Makefile
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
# used by devel/py-pyobjc-framework-LocalAuthentication/Makefile
# used by devel/py-pyobjc-framework-MapKit/Makefile
# used by devel/py-pyobjc-framework-MediaAccessibility/Makefile
# used by devel/py-pyobjc-framework-MediaLibrary/Makefile
# used by devel/py-pyobjc-framework-MediaPlayer/Makefile
py-pyobjc: updated to 6.2 Version 6.2 The project has moved from Bitbucket to Github Remove most remnants of Python 2 support Clean up code quality issues found using flake8 Add pre-commit hook to run black on all Python code. Fix protocol conformance testing when explicitly implementing a protocol Before this bugfix a class explicitly conforming to a protocol could not implement any method that wasn’t declared in the protocol, the bridge would erroneously raise an exception when checking the additional method. Issue reported by Georg Seifert. Fix Python 3 issues in PyObjCTools.Conversion Reported by vinolin asokan. PyObjCTools.Conversio.propertyListFromPythonCollection didn’t recursively convert members of lists and tuples. PyObjCTools.Conversio.propertyListFromPythonCollection and PyObjCTools.Conversio.pythonCollectionFromPropertyList now support sets. Update metadata for Xcode 11.4 (beta 2) Added bindings for framework AutomaticAssessmentConfiguration.framework introduced in macOS 10.15.4 In some cases the compiler uses the type encoding “^{NSObject=#}” instead of “@”. Reported by Georg Seifert. Added bindings for the Metal framework (new in macOS 10.11) Most framework bindings now use the limited ABI for the included C extensions, reducing the number of wheels that are needed. The exception are the bindings for Cocoa, Quartz and libdispatch, those use functionality not available in the limited ABI. The bridge itself (pyobjc-core) still uses the full CPython API. The CoreAudio bindings also don’t use the limited ABI for now, those need more work to work with that ABI.
2020-05-23 09:03:41 +02:00
# used by devel/py-pyobjc-framework-Metal/Makefile
# used by devel/py-pyobjc-framework-MetalKit/Makefile
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
# used by devel/py-pyobjc-framework-ModelIO/Makefile
# used by devel/py-pyobjc-framework-MultipeerConnectivity/Makefile
py-pyobjc: updated to 6.2 Version 6.2 The project has moved from Bitbucket to Github Remove most remnants of Python 2 support Clean up code quality issues found using flake8 Add pre-commit hook to run black on all Python code. Fix protocol conformance testing when explicitly implementing a protocol Before this bugfix a class explicitly conforming to a protocol could not implement any method that wasn’t declared in the protocol, the bridge would erroneously raise an exception when checking the additional method. Issue reported by Georg Seifert. Fix Python 3 issues in PyObjCTools.Conversion Reported by vinolin asokan. PyObjCTools.Conversio.propertyListFromPythonCollection didn’t recursively convert members of lists and tuples. PyObjCTools.Conversio.propertyListFromPythonCollection and PyObjCTools.Conversio.pythonCollectionFromPropertyList now support sets. Update metadata for Xcode 11.4 (beta 2) Added bindings for framework AutomaticAssessmentConfiguration.framework introduced in macOS 10.15.4 In some cases the compiler uses the type encoding “^{NSObject=#}” instead of “@”. Reported by Georg Seifert. Added bindings for the Metal framework (new in macOS 10.11) Most framework bindings now use the limited ABI for the included C extensions, reducing the number of wheels that are needed. The exception are the bindings for Cocoa, Quartz and libdispatch, those use functionality not available in the limited ABI. The bridge itself (pyobjc-core) still uses the full CPython API. The CoreAudio bindings also don’t use the limited ABI for now, those need more work to work with that ABI.
2020-05-23 09:03:41 +02:00
# used by devel/py-pyobjc-framework-NaturalLanguage/Makefile
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
# used by devel/py-pyobjc-framework-NetFS/Makefile
# used by devel/py-pyobjc-framework-NetworkExtension/Makefile
# used by devel/py-pyobjc-framework-NotificationCenter/Makefile
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
# used by devel/py-pyobjc-framework-OpenDirectory/Makefile
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
# used by devel/py-pyobjc-framework-Photos/Makefile
# used by devel/py-pyobjc-framework-PhotosUI/Makefile
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
# used by devel/py-pyobjc-framework-PreferencePanes/Makefile
# used by devel/py-pyobjc-framework-PubSub/Makefile
# used by devel/py-pyobjc-framework-QTKit/Makefile
# used by devel/py-pyobjc-framework-Quartz/Makefile
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
# used by devel/py-pyobjc-framework-SafariServices/Makefile
# used by devel/py-pyobjc-framework-SceneKit/Makefile
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
# used by devel/py-pyobjc-framework-ScreenSaver/Makefile
# used by devel/py-pyobjc-framework-ScriptingBridge/Makefile
# used by devel/py-pyobjc-framework-SearchKit/Makefile
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
# used by devel/py-pyobjc-framework-Security/Makefile
# used by devel/py-pyobjc-framework-SecurityInterface/Makefile
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
# used by devel/py-pyobjc-framework-ServiceManagement/Makefile
# used by devel/py-pyobjc-framework-Social/Makefile
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
# used by devel/py-pyobjc-framework-SpriteKit/Makefile
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
# used by devel/py-pyobjc-framework-StoreKit/Makefile
# used by devel/py-pyobjc-framework-SyncServices/Makefile
# used by devel/py-pyobjc-framework-SystemConfiguration/Makefile
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
# used by devel/py-pyobjc-framework-Vision/Makefile
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
# used by devel/py-pyobjc-framework-WebKit/Makefile
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
# used by devel/py-pyobjc-framework-iTunesLibrary/Makefile
# used by devel/py-pyobjc-framework-libdispatch/Makefile
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 6.2 Version 6.2 The project has moved from Bitbucket to Github Remove most remnants of Python 2 support Clean up code quality issues found using flake8 Add pre-commit hook to run black on all Python code. Fix protocol conformance testing when explicitly implementing a protocol Before this bugfix a class explicitly conforming to a protocol could not implement any method that wasn’t declared in the protocol, the bridge would erroneously raise an exception when checking the additional method. Issue reported by Georg Seifert. Fix Python 3 issues in PyObjCTools.Conversion Reported by vinolin asokan. PyObjCTools.Conversio.propertyListFromPythonCollection didn’t recursively convert members of lists and tuples. PyObjCTools.Conversio.propertyListFromPythonCollection and PyObjCTools.Conversio.pythonCollectionFromPropertyList now support sets. Update metadata for Xcode 11.4 (beta 2) Added bindings for framework AutomaticAssessmentConfiguration.framework introduced in macOS 10.15.4 In some cases the compiler uses the type encoding “^{NSObject=#}” instead of “@”. Reported by Georg Seifert. Added bindings for the Metal framework (new in macOS 10.11) Most framework bindings now use the limited ABI for the included C extensions, reducing the number of wheels that are needed. The exception are the bindings for Cocoa, Quartz and libdispatch, those use functionality not available in the limited ABI. The bridge itself (pyobjc-core) still uses the full CPython API. The CoreAudio bindings also don’t use the limited ABI for now, those need more work to work with that ABI.
2020-05-23 09:03:41 +02:00
PYOBJC_VERS= 6.2
py-pyobjc: updated to 4.1 Version 4.1: Protection agains buffer overflow and negative indexes in __getitem__ and __setitem__ for objc.varlist instances. Fix incorrect metadata for +[NSEvent addLocalMonitorForEventsMatchingMask:handler:] Fix incorrect and misleading error message in the exception that is raised when return a value from a block that should not return a value. Issue 223: Fix hard crash when executing help(Cocoa) Fetching the help for PyObjC framework wrappers isn’t very useful due to the sheer size of the output (4.5 million lines of output for help(Cocoa) at the moment), but shouldn’t cause a hard crash of the interpreter. Issue 218: Explictly cause an ImportError when reloading `objc._objc` Reloading the PyObjC core extension now raises an ImportError because this cannot work and used to raise a rather vague error. Updated metadata for Xcode 9.2 Added missing `MAC_OS_X_VERSION_*` constants Fix memory error in struct wrappers which resulted in a use-after-free error in the initializer for structs. Add bindings for frameworks Security, SecurityFoundation and and SecurityInterface. The bindings for the Security framework don’t expose a number of older APIs that were deprecated in macOS 10.7. Add bindings to libdispatch. These bindings require macOS 10.8 or later, libdispatch was available earlier but macOS 10.8 changed the API in such a way that wrapping became a lot easier.
2018-02-08 20:54:18 +01:00
MAINTAINER?= pkgsrc-users@NetBSD.org
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
HOMEPAGE= https://pyobjc.readthedocs.io/
py-pyobjc: updated to 4.1 Version 4.1: Protection agains buffer overflow and negative indexes in __getitem__ and __setitem__ for objc.varlist instances. Fix incorrect metadata for +[NSEvent addLocalMonitorForEventsMatchingMask:handler:] Fix incorrect and misleading error message in the exception that is raised when return a value from a block that should not return a value. Issue 223: Fix hard crash when executing help(Cocoa) Fetching the help for PyObjC framework wrappers isn’t very useful due to the sheer size of the output (4.5 million lines of output for help(Cocoa) at the moment), but shouldn’t cause a hard crash of the interpreter. Issue 218: Explictly cause an ImportError when reloading `objc._objc` Reloading the PyObjC core extension now raises an ImportError because this cannot work and used to raise a rather vague error. Updated metadata for Xcode 9.2 Added missing `MAC_OS_X_VERSION_*` constants Fix memory error in struct wrappers which resulted in a use-after-free error in the initializer for structs. Add bindings for frameworks Security, SecurityFoundation and and SecurityInterface. The bindings for the Security framework don’t expose a number of older APIs that were deprecated in macOS 10.7. Add bindings to libdispatch. These bindings require macOS 10.8 or later, libdispatch was available earlier but macOS 10.8 changed the API in such a way that wrapping became a lot easier.
2018-02-08 20:54:18 +01:00
LICENSE= mit
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
ONLY_FOR_PLATFORM= Darwin-*-*
py-pyobjc: Python 2.7 is not supported
2019-11-19 06:36:44 +01:00
PYTHON_VERSIONS_INCOMPATIBLE= 27
py-pyobjc: updated to 4.1 Version 4.1: Protection agains buffer overflow and negative indexes in __getitem__ and __setitem__ for objc.varlist instances. Fix incorrect metadata for +[NSEvent addLocalMonitorForEventsMatchingMask:handler:] Fix incorrect and misleading error message in the exception that is raised when return a value from a block that should not return a value. Issue 223: Fix hard crash when executing help(Cocoa) Fetching the help for PyObjC framework wrappers isn’t very useful due to the sheer size of the output (4.5 million lines of output for help(Cocoa) at the moment), but shouldn’t cause a hard crash of the interpreter. Issue 218: Explictly cause an ImportError when reloading `objc._objc` Reloading the PyObjC core extension now raises an ImportError because this cannot work and used to raise a rather vague error. Updated metadata for Xcode 9.2 Added missing `MAC_OS_X_VERSION_*` constants Fix memory error in struct wrappers which resulted in a use-after-free error in the initializer for structs. Add bindings for frameworks Security, SecurityFoundation and and SecurityInterface. The bindings for the Security framework don’t expose a number of older APIs that were deprecated in macOS 10.7. Add bindings to libdispatch. These bindings require macOS 10.8 or later, libdispatch was available earlier but macOS 10.8 changed the API in such a way that wrapping became a lot easier.
2018-02-08 20:54:18 +01:00
SUBST_CLASSES+= pysetup
SUBST_STAGE.pysetup= pre-configure
py-pyobjc: updated to 4.2.1 4.2.1: Bug fixes and improvements.
2018-04-14 10:29:23 +02:00
SUBST_MESSAGE.pysetup= Avoiding hacks in pyobjc_setup.py.
py-pyobjc: updated to 4.1 Version 4.1: Protection agains buffer overflow and negative indexes in __getitem__ and __setitem__ for objc.varlist instances. Fix incorrect metadata for +[NSEvent addLocalMonitorForEventsMatchingMask:handler:] Fix incorrect and misleading error message in the exception that is raised when return a value from a block that should not return a value. Issue 223: Fix hard crash when executing help(Cocoa) Fetching the help for PyObjC framework wrappers isn’t very useful due to the sheer size of the output (4.5 million lines of output for help(Cocoa) at the moment), but shouldn’t cause a hard crash of the interpreter. Issue 218: Explictly cause an ImportError when reloading `objc._objc` Reloading the PyObjC core extension now raises an ImportError because this cannot work and used to raise a rather vague error. Updated metadata for Xcode 9.2 Added missing `MAC_OS_X_VERSION_*` constants Fix memory error in struct wrappers which resulted in a use-after-free error in the initializer for structs. Add bindings for frameworks Security, SecurityFoundation and and SecurityInterface. The bindings for the Security framework don’t expose a number of older APIs that were deprecated in macOS 10.7. Add bindings to libdispatch. These bindings require macOS 10.8 or later, libdispatch was available earlier but macOS 10.8 changed the API in such a way that wrapping became a lot easier.
2018-02-08 20:54:18 +01:00
SUBST_FILES.pysetup= pyobjc_setup.py
py-pyobjc: updated to 6.2 Version 6.2 The project has moved from Bitbucket to Github Remove most remnants of Python 2 support Clean up code quality issues found using flake8 Add pre-commit hook to run black on all Python code. Fix protocol conformance testing when explicitly implementing a protocol Before this bugfix a class explicitly conforming to a protocol could not implement any method that wasn’t declared in the protocol, the bridge would erroneously raise an exception when checking the additional method. Issue reported by Georg Seifert. Fix Python 3 issues in PyObjCTools.Conversion Reported by vinolin asokan. PyObjCTools.Conversio.propertyListFromPythonCollection didn’t recursively convert members of lists and tuples. PyObjCTools.Conversio.propertyListFromPythonCollection and PyObjCTools.Conversio.pythonCollectionFromPropertyList now support sets. Update metadata for Xcode 11.4 (beta 2) Added bindings for framework AutomaticAssessmentConfiguration.framework introduced in macOS 10.15.4 In some cases the compiler uses the type encoding “^{NSObject=#}” instead of “@”. Reported by Georg Seifert. Added bindings for the Metal framework (new in macOS 10.11) Most framework bindings now use the limited ABI for the included C extensions, reducing the number of wheels that are needed. The exception are the bindings for Cocoa, Quartz and libdispatch, those use functionality not available in the limited ABI. The bridge itself (pyobjc-core) still uses the full CPython API. The CoreAudio bindings also don’t use the limited ABI for now, those need more work to work with that ABI.
2020-05-23 09:03:41 +02:00
SUBST_SED.pysetup= -e 's,del sys.modules\["PyObjCTools"\],pass,'
Reference in a new issue Copy permalink