Registry / ai-ml / pyobjc-framework-latentsemanticmapping

pyobjc-framework-latentsemanticmapping

JSON →
library12.2pypypiunverified

This library provides Python wrappers for Apple's LatentSemanticMapping framework on macOS, enabling Python applications to leverage latent semantic analysis capabilities for tasks like text similarity and natural language processing. It is part of the larger PyObjC project, currently at version 12.1, with releases typically tied to macOS SDK updates and Python version support cycles.

pip install pyobjc-framework-latentsemanticmapping
INSTALL
IMPORT
SIG · PYOBJC-FRAMEWORK-L
P
pyobjc-framework-latentsemanticmapping
ai-mlpythonv12.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.

LSMLanguageModel
from LatentSemanticMapping import LSMLanguageModel
LSMSentence
from LatentSemanticMapping import LSMSentence

This quickstart demonstrates how to import and instantiate a basic object from the LatentSemanticMapping framework using PyObjC.

from LatentSemanticMapping import LSMSentence import objc # Instantiate a simple sentence object using the framework sentence_string = "The quick brown fox jumps over the lazy dog." sentence = LSMSentence.sentenceWithString_(sentence_string) print(f"Created LSMSentence object: {sentence}") print(f"Content: {sentence.string()}") # You would typically use this with an LSMLanguageModel for semantic analysis # (e.g., LSMLanguageModel.languageModelForLocale_options_error_) # which requires specific setup (e.g., locale, options, or training data).
Debug
Known issues
breakingPyObjC major versions frequently drop support for older Python versions. For example, v12.0 dropped Python 3.9 support, and v11.0 dropped Python 3.8. Ensure your Python environment meets the `requires_python` constraint for your PyObjC version.
fix
Upgrade your Python interpreter to a supported version (e.g., Python 3.10+ for PyObjC 12.x) or use an older PyObjC version that supports your Python environment.
affects: 11.0, 12.0+
breakingPyObjC 11.1 aligned its Automatic Reference Counting (ARC) behavior for initializer methods with `clang`'s documentation. Methods in the 'init' family now correctly steal a reference to `self` and return a new reference. This is a fundamental change in reference counting semantics that could affect custom memory management or interaction with Objective-C objects.
fix
Review any code that explicitly manages references to objects returned by `init` methods or that relies on specific reference counts for `self` within `init`-like methods. Adjust memory management logic if necessary.
affects: 11.1+
gotchaPyObjC 11.0 introduced experimental support for free-threading (PEP 703) in Python 3.13, requiring significant internal changes related to C Python API usage and borrowed references. While experimental, this could introduce subtle bugs or performance issues in multi-threaded applications using PyObjC with Python 3.13.
fix
Thoroughly test multi-threaded PyObjC applications on Python 3.13. If encountering issues, consider using an earlier Python version or isolating PyObjC calls to a single thread until free-threading support matures.
affects: 11.0+
gotchaPyObjC 10.3 temporarily broke the ability to use `__init__` in Python subclasses when a user-defined `__new__` method was present. This was partially reverted in 10.3.1: `__init__` can now be used if a user-implemented `__new__` exists, but not if relying on PyObjC's default `__new__`.
fix
If you override `__new__` in a PyObjC-bridged class, ensure your `__init__` correctly handles object initialization, and be aware that `__init__` will not be called if you rely on PyObjC's default `__new__` for new instances.
affects: 10.3, 10.3.1+
gotchaStarting with PyObjC 12.1, Key-Value Observing (KVO) usage is automatically disabled for subclasses of `NSProxy` defined in Python. If your application relies on KVO notifications for changes in properties of such `NSProxy` subclasses, they will no longer be triggered.
fix
If KVO on Python-defined `NSProxy` subclasses is critical, you may need to implement custom observation mechanisms or reconsider your class design to avoid `NSProxy` for observable objects.
affects: 12.1+
Upgrade
Version history
12.2latest on PyPI · released May 30, 2026
Audit
Dependencies
pyobjc-corerequiredProvides the core PyObjC bridge functionality necessary for all framework wrappers.
Agent activity
10 hits · last 30 days
node
8
Amazon
1
OpenAI (training)
1
Resources
pyobjc-framework-latentsemanticmapping — pip install pyobjc-framework-latentsemanticmapping · libregistry