Registry / serialization / pyobjc-framework-gamesave

pyobjc-framework-gamesave

JSON →
library12.2pypypiunverified

pyobjc-framework-gamesave provides Python bindings for Apple's macOS GameSave framework. It is part of the larger PyObjC bridge, which allows Python scripts to use and extend Objective-C class libraries, primarily the Cocoa frameworks. The library is actively maintained, with releases frequently aligning with new macOS SDK versions, and its current version is 12.1.

pip install pyobjc-framework-gamesave
INSTALL
IMPORT
SIG · PYOBJC-FRAMEWORK-G
P
pyobjc-framework-gamesave
serializationpythonv12.2
Install
Import
Disk
Pass rate
0/ 10
Env Coverage0 / 10
glibc
3.93.13
musl
3.93.13
Install & Compatibility
Where this runs
tested against v? · pip install
Install × environment matrix
Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux
musl
py 3.103.920 runs
build_error
glibc
py 3.103.920 runs
build_error
Code
Verified usage

Verified import paths — ran on the pinned version, not inferred.

GSGameSaveManager
from GameSave import GSGameSaveManager
PyObjC maps macOS frameworks directly to Python packages with the same name.

This example demonstrates how to import and instantiate `GSGameSaveManager`, a core class from the GameSave framework, using PyObjC. It follows the common Objective-C `alloc().init()` pattern for object creation and prints the object's description. Note that actual GameSave operations might require a running macOS application context or specific entitlements.

from GameSave import GSGameSaveManager from Foundation import NSObject # Common base class for Objective-C objects def main(): print('Attempting to interact with GSGameSaveManager...') # In Objective-C, objects are typically allocated then initialized. # PyObjC follows this pattern for many Cocoa classes. try: manager = GSGameSaveManager.alloc().init() print(f'Successfully initialized GSGameSaveManager: {manager.description()}.') # Further GameSave API calls would go here. # Example: manager.loadGameSavesWithCompletionHandler_(...) except Exception as e: print(f'Error initializing GSGameSaveManager: {e}') print('Note: GameSave framework might require specific application entitlements or context.') if __name__ == '__main__': # For Cocoa applications, an event loop is often required. # For simple script usage, direct execution might suffice or need AppKit integration. # import AppKit # AppKit.NSApplication.sharedApplication() # main() # AppKit.NSApp.run() main()
Debug
Known issues
breakingPyObjC 12.0 (which introduced `pyobjc-framework-gamesave`) dropped support for Python 3.9. Users on Python 3.9 or older must use an earlier PyObjC version or upgrade Python.
fix
Upgrade to Python 3.10 or later, or downgrade `pyobjc-framework-gamesave` to a compatible version if one existed (note: GameSave bindings were introduced in 12.0).
affects: <12.0
breakingPyObjC 11.0 dropped support for Python 3.8. Ensure your Python environment is 3.9 or later if using PyObjC 11.x, or 3.10+ for 12.x.
fix
Upgrade to Python 3.9 or later (for PyObjC 11.x), or 3.10 or later (for PyObjC 12.x).
affects: <11.0
gotcha`pyobjc-framework-gamesave` bindings were first introduced in PyObjC version 12.0. This package is not available for PyObjC versions older than 12.0.
fix
Ensure `pyobjc-framework-gamesave` is installed with `pyobjc-core>=12.0`. Use `pip install 'pyobjc-framework-gamesave>=12.0'`.
affects: <12.0
gotchaPyObjC 12.0 incorrectly indicated support for Python 3.9 in its packaging metadata. This was fixed in PyObjC 12.1.
fix
Upgrade to `pyobjc-framework-gamesave` version 12.1 or later to avoid potential installation issues on Python 3.9 (though Python 3.9 itself is not supported by PyObjC 12.x).
affects: 12.0
gotchaPyObjC's handling of `__init__` when a user implements `__new__` changed in v10.3, then partially reverted in v10.3.1. If you are subclassing Objective-C classes in Python and using custom `__new__`, be aware of potential breakage around object initialization.
fix
Review the PyObjC 10.3 and 10.3.1 release notes regarding `__init__` and `__new__` behavior, and ensure your custom `__new__` implementations are compatible with the specific PyObjC version used.
affects: 10.3
gotchaExperimental free-threading (PEP 703) in Python 3.13 is not fully supported by PyObjC 10.3. While experimental support was introduced in PyObjC 11.0, significant changes were required in the core. Exercise caution if using PyObjC with free-threaded Python 3.13.
fix
Consult PyObjC documentation for current free-threading support status with Python 3.13. For stability, consider using non-free-threaded Python 3.13 or Python 3.12 until full support is confirmed.
affects: 10.3, 11.0
Upgrade
Version history
12.2latest on PyPI · released May 30, 2026
Audit
Dependencies
pyobjc-corerequiredCore PyObjC bridge functionality, implicitly required by all PyObjC framework wrappers.
PythonrequiredRequires Python 3.10 or later.
Agent activity
9 hits · last 30 days
node
8
Resources
pyobjc-framework-gamesave — pip install pyobjc-framework-gamesave · libregistry