| Server IP : 85.214.239.14 / Your IP : 18.226.34.148 Web Server : Apache/2.4.62 (Debian) System : Linux h2886529.stratoserver.net 4.9.0 #1 SMP Tue Jan 9 19:45:01 MSK 2024 x86_64 User : www-data ( 33) PHP Version : 7.4.18 Disable Function : pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_get_handler,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,pcntl_async_signals,pcntl_unshare, MySQL : OFF | cURL : OFF | WGET : ON | Perl : ON | Python : ON | Sudo : ON | Pkexec : OFF Directory : /proc/self/root/usr/share/doc/python3-resolvelib/examples/visualization/ |
Upload File : |
# Visualization Reporter This directory contains a reporter, that can be used to visualize how the resolution algorithm is exploring the dependency graph, by exposing the information about the process that is being provided by the reporter. ## Usage There's 2 ways to try out the reporter defined in this directory: 1. With `run.py`, based on an output from `reporter_demo.py`. This demonstrates how to "record" a resolution run, and "play it back" later to generate the visualization. ```sh-session $ # In the examples/ directory $ python reporter_demo.py > foo.txt $ python visualization/run.py foo.txt out.html ... ``` 2. With `run_pypi.py`, that uses the `pypi_wheel_provider.py` example code. This demonstrates how a visualization can be generated while running the resolver. ```sh-session $ # In the examples/ directory $ python visualization/run_pypi.py out.html ... ``` > NOTE: This code mainly serves to demonstrate what can be done with > resolvelib's Reporter API. It likely contains bugs and there's definitely a > lot of scope for improvement here (more interactive visualization, making it > easier to look at and work with larger dependency graphs and more).