semvec/pypi-packages huggingface dataset:
interzoid-full-name-match-score 1.0.1
Provides an AI-based match score as to how likely two person names are the same.
Requires Python: >=3.7

## interzoid_full_name_match_score

Python package for generating a match score of two individual person names from 0-100, where 100 is the highest matching score, on how closely two individual full names are likely to be a match. The scoring is based on a series of tests, algorithms, AI, and an ever-growing and improving body of Machine Learning-based generated knowledge. As the context of the data is known, in this case individual person names, it performs far better than generic string comparison algorithms.

### Usage

To generate the match score, you will need the following information:

- an API License key, available at https://www.interzoid.com
- two individual full names to compare

An API is called by the package to access the Cloud server that performs the comparison and provides the score.

Begin by importing the package:

    from interzoid_full_name_match_score import full_name_match_score

Then, provide the information into the get_score() method:

    score, credits, http_code, msg = full_name_match_score.get_score('YOUR-API-KEY','Jim Smith','Mr. James Smythe')

    #200 is the HTTP status for OK
    if http_code == 200:  
        print(score, msg, credits)
    else:
        print(score, "error:", http_code, msg, credits)

The return values will be the generated match comparison score (0-100), how many remaining credits on your API license key, an http code, and a message (OK or Error). The score allows you to set a score threshold in your own logic for your specific case, for example, any score higher than 50 can be considered a "match" (or 60, 70, etc.)

Examples:

    "James Kelly", "Jim Kelly"  ->  85

    "Mr Robert J McCarthy", "Bob Macarthy"  ->  80
test-students-code 1.0.0
This repository contains a custom testing framework for Python students code.
Requires Python: >=3.7
Keywords: education,framework,python,python3,python3.7,python3.8,python3.9,school,students,test,testing

# Python Student Testing Framework

## Introduction

Welcome to the Python Student Testing Framework! This README provides a brief overview of what the framework is and how to use it. The framework is designed for instructors and TAs to easily test and grade students' Python code.

## Features

- Automated testing of students' code against a set of test cases
- Support for multiple test cases and multiple functions
- Ability to define custom tests and assertions
- Clear and detailed feedback for students on test results

## Installation

To use the Python Student Testing Framework, you will need to have Python installed on your machine. Then, simply clone the repository


## Contributing

The Python Student Testing Framework is an open-source project and contributions are welcome. 

## License

The Python Student Testing Framework is released under the MIT license. See the LICENSE file for more information.

## Contact

If you have any questions or issues, please create a GitHub issue or reach out to the project maintainers at marc-olivier.derouin@poulet-frit.com
bwtrack 1.4
A small particle tracking package that detects black and white particles.
Requires Python: >=3.9

# bwtrack

This repo hosts the code for tracking black and white particles in the mini interfacial rheometer developed by my friend Qiaoge.

乔哥牛逼！

I've got very timely and insightful feedbacks from Qiaoge, and I'm optimistic that the method here will become useful for other purposes eventually. So I create this repo to record the progress of the core functions. 

I've always been fascinated about how a software package is made available to users from general public. I have downloaded many Python packages from PyPI. It is part of my habit to check out if there are existing projects that aim to solve my problem, and I'm more than happy to go through the documentations and see if there is a chance to participate in the project.

I've also been interested in publishing the code I write for other people to use. This is the key motivation for me to write code in a maintainable way, with clear comments and documentations. I tried to convince other people to try my code, but every time I have a feeling that I'm confusing other people with some functions in my local library, which do not exist on their computer. The problem is, I import my own functions as if they are from available packages, but they are not. For example, I often write in my code

```python
from myImageLib import readdata
```

and this almost always cause problem to other people. Because they will get an error "myImageLib not found". Users with some Python experience will try

```console
pip install myImageLib
```

only to find there is no package called this. Then they come ask me, and I explain them: you need to go to my GitHub and download this piece of code to your computer, and set this directory as your Python path. Not many steps, but can be confusing at each step, and ... not easy. 

Imagine, if I can make myImageLib a PyPI package, and state it as a requirement of other code I give to users, things can be much more straightforward!

So this code, along with myImageLib, will be the first package I'm going to publish. The goal is to make it downloadable through `pip`, and work properly right after downloading.