Repository navigation
0.6.3: arraybridge 0.5.0 - #42
Merged
Merged
Conversation
storage_numpy_array asks the library that made the array to download it (ArrayLibrary.of(data).to_numpy(data)); it no longer names a device, and the removed gpu_id keyword is gone. polystore.constants no longer re-exports CPU_MEMORY_TYPES, GPU_MEMORY_TYPES and SUPPORTED_MEMORY_TYPES, which arraybridge 0.5.0 removed; nothing read them. polystore.MemoryType stays. polystore.streaming.handlers is deleted: it imported metaclass_registry.lazy, which metaclass-registry 0.4 (already required) does not have, so the package could not be imported and nothing imported it. A new test imports every module in a child interpreter and fails on any first-party import error. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PolyStore 0.6.2 cannot be imported with arraybridge 0.5.0 (
polystore.constantsimports removed names) and every non-NumPy write would raise (gpu_id=0to a NumPy target).array_payload.storage_numpy_array:ArrayLibrary.of(data).to_numpy(data). The library that made the array downloads it; no device is named. Parameter annotatedobjectinstead ofAny.constants.py: the re-exports ofCPU_MEMORY_TYPES,GPU_MEMORY_TYPES,SUPPORTED_MEMORY_TYPESare deleted. Nothing in PolyStore, OpenHCS or pyqt-reactive read them, so there is no question to redirect to the library family.polystore.streaming.handlersdeleted (327 lines): it importsmetaclass_registry.lazy, absent from the already-required metaclass-registry 0.4, so it was unimportable and unreferenced. Found by the new import test.tests/test_every_module_imports.py: imports every module in a child interpreter; any first-party import error fails.arraybridge>=0.5.0,<0.6;uv.lockregenerated (uv lock --checkclean).Local, fresh Python 3.12 venv from PyPI (arraybridge 0.5.0): 600 passed, 5 skipped; with the torch CPU wheel added: 601 passed, 4 skipped. Baseline on main with arraybridge 0.4.1: 598 passed, 5 skipped.
🤖 Generated with Claude Code