arrowspace 0.13.2__tar.gz → 0.13.3__tar.gz

{arrowspace-0.13.2/pyarrowspace → arrowspace-0.13.3}/Cargo.lock

@@ -92,7 +92,9 @@ dependencies = [
 
 [[package]]
 name = "arrowspace"
-version = "0.13.2"
+version = "0.13.3"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "c6a0216c0bc0fd7f7136fb2118a9df9a517f10db14a9cd987e955a85619e0cb0"
 dependencies = [
  "approx 0.5.1",
  "dashmap",
@@ -513,7 +515,7 @@ dependencies = [
 
 [[package]]
 name = "pyarrowspace"
-version = "0.13.2"
+version = "0.13.3"
 dependencies = [
  "arrowspace",
  "numpy",
@@ -762,8 +764,9 @@ checksum = "67b1b7a3b5fe4f1376887184045fcf45c69e92af734b7aaddc05fb777b6fbd03"
 
 [[package]]
 name = "smartcore"
-version = "0.4.3"
-source = "git+https://github.com/tuned-org-uk/smartcore.git?branch=main#d6e210e6ed5babafc3d11bec617e50395c8aab71"
+version = "0.4.5"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "9e569eba50db04f51f83ad1ad2186cc1cf88bb68de052177bda165f6cdcf8d81"
 dependencies = [
  "approx 0.5.1",
  "cfg-if",

{arrowspace-0.13.2/pyarrowspace → arrowspace-0.13.3}/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "pyarrowspace"
-version = "0.13.2"
+version = "0.13.3"
 edition = "2024"
 readme = "README.md"
 
@@ -14,6 +14,6 @@ name = "arrowspace"
 crate-type = ["cdylib"]
 
 [dependencies]
-arrowspace = { path = "../arrowspace-rs"}
+arrowspace = "0.13.3"
 pyo3 = { version = "*", features = ["extension-module"] }
 numpy = "0.19"

{arrowspace-0.13.2 → arrowspace-0.13.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: arrowspace
-Version: 0.13.2
+Version: 0.13.3
 Classifier: Programming Language :: Rust
 Classifier: Programming Language :: Python :: Implementation :: CPython
 Classifier: Programming Language :: Python :: Implementation :: PyPy

{arrowspace-0.13.2 → arrowspace-0.13.3}/pyproject.toml

@@ -13,4 +13,3 @@ classifiers = [
 dynamic = ["version"]
 [tool.maturin]
 features = ["pyo3/extension-module"]
-manifest-path = "pyarrowspace/Cargo.toml"

arrowspace-0.13.2/arrowspace-rs/.gitignore

@@ -1,2 +0,0 @@
-/target
-TODOs.md

arrowspace-0.13.2/arrowspace-rs/CITATION.cff

@@ -1,26 +0,0 @@
-cff-version: "1.2.0"
-authors:
-- family-names: Moriondo
-  given-names: Lorenzo
-  orcid: "https://orcid.org/0000-0002-8804-2963"
-doi: 10.5281/zenodo.17213264
-message: If you use this software, please cite our article in the
-  Journal of Open Source Software.
-preferred-citation:
-  authors:
-  - family-names: Moriondo
-    given-names: Lorenzo
-    orcid: "https://orcid.org/0000-0002-8804-2963"
-  date-published: 2025-09-27
-  doi: 10.21105/joss.09002
-  issn: 2475-9066
-  issue: 113
-  journal: Journal of Open Source Software
-  publisher:
-    name: Open Journals
-  start: 9002
-  title: "ArrowSpace: introducing Spectral Indexing for vector search"
-  type: article
-  url: "https://joss.theoj.org/papers/10.21105/joss.09002"
-  volume: 10
-title: "ArrowSpace: introducing Spectral Indexing for vector search"

arrowspace-0.13.2/arrowspace-rs/CODE_OF_CONDUCT.md

@@ -1,22 +0,0 @@
-# Code of Conduct
-
-As contributors and maintainers of this project, and in the interest of fostering an open and welcoming community, we pledge to respect all people who contribute through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, and other activities.
-
-We are committed to making participation in this project a harassment-free experience for everyone, regardless of level of experience, gender, gender identity and expression, sexual orientation, disability, personal appearance, body size, race, ethnicity, age, religion, or nationality.
-
-Examples of unacceptable behavior by participants include:
-
-* The use of sexualized language or imagery
-* Personal attacks
-* Trolling or insulting/derogatory comments
-* Public or private harassment
-* Publishing other's private information, such as physical or electronic addresses, without explicit permission
-* Other unethical or unprofessional conduct.
-
-Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct. By adopting this Code of Conduct, project maintainers commit themselves to fairly and consistently applying these principles to every aspect of managing this project. Project maintainers who do not follow or enforce the Code of Conduct may be permanently removed from the project team.
-
-This code of conduct applies both within project spaces and in public spaces when an individual is representing the project or its community.
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by opening an issue or contacting one or more of the project maintainers.
-
-This Code of Conduct is adapted from the [Contributor Covenant](http://contributor-covenant.org), version 1.2.0, available at [http://contributor-covenant.org/version/1/2/0/](http://contributor-covenant.org/version/1/2/0/)

arrowspace-0.13.2/arrowspace-rs/CONTRIBUTING.md

@@ -1,44 +0,0 @@
-# **Contributing**
-
-When contributing to this repository, please first discuss the change you wish to make via issue,
-email, or any other method with the owners of this repository before making a change.
-
-Please note we have a [code of conduct](CODE_OF_CONDUCT.md), please follow it in all your interactions with the project.
-
-## Pull Request Process
-
-1. Open a PR following the template (erase the part of the template you don't need).
-2. Pull Request can be merged in once you have the sign-off of a code owner, or if you do not have permission to do that you may request the reviewer to merge it for you.
-
-### generic guidelines
-Take a look to the conventions established by existing code:
-* Every module should come with some reference to scientific literature that allows relating the code to research. Use the `//!` comments at the top of the module to tell readers about the basics of the procedure you are implementing.
-* Every module should provide a Rust doctest, a brief test embedded with the documentation that explains how to use the procedure implemented.
-* Run `cargo doc --no-deps --open` and read the generated documentation in the browser to be sure that your changes reflects in the documentation and new code is documented.
-
-## Issue Report Process
-
-1. Go to the project's issues.
-2. Select the template that better fits your issue.
-3. Read carefully the instructions and write within the template guidelines.
-4. Submit it and wait for support.
-
-## Reviewing process
-
-1. After a PR is opened maintainers are notified
-2. Probably changes will be required to comply with the workflow, these commands are run automatically and all tests shall pass:
-    * **Formatting**: run `rustfmt src/*.rs` to apply automatic formatting
-    * **Linting**: `clippy` is used with command `cargo clippy --all-features -- -Drust-2018-idioms -Dwarnings`
-    * **Testing**: multiple test pipelines are run for different targets
-3. When everything is OK and the PR is accepted, code is merged.
-
-
-## Contribution Best Practices
-
-* Read this [how-to about Github workflow here](https://guides.github.com/introduction/flow/) if you are not familiar with.
-
-* Read this [how-to about writing a PR](https://github.com/blog/1943-how-to-write-the-perfect-pull-request) and this [other how-to about writing a issue](https://wiredcraft.com/blog/how-we-write-our-github-issues/)
-  
-* **read history**: search past open or closed issues for your problem before opening a new issue.
-
-* **testing**:  everything should work and be tested as defined in the workflow. If any is failing for non-related reasons, annotate the test failure in the PR comment.