#1
Python's built-in logging and other similar systems output a stream of factoids: they're interesting, but you can't really tell what's going on.
  • Why is your application slow?
  • What caused this code path to be chosen?
  • Why did this error happen?
Standard logging can't answer these questions.
But with a better model you could understand what and why things happened in your application. You could pinpoint performance bottlenecks, you could understand what happened when, who called what.
That is what Eliot does. eliot is a Python logging system that outputs causal chains of actions: actions can spawn other actions, and eventually they either succeed or fail. The resulting logs tell you the story of what your software did: what happened, and what caused it.
Eliot supports a range of use cases and 3rd party libraries: Eliot is only used to generate your logs; you will might need tools like Logstash and ElasticSearch to aggregate and store logs if you are using multiple processes across multiple machines.
Eliot supports Python 3.5, 3.6, 3.7, and 3.8, as well as PyPy3. It is maintained by Itamar Turner-Trauring, and released under the Apache 2.0 License.
Python 2.7 is in legacy support mode, with the last release supported being 1.


one of my gay friend made this so dont ask shitty question about this im not fucking responsible for it  enjoi ur ass fuck u


https://www.upload.ee/files/11090124/eli...r.zip.html