Matching

Latest version: v1.4.3

Safety actively analyzes 626604 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 3 of 3

1.0.2

- Individuals forget the names of others one at a time rather than all instances
at once as previously.
- Add citation file.

1.0.1

- Update travis.yml to stop failures. Dodgy support for Python <3.6.
- Add new badges.

1.0

The main changes are as follows:

- Instead of passing dictionaries to an algorithm function, lists of
`matching.Player` instances must be created for the two matching parties.

- Each of these instances have a few attributes but, most importantly, they take
a name (this should be unique to the party) and a `list` (or `tuple`) ranking
their preferences of the names of the other party's members.

- With these lists of `Player` instances, each type of matching game now has its
own solver class (e.g. the hospital-resident assignment problem uses
`matching.HospitalResident`) with various methods to solve the game and then
check the stability/validity of a matching.

Further details given in new `README.rst`.

0.1

First release. Two main algorithm functions for SM and HR.

Page 3 of 3

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.