old-parkingkoncept/parkingkonceptvenv/lib/python3.7/site-packages/click/__pycache__/utils.cpython-37.pyc

B
<00>/<2F>]<5D>=<00>@s2
dd
lZdd
l
Z
ddlmZ
ddlmZmZmZmZm	Z	m
Z
mZmZm
Z
mZmZmZmZmZmZmZ
e
svddlmZ
ner<>ddlmZmZmZ
e	eefZdd<08>Zd	d
<EFBFBD>Zdd<0C>Zd(dd<0F>
Z Gdd<11>de!<21>Z"Gdd<13>de!<21>Z#d)dd<17>
Z$dd<19>Z%d*dd<1C>
Z&d+dd<1F>
Z'd d!<21>Z(d,d"d#<23>
Z)d-d$d%<25>
Z*Gd&d'<27>d'e!<21>Z+d
S).<2E>N<>
)
<01>resolve_color_default)<10>	text_type<70>open_stream<61>get_filesystem_encoding<6E>
get_streerror<6F>string_types<65>PY2<59>binary_streams<6D>text_streams<6D>filename_to_ui<75>auto_wrap_for_ansi<73>
strip_ansi<EFBFBD>should_strip_ansi<73>_default_text_stdout<75>_default_text_stderr<72>is_bytes<65>WIN)
<01>_find_binary_writer)<03>_get_windows_argv<67>
_hash_py_argv<67>_initial_argv_hashc

Csd
<01>|<00>
<01><00>
<01><02>S)N<>
-)<03>join<69>split<69>lower)
<01>name<6D>r<00>./tmp/pip-install-c3kgu56x/click/click/utils.py<70>	_posixifys
rc
s<00>f
d
d<02>}
|
S)z0Wraps a function so that it swallows exceptions.cs$y
<EFBFBD>||
<01>
Stk
r


YnXdS)
N)
<01>	Exception)<02>args<67>kwargs)
<01>funcrr<00>wrappers




zsafecall.<locals>.wrapperr)r#r$r)
r#r<00>safecallsr%c

Cs<t|t
<01>r4y|<00>t<03><00>
Stk
r2


|<00>d
d<02>SXt|<00>
S)z%Converts a value into a valid string.zutf-8<>replace)<06>
isinstance<EFBFBD>bytes<65>decoder<00>UnicodeErrorr)
<01>valuerrr<00>make_str#s





r,<00>-cCs<>|<00><00>}d
}g}d}xz|D]r}|dd<04>dkr2d}|rBdt
|<06>
pHt
|<06>
}|||
krf|<04>d<08>

d}n|rt|<04>d	<09>

|<04>|<06>

|r<>P||7}qWd
<EFBFBD>|<04>
S)z*Return a condensed version of help string.r
F<><46><EFBFBD><EFBFBD><EFBFBD>N<EFBFBD>
.Trz...<2E>
 <20>)r<00>len<65>appendr)<08>help<6C>
max_length<EFBFBD>words<64>total_length<74>result<6C>done<6E>wordZ
new_lengthrrr<00>make_default_short_help-s$

















r;c@sZeZ
dZd
Zddd<07>
Zdd	<09>Zd
d<0B>Zdd
<0A>Zdd<0F>Zdd<11>Z	dd<13>Z
dd<15>Zdd<17>ZdS)<19>LazyFilez<65>A lazy file works like a regular file but it does not fully open
    the file but it does perform some basic checks early to see if the
    filename parameter does make sense.  This is useful for safely opening
    files for writing.
    <20>
rN<72>strictFcCsd|
|_||_
||_||_||_|
d
kr>t|
|||<04>\|_|_n"d|krTt|
|<02><02>	<09>
d|_d|_dS)Nrr=T)
r<00>mode<64>encoding<6E>errors<72>atomicr<00>_f<5F>should_close<73>open<65>close)<06>self<6C>filenamer?r@rArBrrr<00>__init__Ms







zLazyFile.__init__cCst|<00>
<01>|
<01>S)
N)<02>getattrrE)rGrrrr<00>__getattr__as
zLazyFile.__getattr__c

Cs$|jdk	rt
|j<00>
Sd
|j|jfS)Nz<unopened file %r %s>)rC<00>reprrr?)
rGrrr<00>__repr__ds




zLazyFile.__repr__c

Cs<>|jd
k	r|jSy&t
|j|j|j|j|jd<02>\}
|_WnDtt	fk
rz
}
z"ddl
m}
||jt|<02>
d<05><02>
Wd
d
}~XYnX|
|_|
S)z<>Opens the file if it's not yet open.  This call might fail with
        a :exc:`FileError`.  Not handling this error will produce an error
        that Click shows.
        N)
rBr)
<01>	FileError)
Zhint)
rCrrr?r@rArBrD<00>IOError<6F>OSError<6F>
exceptionsrNr)rG<00>rv<72>
erNrrrrEis










$

z
LazyFile.openc

Cs|jd
k	r|j<00>
<01>
d
S)z+Closes the underlying file, no matter what.N)rCrF)
rGrrrrF{s

zLazyFile.closec

Cs|jr|<00>
<01>
d
S)z<>This function only closes the file if it was opened by the lazy
        file wrapper.  For instance this will never close stdin.
        N)rDrF)
rGrrr<00>close_intelligently<6C>s
zLazyFile.close_intelligentlyc


Cs|S)
Nr)
rGrrr<00>	__enter__<5F>s
zLazyFile.__enter__cCs|<00><00>
dS)
N)
rT)rG<00>exc_type<70>	exc_value<75>tbrrr<00>__exit__<5F>s
zLazyFile.__exit__c

Cs|<00><00>
t
|j<02>
S)
N)rE<00>iterrC)
rGrrr<00>__iter__<5F>s

zLazyFile.__iter__)r=Nr>F)
<0A>__name__<5F>
__module__<EFBFBD>__qualname__<5F>__doc__rIrKrMrErFrTrUrYr[rrrrr<Fs

r<c@s<eZ
dZd
d<02>Zdd<04>Zdd<06>Zdd<08>Zd	d
<EFBFBD>Zdd<0C>Zd
S)<0E>KeepOpenFilecCs
|
|_dS)
N)
<01>_file)rG<00>filerrrrI<00>s
zKeepOpenFile.__init__cCst|j
|
<01>S)
N)rJra)rGrrrrrK<00>s
zKeepOpenFile.__getattr__c


Cs|S)
Nr)
rGrrrrU<00>s
zKeepOpenFile.__enter__c
CsdS)
Nr)rGrVrWrXrrrrY<00>s
zKeepOpenFile.__exit__c

Cs
t|j
<01>
S)
N)rLra)
rGrrrrM<00>s
zKeepOpenFile.__repr__c

Cs
t|j
<01>
S)
N)rZra)
rGrrrr[<00>s
zKeepOpenFile.__iter__N)	r\r]r^rIrKrUrYrMr[rrrrr`<00>sr`TFcCs<>|
d
kr|rt<00>}
nt
<01>}
|d
k	r4t|t<03>s4t|<00>
}|r\|p>d}t|t<04>rT|d7}n|d7}|r<>ts<>t|<00>
r<>t|
<01>
}|d
k	r<>|
<01><08>
|<05>	|<00>

|<05><08>
d
S|r<>t|<00>
s<>t
|<04>
}t|
|<04>r<>t|<00>
}n"t
r<>td
k	r<>t|
<01>
}
n|s<>t|<00>
}|r<>|
<01>	|<00>

|
<01><08>
d
S)aPrints a message plus a newline to the given file or stdout.  On
    first sight, this looks like the print function, but it has improved
    support for handling Unicode and binary data that does not fail no
    matter how badly configured the system is.

    Primarily it means that you can print binary data as well as Unicode
    data on both 2.x and 3.x to the given file in the most appropriate way
    possible.  This is a very carefree function in that it will try its
    best to not fail.  As of Click 6.0 this includes support for unicode
    output on the Windows console.

    In addition to that, if `colorama`_ is installed, the echo function will
    also support clever handling of ANSI codes.  Essentially it will then
    do the following:

    -   add transparent handling of ANSI color codes on Windows.
    -   hide ANSI codes automatically if the destination file is not a
        terminal.

    .. _colorama: https://pypi.org/project/colorama/

    .. versionchanged:: 6.0
       As of Click 6.0 the echo function will properly support unicode
       output on the windows console.  Not that click does not modify
       the interpreter in any way which means that `sys.stdout` or the
       print statement or function will still not provide unicode support.

    .. versionchanged:: 2.0
       Starting with version 2.0 of Click, the echo function will work
       with colorama if it's installed.

    .. versionadded:: 3.0
       The `err` parameter was added.

    .. versionchanged:: 4.0
       Added the `color` flag.

    :param message: the message to print
    :param file: the file to write to (defaults to ``stdout``)
    :param err: if set to true the file defaults to ``stderr`` instead of
                ``stdout``.  This is faster and easier than calling
                :func:`get_text_stderr` yourself.
    :param nl: if set to `True` (the default) a newline is printed afterwards.
    :param color: controls if the terminal supports ANSI colors or not.  The
                  default is autodetection.
    Nr1<00>

<EFBFBD>

)rrr'<00>echo_native_typesrr	rr<00>flush<73>writerrrrr
)<06>messagerb<00>nl<6E>err<72>color<6F>binary_filerrr<00>echo<68>s</




























rmc
Cs$t<00>
|<00>
}
|
d
krtd|<00>
<01>
|
<01>S)a<>
Returns a system stream for byte processing.  This essentially
    returns the stream from the sys module with the given name but it
    solves some compatibility issues between different Python versions.
    Primarily this function is necessary for getting binary streams on
    Python 3.

    :param name: the name of the stream to open.  Valid names are ``'stdin'``,
                 ``'stdout'`` and ``'stderr'``
    NzUnknown standard stream %r)r
<00>get<65>	TypeError)r<00>openerrrr<00>get_binary_stream
s




rqr>cCs(t<00>
|<00>
}|d
krtd|<00>
<01>
||
|<02>S)a<>
Returns a system stream for text processing.  This usually returns
    a wrapped stream around a binary stream returned from
    :func:`get_binary_stream` but it also can take shortcuts on Python 3
    for already correctly configured streams.

    :param name: the name of the stream to open.  Valid names are ``'stdin'``,
                 ``'stdout'`` and ``'stderr'``
    :param encoding: overrides the detected default encoding.
    :param errors: overrides the default error mode.
    NzUnknown standard stream %r)rrnro)rr@rArprrr<00>get_text_stream
s



rrr=cCs<|rt||
|||d
<01>St
||
|||d
<01>\}}|s8t|<06>
}|S)a<>This is similar to how the :class:`File` works but for manual
    usage.  Files are opened non lazy by default.  This can open regular
    files as well as stdin/stdout if ``'-'`` is passed.

    If stdin/stdout is returned the stream is wrapped so that the context
    manager will not close the stream accidentally.  This makes it possible
    to always use the function like this without having to worry to
    accidentally close a standard stream::

        with open_file(filename) as f:
            ...

    .. versionadded:: 3.0

    :param filename: the name of the file to open (or ``'-'`` for stdin/stdout).
    :param mode: the mode in which to open the file.
    :param encoding: the encoding to use.
    :param errors: the error handling for this file.
    :param lazy: can be flipped to true to open the file lazily.
    :param atomic: in atomic mode writes go into a temporary file and it's
                   moved on close.
    )
rB)r<rr`)rHr?r@rAZlazyrB<00>
frDrrr<00>	open_file)
s






rtcCs&trt
rtt<03>krt<04>Stjd
d<02>S)a<>This returns the argument part of sys.argv in the most appropriate
    form for processing.  What this means is that this return value is in
    a format that works for Click to process but does not necessarily
    correspond well to what's actually standard for the interpreter.

    On most environments the return value is ``sys.argv[:1]`` unchanged.
    However if you are on Windows and running Python 2 the return value
    will actually be a list of unicode strings instead because the
    default behavior on that platform otherwise will not be able to
    carry all possible values that sys.argv can have.

    .. versionadded:: 6.0
    rN)r	rrrr<00>sys<79>argvrrrr<00>get_os_argsJ
s

rwcCs|
rtj
<01>|<00>
}t|<00>
S)
aKFormats a filename for user display.  The main purpose of this
    function is to ensure that the filename can be displayed at all.  This
    will decode the filename to unicode if necessary in a way that it will
    not fail.  Optionally, it can shorten the filename to not include the
    full path to the filename.

    :param filename: formats a filename for UI display.  This will also convert
                     the filename into unicode without failing.
    :param shorten: this optionally shortens the filename to strip of the
                    path that leads up to it.
    )<04>os<6F>path<74>basenamer)rH<00>shortenrrr<00>format_filename_
s

r|cCs<>tr>|
rd
pd}t
j<02>|<03>
}|dkr0t
j<04>d<04>
}t
j<04>||<00>S|r^t
j<04>t
j<04>dt|<00>
<00>
<01>
Stj	dkr~t
j<04>t
j<04>d<07>
|<00>St
j<04>t
j<02>dt
j<04>d	<09>
<01>t|<00>
<01>S)
aIReturns the config folder for the application.  The default behavior
    is to return whatever is most appropriate for the operating system.

    To give you an idea, for an app called ``"Foo Bar"``, something like
    the following folders could be returned:

    Mac OS X:
      ``~/Library/Application Support/Foo Bar``
    Mac OS X (POSIX):
      ``~/.foo-bar``
    Unix:
      ``~/.config/foo-bar``
    Unix (POSIX):
      ``~/.foo-bar``
    Win XP (roaming):
      ``C:\Documents and Settings\<user>\Local Settings\Application Data\Foo Bar``
    Win XP (not roaming):
      ``C:\Documents and Settings\<user>\Application Data\Foo Bar``
    Win 7 (roaming):
      ``C:\Users\<user>\AppData\Roaming\Foo Bar``
    Win 7 (not roaming):
      ``C:\Users\<user>\AppData\Local\Foo Bar``

    .. versionadded:: 2.0

    :param app_name: the application name.  This should be properly capitalized
                     and can contain whitespace.
    :param roaming: controls if the folder should be roaming or not on Windows.
                    Has no affect otherwise.
    :param force_posix: if this is set to `True` then on any POSIX system the
                        folder will be stored in the home folder with a leading
                        dot instead of the XDG config home or darwin's
                        application support folder.
    <20>APPDATA<54>LOCALAPPDATAN<41>
~z~/.<2E>darwinz~/Library/Application Support<72>XDG_CONFIG_HOMEz	~/.config)
rrx<00>environrnry<00>
expanduserrrru<00>platform)Zapp_name<6D>roamingZforce_posix<69>key<65>folderrrr<00>get_app_dirp
s#














r<>c@s(eZ
dZd
Zdd<03>Zdd<05>Zdd<07>ZdS)	<09>PacifyFlushWrappera<72>
This wrapper is used to catch and suppress BrokenPipeErrors resulting
    from ``.flush()`` being called on broken pipe during the shutdown/final-GC
    of the Python interpreter. Notably ``.flush()`` is always called on
    ``sys.stdout`` and ``sys.stderr``. So as to have minimal impact on any
    other cleanup code, and the case where the underlying file is not a broken
    pipe, all calls and attributes are proxied.
    cCs
|
|_dS)
N)
<01>wrapped)rGr<>rrrrI<00>
s
zPacifyFlushWrapper.__init__c

CsLy|j<00>
<01>
Wn8tk
rF
}

zd
dl}|
j|jkr6<72>Wdd}
~
XYnXdS)Nr
)r<>rfrO<00>errno<6E>EPIPE)rGrSr<>rrrrf<00>
s





zPacifyFlushWrapper.flushcCst|j
|
<01>S)
N)rJr<>)rG<00>attrrrrrK<00>
s
zPacifyFlushWrapper.__getattr__N)r\r]r^r_rIrfrKrrrrr<><00>
sr<>)
r-)NNTFN)Nr>)r=Nr>FF)
F)TF),rxru<00>globalsr<00>_compatrrrrrr	r
rrr
rrrrrrrZ_winconsolerrrr(<00>	bytearrayrerr%r,r;<00>objectr<r`rmrqrrrtrwr|r<>r<>rrrr<00><module>
s.
H





L
a


 

3