{:iA SrSSKJrJr SSKrSSKJrJrJ r J r J r J r J r JrJrJrJrJrJrJrJrJrJrJrJrJrJrJrJrJrJrJ r J!r!J"r"J#r#J$r$ SSK%J&r&J'r'J(r(J)r)J*r*J+r+ SSKJ,r,J-r-J.r/ SSK07 SSK17 SSK27 SSK37 SSK47 SSK1r5SSK6J7r7 SSK8r8\9"S5Rtr:\9"S5Rvr;\9"S5Rxr<\9"S5Rzr=\9"S5R|r>\9"S5R~r?\9"S5Rr@g) 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)*builtins)A__doc__matplotlib.cbookrr matplotlibmplmatplotlib.datesrrrrr r r r r rrrrrrrrrrrrrrrrrrr r!r"matplotlib.mlabr#r$r%r&r'r(r)r*r+pltmatplotlib.pyplotnumpy numpy.fft numpy.random numpy.linalgnpnumpy.mamadatetime __import__bytesabsboolmaxminpowroundS/srv/projetos/modelo_ml_acdoc/venv/lib/python3.13/site-packages/matplotlib/pylab.pyrIs.221 :$$  *""      :$$rG