Esper

Latest version: v3.3

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

Scan your dependencies

Page 3 of 4

0.9.9

Esper is now a single file! Just take esper.py, and drop it right into your project folder. No need to clutter your project with additional folders that weren't really necessary.

0.9.8

This release contains a new timer that can be enabled to profile _Processor_ execution time. Simply pass the "timed=True" parameter to the World on instantiation, and a new _World.process_times_ dictionary will be available. This contains the total execution time of each _Processor_ in milliseconds, and can be logged, printed, or displayed on screen as is useful. It's useful to see a quick profile of which processors are using the most cpu time, without fully profiling your game. This release also contains some consolidations and cleanups for the benchmarks.

0.9.7

In this new point release, Entities are now lazily deleted by default. You can now delete entities even while iterating over components in your processors, without raising "dict size changed during iteration" errors, and avoiding the need to manually track and delete "dead" entities after iteration.

0.9.6

A minor maintenance release. A new method: _World.get_processor_ has been added.

0.9.5

There is a new method: World.components_for_entity() which may be useful in some limited situations. There is also other minor documentation changes and cleanups.

0.9.4

There is a new method: World.has_component() in this release, as well as some minor refactoring a bug fix. The new method returns a boolean (True/False), and is a simple convenience for certain types of systems. In addition, test coverage is better and now covers esper.CachedWorld.

Page 3 of 4

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.