diff --git a/.github/workflows/pypi-publish.yml b/.github/workflows/pypi-publish.yml index 8bbaa5d..c248f23 100644 --- a/.github/workflows/pypi-publish.yml +++ b/.github/workflows/pypi-publish.yml @@ -1,11 +1,3 @@ -# This workflow will upload a Python Package using Twine when a release is created -# For more information see: https://docs.github.com/en/actions/automating-builds-and-tests/building-and-testing-python#publishing-to-package-registries - -# This workflow uses actions that are not certified by GitHub. -# They are provided by a third-party and are governed by -# separate terms of service, privacy policy, and support -# documentation. - name: Upload Python Package To pypi on: diff --git a/.github/workflows/run-tests.yml b/.github/workflows/run-tests.yml index 49905b8..9751347 100644 --- a/.github/workflows/run-tests.yml +++ b/.github/workflows/run-tests.yml @@ -1,6 +1,3 @@ -# This workflow will install Python dependencies, run tests and lint with a single version of Python -# For more information see: https://docs.github.com/en/actions/automating-builds-and-tests/building-and-testing-python - name: Run Tests on: [push, pull_request] @@ -14,7 +11,7 @@ jobs: runs-on: ubuntu-latest strategy: matrix: - python-version: ["3.10", "3.11"] + python-version: ["3.10", "3.11", '3.12'] steps: - uses: actions/checkout@v3 - name: Set up Python ${{ matrix.python-version }} diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md index 3cc3577..2f85f92 100644 --- a/CODE_OF_CONDUCT.md +++ b/CODE_OF_CONDUCT.md @@ -1,60 +1,3 @@ # Code of Conduct -## Our Pledge - -In the interest of fostering an open and welcoming environment, -we as contributors and maintainers pledge to make participation in our project and our community a harassment-free experience for everyone, -regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, -personal appearance, race, religion, or sexual identity and orientation. - -## Our Standards - -Examples of behavior that contributes to creating a positive environment include: - -- 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 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 both within project spaces and in public spaces when an individual is representing the project or its community. -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. - -## Enforcement - -Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team -at [quill@craftsman.lol](mailto:quill@craftsman.lol). -The project team will review and investigate all complaints and will respond in a way that it deems 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](https://www.contributor-covenant.org), -version 1.4, available -at [https://www.contributor-covenant.org/version/1/4/code-of-conduct.html](https://www.contributor-covenant.org/version/1/4/code-of-conduct.html) - -For answers to common questions about this code of conduct, -see [https://www.contributor-covenant.org/faq](https://www.contributor-covenant.org/faq) \ No newline at end of file +FindSimilar [Code Of Conduct](https://github.com/findsimilar/community/blob/main/CODE_OF_CONDUCT.md) \ No newline at end of file diff --git a/GOVERNANCE.md b/GOVERNANCE.md new file mode 100644 index 0000000..f968a22 --- /dev/null +++ b/GOVERNANCE.md @@ -0,0 +1,3 @@ +# Governance + +FindSimilar [Governance](https://github.com/findsimilar/community/blob/main/GOVERNANCE.md) \ No newline at end of file diff --git a/README.md b/README.md index 40896e8..4613451 100644 --- a/README.md +++ b/README.md @@ -4,7 +4,7 @@ # FindSimilar -> User-friendly library to find similar objects +User-friendly library to find similar objects * [To get acquainted][get_acquanted] * [Mission Statement][mission_statement] diff --git a/SECURITY.md b/SECURITY.md index b2130e5..1aaa0b9 100644 --- a/SECURITY.md +++ b/SECURITY.md @@ -1,8 +1,3 @@ # Security Policy -## Vulnerability Reporting -We provide a clear process for reporting security vulnerabilities. - -If you discover a security issue, please **do not** create an issue on GitHub. -Instead, please email us at [quill@craftsman.lol](mailto:quill@craftsman.lol). -We will acknowledge your report, conduct an investigation, and work on a resolution. \ No newline at end of file +FindSimilar [Security](https://github.com/findsimilar/community/blob/main/SECURITY.md) \ No newline at end of file diff --git a/SUPPORT.md b/SUPPORT.md new file mode 100644 index 0000000..18bb775 --- /dev/null +++ b/SUPPORT.md @@ -0,0 +1,3 @@ +# Support + +FindSimilar [Support](https://github.com/findsimilar/community/blob/main/SUPPORT.md) \ No newline at end of file diff --git a/dev_requirements.txt b/dev_requirements.txt index b18540f..0033644 100644 --- a/dev_requirements.txt +++ b/dev_requirements.txt @@ -1,5 +1,6 @@ -pytest-cov==4.1.0 -yamllint==1.32.0 -pylint==2.17.5 -black==23.9.0 -build==1.0.3 \ No newline at end of file +pytest +pytest-cov +yamllint +pylint +black +build \ No newline at end of file diff --git a/find_similar/calc_models.py b/find_similar/calc_models.py index 6a1e613..7e8cec5 100644 --- a/find_similar/calc_models.py +++ b/find_similar/calc_models.py @@ -15,7 +15,7 @@ class Item(BaseModel): id_shop: int id_base_item: Optional[int] cos: Optional[float] = 0 - token_set: Optional[set] + token_set: Optional[set] = {} def __eq__(self, other): return self.id == other.id_base_item diff --git a/requirements.txt b/requirements.txt index b5aaca3..3cf818b 100644 Binary files a/requirements.txt and b/requirements.txt differ