0h3SSKJr SSKrSSKrSSKrSSKrSSKrSSKJ r \R(a SSK r SSK Jr \R"S5r"SS\R"\5r"S S \5rg) ) annotationsN) import_string)AppTc\rSrSrSrS S Sjjr\RS Sj5r\RS Sj5rS SSjjrSSjr S r g)ConfigAttributez(Makes an attribute forward to the configNcXlX lgN__name__ get_converter)selfnamers D/var/www/auris/envauris/lib/python3.13/site-packages/flask/config.py__init__ConfigAttribute.__init__s *cgr robjowners r__get__ConfigAttribute.__get__s:=rcgr rrs rrr s8;rc~UcU$URURnURbURU5nU$r )configrr)rrrrvs rrr#s? ;K ZZ &    )##B'B rc4X!RUR'gr )rr)rrvalues r__set__ConfigAttribute.__set__.s$) 4==!rr r )rstrrzt.Callable[[t.Any], T] | NonereturnNone)rr'rr'r&zte.Self)rrrz type[App]r&r)rz App | Nonerztype[App] | Noner&z T | te.Self)rrr"t.Anyr&r') r __module__ __qualname____firstlineno____doc__rtoverloadrr#__static_attributes__rrrr r sY2IM++(E+ + ZZ==ZZ;; *rr c^\rSrSrSrSSU4SjjjrSSSjjrS\RS.SSjjjr SSSjjr SSjr SSS jjr SSS jjr SSS jjrSS jrS rU=r$)Config2aaWorks exactly like a dict but provides ways to fill it from files or special dictionaries. There are two common patterns to populate the config. Either you can fill the config from a config file:: app.config.from_pyfile('yourconfig.cfg') Or alternatively you can define the configuration options in the module that calls :meth:`from_object` or provide an import path to a module that should be loaded. It is also possible to tell it to use the same module and with that provide the configuration values just before the call:: DEBUG = True SECRET_KEY = 'development key' app.config.from_object(__name__) In both cases (loading from any Python file or loading from modules), only uppercase keys are added to the config. This makes it possible to use lowercase values in the config file for temporary values that are not added to the config or to define the config keys in the same file that implements the application. Probably the most interesting way to load configurations is from an environment variable pointing to a file:: app.config.from_envvar('YOURAPPLICATION_SETTINGS') In this case before launching the application you have to set this environment variable to the file you want to use. On Linux and OS X use the export statement:: export YOURAPPLICATION_SETTINGS='/path/to/config/file' On windows use `set` instead. :param root_path: path to which files are read relative from. When the config object is created by the application, this is the application's :attr:`~flask.Flask.root_path`. :param defaults: an optional dictionary of default values cB>[TU]U=(d 05 Xlgr )superr root_path)rr5defaults __class__s rrConfig.__init__^s R("rc[RRU5nU(dU(ag[SU<S35eUR X2S9$)aLoads a configuration from an environment variable pointing to a configuration file. This is basically just a shortcut with nicer error messages for this line of code:: app.config.from_pyfile(os.environ['YOURAPPLICATION_SETTINGS']) :param variable_name: name of the environment variable :param silent: set to ``True`` if you want silent failure for missing files. :return: ``True`` if the file was loaded successfully. FzThe environment variable zv is not set and as such configuration could not be loaded. Set this variable and make it point to a configuration file)silent)osenvironget RuntimeError from_pyfile)r variable_namer:r s r from_envvarConfig.from_envvarfsTZZ^^M *+M+<=  22r)loadscnUS3n[[R5HnURU5(dM[RUnUR U5nU"U5nSU;aX@U'MTUnUR S5GtpgUHnX;a0XX'XXnM XEU'M g![ a NLf=f)a~Load any environment variables that start with ``FLASK_``, dropping the prefix from the env key for the config key. Values are passed through a loading function to attempt to convert them to more specific types than strings. Keys are loaded in :func:`sorted` order. The default loading function attempts to parse values as any valid JSON type, including dicts and lists. Specific items in nested dicts can be set by separating the keys with double underscores (``__``). If an intermediate key doesn't exist, it will be initialized to an empty dict. :param prefix: Load env vars that start with this prefix, separated with an underscore (``_``). :param loads: Pass each string value to this function and use the returned value as the config value. If any error is raised it is ignored and the value remains a string. The default is :func:`json.loads`. .. versionadded:: 2.1 ___T)sortedr;r< startswith removeprefix Exceptionsplit) rprefixrCkeyr"currentpartstailparts rfrom_prefixed_envConfig.from_prefixed_env~s481"**%C>>&))JJsOE""6*C e  3!S G99T?LU&$&GM!- "DM;&>-  sB'' B43B4c<[RRURU5n[R "S5nXl[USS9n[[UR5US5UR5 SSS5 UR%U5 g !,(df  N =f![adnU(aBUR[R[R[R 4;aSnAgSUR"S3UleSnAff=f) aUpdates the values in the config from a Python file. This function behaves as if the file was imported as module with the :meth:`from_object` function. :param filename: the filename of the config. This can either be an absolute filename or a filename relative to the root path. :param silent: set to ``True`` if you want silent failure for missing files. :return: ``True`` if the file was loaded successfully. .. versionadded:: 0.7 `silent` parameter. rrb)modeexecNF#Unable to load configuration file ()T)r;pathjoinr5types ModuleType__file__openrWcompileread__dict__OSErrorerrnoENOENTEISDIRENOTDIRstrerror from_object)rfilenamer:d config_filees rr?Config.from_pyfiles"77<<9   X &  hT*kW[--/6BAJJO+ +* !''ellELL%--%PP>qzzl!LAJ   s= B-0BB- B*&B-*B-- D7ADDDc[U[5(a [U5n[U5H'nUR 5(dM[ X5X'M) g)aUpdates the values from the given object. An object can be of one of the following two types: - a string: in this case the object with that name will be imported - an actual object reference: that object is used directly Objects are usually either modules or classes. :meth:`from_object` loads only the uppercase attributes of the module/class. A ``dict`` object will not work with :meth:`from_object` because the keys of a ``dict`` are not attributes of the ``dict`` class. Example of module-based configuration:: app.config.from_object('yourapplication.default_config') from yourapplication import default_config app.config.from_object(default_config) Nothing is done to the object before loading. If the object is a class and has ``@property`` attributes, it needs to be instantiated before being passed to this method. You should not use this function to load the actual configuration but rather configuration defaults. The actual config should be loaded with :meth:`from_pyfile` and ideally from a location not within the package because the package might be installed system wide. See :ref:`config-dev-prod` for an example of class-based configuration using :meth:`from_object`. :param obj: an import name or object N) isinstancer%rdirisuppergetattr)rrrMs rriConfig.from_objectsA@ c3  $Cs8C{{}}#C- rc[RRURU5n[ X(aSOS5nU"U5nSSS5 URW5$!,(df  N=f![ aUnU(a3UR [ R[ R4;aSnAgSURS3Ul eSnAff=f)aUpdate the values in the config from a file that is loaded using the ``load`` parameter. The loaded data is passed to the :meth:`from_mapping` method. .. code-block:: python import json app.config.from_file("config.json", load=json.load) import tomllib app.config.from_file("config.toml", load=tomllib.load, text=False) :param filename: The path to the data file. This can be an absolute path or relative to the config root path. :param load: A callable that takes a file handle and returns a mapping of loaded data from the file. :type load: ``Callable[[Reader], Mapping]`` where ``Reader`` implements a ``read`` method. :param silent: Ignore the file if it doesn't exist. :param text: Open the file in text or binary mode. :return: ``True`` if the file was loaded successfully. .. versionchanged:: 2.3 The ``text`` parameter was added. .. versionadded:: 2.0 rrUNFrXrY) r;rZr[r5r_rcrdrerfrh from_mapping)rrjloadr:textfrrms r from_fileConfig.from_filesD77<<9 ht6!1g7  %%76 !''ellELL%AA>qzzl!LAJ   s;A3 A" A3" A0,A30A33 C=5C 7C  Cc 0nUbURU5 URU5 UR5H upEUR5(dMXPU'M" g)zUpdates the config like :meth:`update` ignoring items with non-upper keys. :return: Always returns ``True``. .. versionadded:: 0.11 T)updateitemsrr)rmappingkwargsmappingsrMr"s rrwConfig.from_mapping0sQ&(   OOG $"..*JC{{}}!S +rc0nUR5HPupVURU5(dMU(aU[U5SnOUnU(aUR5nXdU'MR U$)aReturns a dictionary containing a subset of configuration options that match the specified namespace/prefix. Example usage:: app.config['IMAGE_STORE_TYPE'] = 'fs' app.config['IMAGE_STORE_PATH'] = '/var/app/images' app.config['IMAGE_STORE_BASE_URL'] = 'http://img.website.com' image_store_config = app.config.get_namespace('IMAGE_STORE_') The resulting dictionary `image_store_config` would look like:: { 'type': 'fs', 'path': '/var/app/images', 'base_url': 'http://img.website.com' } This is often useful when configuration options map directly to keyword arguments in functions or class constructors. :param namespace: a configuration namespace :param lowercase: a flag indicating if the keys of the resulting dictionary should be lowercase :param trim_namespace: a flag indicating if the keys of the resulting dictionary should not include the namespace .. versionadded:: 0.11 N)rrHlenlower)r namespace lowercasetrim_namespacer kvrMs r get_namespaceConfig.get_namespaceCsb<JJLDA<< **I()iiksG! rc`S[U5RS[RU5S3$)N< >)typerdict__repr__)rs rrConfig.__repr__ns,4:&&'qt)<(=Q??r)r5r )r5str | os.PathLike[str]r6zdict[str, t.Any] | Noner&r')F)r@r%r:boolr&r)FLASK)rLr%rCzt.Callable[[str], t.Any]r&r)rjrr:rr&r)rz object | strr&r')FT) rjrrxz0t.Callable[[t.IO[t.Any]], t.Mapping[str, t.Any]]r:rryrr&r)rzt.Mapping[str, t.Any] | Nonerr(r&r)TT)rr%rrrrr&zdict[str, t.Any])r&r%)rr)r*r+r,rrAjsonrCrRr?rir{rwrrr/ __classcell__)r7s@rr1r12s+)\-1#)#*#  ##32$;JN**;;/G; ;|@E.8< >$.T .&(.&?.& .&  .&  .&b7;3FK (NR)))-)FJ) )V@@rr1) __future__rrdrr;r\typingr-werkzeug.utilsr TYPE_CHECKINGtyping_extensionste sansio.apprTypeVarrGenericr rr1rrrrsZ" (??"IIcN*aiil*<}@T}@r