python (3.11.7)
eVO d Z ddlZddlZddlZddlZddlZddlZddlmZm Z m
Z
mZmZm
Z
mZmZmZmZmZmZmZ dZ ej eed eee
eeeeh Z e n
# e$ r i ZY nw xY wd Z G d d e Zeee fZ!d
Z"d Z#d Z$d
Z%ddZ&ddZ'e'Z(d dZ) G d d Z* G d de* Z+d Z,d!dZ-ej. dk r G d d Z/ G d de* Z0dS dS )"a Basic infrastructure for asynchronous socket service clients and servers.
There are only two ways to have a program on a single processor do "more
than one thing at a time". Multi-threaded programming is the simplest and
most popular way to do it, but there is another very different technique,
that lets you have nearly all the advantages of multi-threading, without
actually using multiple threads. it's really only practical if your program
is largely I/O bound. If your program is CPU bound, then pre-emptive
scheduled threads are probably what you really need. Network servers are
rarely CPU-bound, however.
If your operating system supports the select() system call in its I/O
library (and nearly all do), then you can use it to juggle multiple
communication channels at once; doing other work while your I/O is taking
place in the "background." Although this strategy can seem strange and
complex, especially at first, it is in many ways easier to understand and
control than multi-threaded programming. The module documented here solves
many of the difficult problems for you, making the task of building
sophisticated high-performance network servers and clients a snap.
N)
EALREADYEINPROGRESSEWOULDBLOCK
ECONNRESETEINVALENOTCONN ESHUTDOWNEISCONNEBADFECONNABORTEDEPIPEEAGAIN errorcodeznThe {name} module is deprecated and will be removed in Python {remove}. The recommended replacement is asyncio) )removec t j | S # t t t f$ r | t
v rt
| cY S d| z cY S w xY w)NzUnknown error %s)osstrerror
ValueError
OverflowError NameErrorr )errs </BuggyBox/python/3.11.7/bootstrap/lib/python3.11/asyncore.py _strerrorr I se '{3
y1 '