+ ]iA cs Rt^RIHtHt^RIt^RIHtHtH t H t H t H t H t HtHtHtHtHtHtHtHtHtHtHtHtHtHtHtHtHtHtH t H!t!H"t"H#t#H$t$^RI%H&t&H't'H(t(H)t)H*t*H+t+^RIH,t,H-t-H.t/^RI05^RI15^RI25^RI35^RI45^RI1t5^RI6H7t7^RI8t8]9!R4Ptt:]9!R4Pvt;]9!R4Pxt<]9!R4Pzt=]9!R4P|t>]9!R4P~t?]9!R4Pt@R#)a `pylab` is a historic interface and its use is strongly discouraged. The equivalent replacement is `matplotlib.pyplot`. See :ref:`api_interfaces` for a full overview of Matplotlib interfaces. `pylab` was designed to support a MATLAB-like way of working with all plotting related functions directly available in the global namespace. This was achieved through a wildcard import (``from pylab import *``). .. warning:: The use of `pylab` is discouraged for the following reasons: ``from pylab import *`` imports all the functions from `matplotlib.pyplot`, `numpy`, `numpy.fft`, `numpy.linalg`, and `numpy.random`, and some additional functions into the global namespace. Such a pattern is considered bad practice in modern python, as it clutters the global namespace. Even more severely, in the case of `pylab`, this will overwrite some builtin functions (e.g. the builtin `sum` will be replaced by `numpy.sum`), which can lead to unexpected behavior. )flatten silent_listN)date2numnum2date datestr2numdrange DateFormatter DateLocator RRuleLocator YearLocator MonthLocatorWeekdayLocator DayLocator HourLocator MinuteLocator SecondLocatorrruleMOTUWETHFRSASUYEARLYMONTHLYWEEKLYDAILYHOURLYMINUTELYSECONDLY relativedelta)detrenddetrend_linear detrend_mean detrend_nonewindow_hanning window_none)cbookmlabpyplot)Z*Zbuiltins)AZ__doc__Zmatplotlib.cbookrrZ matplotlibZmplZmatplotlib.datesrrrrrrrr r r r r rrrrrrrrrrrrrrrrrrZmatplotlib.mlabr r!r"r#r$r%r&r'r(ZpltZmatplotlib.pyplotZnumpyZ numpy.fftZ numpy.randomZ numpy.linalgZnpZnumpy.maZmaZdatetimeZ __import__ZbytesZabsZboolZmaxZminZpowZround)Z7/usr/lib64/python3.14/site-packages/matplotlib/pylab.pyr*s.221 :$$  *""      :$$r)