swh.graph.libs 9.0.0__tar.gz

swh_graph_libs-9.0.0/.cargo/config.toml

@@ -0,0 +1,2 @@
+[build]
+rustflags = ["-C", "target-cpu=native"]

swh_graph_libs-9.0.0/.copier-answers.yml

@@ -0,0 +1,11 @@
+# Changes here will be overwritten by Copier
+_commit: v0.3.5
+_src_path: https://gitlab.softwareheritage.org/swh/devel/swh-py-template.git
+description: Rust libraries for the Software Heritage graph service
+distribution_name: swh-graph-libs
+have_cli: false
+have_workers: false
+package_root: swh/graph/libs
+project_name: swh.graph.libs
+python_minimal_version: '3.9'
+readme_format: rst

swh_graph_libs-9.0.0/.git-blame-ignore-revs

@@ -0,0 +1,5 @@
+# Enable black
+4c3c6d839b642009ba1eeee4acf4a58f209580e6
+
+# python: Reformat code with black 22.3.0
+1efea9bb9035e1d04191f8cd25a3f7ff9ad6d8f3

swh_graph_libs-9.0.0/.gitignore

@@ -0,0 +1,21 @@
+*.egg-info/
+*.pyc
+.coverage
+.eggs/
+.hypothesis
+.mypy_cache
+.tox
+__pycache__
+build/
+dist/
+# these are symlinks created by a hook in swh-docs' main sphinx conf.py
+docs/README.rst
+docs/README.md
+# this should be a symlink for people who want to build the sphinx doc
+# without using tox, generally created by the swh-env/bin/update script
+docs/Makefile.sphinx
+
+target/
+
+# These are backup files generated by rustfmt
+**/*.rs.bk

swh_graph_libs-9.0.0/.mailmap

@@ -0,0 +1,3 @@
+Andrey Starodubtsev <andreystar2403@gmail.com>
+Léni Gauffier <lenigauffier@gmail.com>
+Valentin Lorentz <vlorentz@softwareheritage.org>

swh_graph_libs-9.0.0/.pre-commit-config.yaml

@@ -0,0 +1,68 @@
+repos:
+  - repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v6.0.0
+    hooks:
+      - id: trailing-whitespace
+      - id: check-json
+      - id: check-yaml
+
+  - repo: https://github.com/python/black
+    rev: 25.9.0
+    hooks:
+      - id: black
+
+  - repo: https://github.com/PyCQA/isort
+    rev: 6.1.0
+    hooks:
+      - id: isort
+
+  - repo: https://github.com/pycqa/flake8
+    rev: 7.3.0
+    hooks:
+      - id: flake8
+        additional_dependencies: [flake8-bugbear==24.12.12, flake8-pyproject]
+
+  - repo: https://github.com/codespell-project/codespell
+    rev: v2.4.1
+    hooks:
+      - id: codespell
+        name: Check source code spelling
+        args:
+          - "-L te,wth,alledges,afterall,mmapped,crate,beling,ser,\
+            implementor,implementors"
+          - "--skip=rust/tests/data/*"
+        stages: [pre-commit]
+      - id: codespell
+        name: Check commit message spelling
+        stages: [commit-msg]
+
+  - repo: local
+    hooks:
+      - id: mypy
+        name: mypy
+        entry: mypy
+        args: [swh]
+        pass_filenames: false
+        language: system
+        types: [python]
+      - id: twine-check
+        name: twine check
+        description: call twine check when pushing an annotated release tag
+        entry: bash -c "ref=$(git describe) &&
+          [[ $ref =~ ^v[0-9]+\.[0-9]+\.[0-9]+$ ]] &&
+          (python3 -m build --sdist && twine check $(ls -t dist/* | head -1)) || true"
+        pass_filenames: false
+        stages: [pre-push]
+        language: python
+        additional_dependencies: [twine, build]
+
+  - repo: https://github.com/doublify/pre-commit-rust
+    rev: v1.0
+    hooks:
+      - id: fmt
+      - id: cargo-check
+        args: ["--all-features"]
+      - id: clippy
+        args: ["--all-features", "--all-targets", "--", "--deny", "warnings"]
+
+exclude: ^swh/graph/grpc/

swh_graph_libs-9.0.0/AUTHORS

@@ -0,0 +1,3 @@
+Copyright (C) 2019 The Software Heritage developers
+
+See http://www.softwareheritage.org/ for more information.

swh_graph_libs-9.0.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,78 @@
+# Software Heritage Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as Software
+Heritage contributors and maintainers pledge to making participation in our
+project and our community a harassment-free experience for everyone, regardless
+of age, body size, disability, ethnicity, sex characteristics, gender identity
+and expression, level of experience, education, socioeconomic status,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+  advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+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, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies within all project spaces, and it also applies when
+an individual is representing the project or its community in public spaces.
+Examples of representing a project or community include using an official
+project e-mail address, posting via an official social media account, or acting
+as an appointed representative at an online or offline event. Representation of
+a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at `conduct@softwareheritage.org`. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an
+incident.  Further details of specific enforcement policies may be posted
+separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

swh_graph_libs-9.0.0/CONTRIBUTORS

@@ -0,0 +1,7 @@
+Andrey Starodubtsev
+Hakim Baaloudj
+Léni Gauffier
+Pratyush Desai
+Rafael Passos
+Thibault Allançon
+Théo Zimmermann