./devel/py-pyobjc-framework-GameplayKit, Bridge between Python and Objective-C (GameplayKit framework)

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ] [ Add to tracker ]

Branch: CURRENT, Version: 5.1.2, Package name: py27-pyobjc-framework-GameplayKit-5.1.2, Maintainer: pkgsrc-users

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 'GameplayKit'.

Required to run:
[devel/py-setuptools] [lang/python27] [devel/py-pyobjc-core] [devel/py-pyobjc-framework-Cocoa] [devel/py-pyobjc-framework-SpriteKit]

Required to build:

Master sites:

SHA1: c5c03a9cbd1b40ec10f1eed36d4bd7d4ed1fc84b
RMD160: 20fb21f113bf260068947be80366c0e1385e1c51
Filesize: 27.85 KB

Version history: (Expand)

CVS history: (Expand)

   2019-01-08 13:08:47 by Adam Ciarcinski | Files touched by this commit (85) | Package updated
Log message:
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 \ 
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: \ 
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 \ 
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.
   2018-08-15 21:00:56 by Adam Ciarcinski | Files touched by this commit (79) | Package updated
Log message:
py-pyobjc: updated to 4.2.2

Version 4.2.2:
Update metadata for Xcode 9.4
The binary release now includes wheels for both variants for the Python.org \ 
installer for python 3.6 and 3.7: 32- and 64-bit for macOS 10.6 or later, and \ 
64-bit only for macOS 10.9 or later.
Ensure the context manager for NSAnimationContext defined in \ 
PyObjCTools.AppCategories actually works.
Fix convenience wrappers for Foundation.NSCache.
Fix convenience wrappers for Foundation.NSHashTable.
   2018-04-14 10:29:30 by Adam Ciarcinski | Files touched by this commit (79) | Package updated
Log message:
py-pyobjc: updated to 4.2.1

Bug fixes and improvements.