Negmas

Latest version: v0.11.3

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

Scan your dependencies

Page 7 of 19

0.9.0

Not secure
-------------

This is a major release and it is **not** backward compatible. Please reference
the upgrade guide at the upgrdade guide_.

.. _guide: https://negmas.readthedocs.io/en/latest/upgrade_guide.html

Some of the most important changes are:

* Introduces the `ModularNegotiator` and `Component` objects to simplify reuse of negotiation strategies through composition instead of inheritance.
* Restructures most of the code-base for readability.
* Completed the tutorial.
* Simplified several key methods.
* Introduced the `SAOModularNegotiator`, `MAPNegotiator`, `BOANegotiator` as basic modular negotiators for the SAO mechanism as well as reusable components like `AcceptanceStrategy`, and `OfferingStrategy`

0.8.9

Not secure
-------------

* [sao] improvement to the plot() method of SAOMechanism
* [genius] Almost complete rewriting of the genius-bridge. Now we are
compatible with genius*bridge v0.2.0
* [genius] Renaming get_genius_agents() to get_anac_agents()
* [genius] Updating TEST_FAILING_NEGOTIATORS and adding ALL_GENIUS_NEGOTIATORS,
ALL_BASIC_GENIUS_NEGOTIATORS to ginfo
* [core] Adding nash_point() to find the nash point of a set of ufuns (within
the pareto frontier)
* [bugfix] plotting SAOMechanism instances with continuous Issue spaces work
now
* [genius] Stricter GeniusNegotiator. If strict=True is given to a
GeniusNegotiator (or in an n_steps limited negotaition with strict not given
at all), more tests are incorporated to make sure that the Genius agent is
getting what it expects all the time.
* [sao] relative_time matches Genius behavior. relative_time was equal to
step/n_steps now it is (step+1)/(n_steps+1) This is only in the case of using
n_steps as a limit of a mechanism.
* [tests] Extracting long genius tests out and running genius tests in CI
* [genius] Added is_installed to GeniusBridge and genius_bridge_is_installed()
* [bugfix] Handling wrong time perception in Genius agents
* [genius] Adding wxtra warnings for common timinig problems in SAO
* A warning is now raised in either of the following cases:
1. A mechanism is created with neither a time_limit nor n_step set
2. A Genius agent tries to join a mechanism with both time_limit and
n_steps set
* We stopped using timeline.increment() inside the genius bridge and now
pass the round number (step in negmas terms) directly from negmas.
This should avoid any possibility of double counting
* [sao] Adding enforce_outcome_type to SAOMechanism
* [sao] Adding enforcement of issue value types SAOP
* [sao] Adding the ability to cast_outcome to Mechanism
* [genius] Adding relative_time to GeniusNegotiator which checks the time as perceived by the Genius Agent inside the JVM
* [genius] Improving the way tuple ouctomes are handled in GeniusNegotiator
* [tournament] Allowing truncated_mean in eval
* [cli] adding truncated_mean as a possible metric

0.8.8

Not secure
-------------

* [sao] Treating `None` as `(REJECT_OFFER, None)` in responses from counter_all()

0.8.7

Not secure
-------------

* [core] better normalization for random Linear*UFun
* [helpers] single_thread() context manager
* [bugfix] Partner params incorrectly passed in NegWorld

0.8.6

Not secure
-------------

* [core] Adding to_dict/from_dict to all ufun types
* [core] Better random LinearAdditiveUtilityFunction
* [core] better implementation of stepall and runall
* [core] implementing keep_order=False for stepall()
* [tournaments] Adding negotiation tournaments.
* [situated] shuffle_negotiations option in World
* [bugfix] SAOSyncController never loses offers

0.8.5

Not secure
-------------

* [sao] Avoiding an issue with avoid-ultimatum if all agents sent None as their first offer
* [situated] bugfix in reporting mechanism exceptions
* [helpers] Adding one-thread mode
* [situated] enable agent printing by default
* [tournament] not setting log_negotiations for forced logs

Page 7 of 19

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.