File "parse.cpython-36.pyc"
Full Path: /home/attunedd/public_html/byp/izo/con7ext_sym404/rintoar.txt/opt/alt/python36/lib64/python3.6/urllib/__pycache__/parse.cpython-36.pyc
File size: 30.32 KB
MIME-type: text/x-bytecode.python
Charset: 8 bit
3
fo @ s` d Z ddlZddlZddlZddddddd d
ddd
ddddddddddgZddddddddd d!d"d#d$d%d&d'd(d)d*gZdddddd+dddd"d d!d,d#d$d%d-d'd(d&d.d/d0d)d*gZddd1d#ddd d!d$d%d2d3d"d&d4gZdd1d5d6d+ddd,d2d3g
Zddddd d!d"dd$d%d2d3gZ ddd1ddd6ddd d!d,dd#g
Z
d7Zd8d9d:gZd;Z
i Zd<d= Zd>Zd?Zd@dA ZeefdBdCZeefdDdEZdFdG ZG dHdI dIeZG dJdK dKeZG dLdM dMeZG dNdO dOeeZG dPdQ dQeeZddRlmZ eddSZeddTZeddUZdVe_ dWej _ dXej!_ dYe_ dZej"_ d[ej#_ d\ej$_ d]ej%_ d^ej!_ d_e_ ej"j ej"_ ej#j ej#_ ej$j ej$_ d`ej&_ ej%j ej%_ ej!j ej!_ eZ'G dad deeZ(G dbd deeZ)G dcd deeZ*G ddd deeZ+G ded deeZ,G dfd deeZ-dgdh Z.e. [.ddjdZ/dkdl Z0ddmdnZ1dodp Z2dqdr Z3ddsdZ4dtd Z5dud Z6ddvdZ7dwd Z8dxZ9da:dyd Z;ej<dzZ=dd}dZ>ddd
Z?dddZ@dddZAeBdZCeDeCZEi ZFG dd dejGZHdddZIddd
ZJdddZKd~dddeJfdd ZLdd ZMdd ZNdaOdd ZPdaQdd ZRdd ZSdd ZTdaUdd ZVdddZWdd ZXdd ZYdd ZZdd Z[dS )ac Parse (absolute and relative) URLs.
urlparse module is based upon the following RFC specifications.
RFC 3986 (STD66): "Uniform Resource Identifiers" by T. Berners-Lee, R. Fielding
and L. Masinter, January 2005.
RFC 2732 : "Format for Literal IPv6 Addresses in URL's by R.Hinden, B.Carpenter
and L.Masinter, December 1999.
RFC 2396: "Uniform Resource Identifiers (URI)": Generic Syntax by T.
Berners-Lee, R. Fielding, and L. Masinter, August 1998.
RFC 2368: "The mailto URL scheme", by P.Hoffman , L Masinter, J. Zawinski, July 1998.
RFC 1808: "Relative Uniform Resource Locators", by R. Fielding, UC Irvine, June
1995.
RFC 1738: "Uniform Resource Locators (URL)" by T. Berners-Lee, L. Masinter, M.
McCahill, December 1994
RFC 3986 is considered the current standard and any future changes to
urlparse module should conform with it. The urlparse module is
currently not entirely compliant with this RFC due to defacto
scenarios for parsing, and for backward compatibility purposes, some
parsing quirks from older RFCs are retained. The testcases in
test_urlparse.py provides a good indicator of parsing behavior.
Nurlparse
urlunparseurljoin urldefragurlsplit
urlunsplit urlencodeparse_qs parse_qslquote
quote_plusquote_from_bytesunquoteunquote_plusunquote_to_bytesDefragResultParseResultSplitResultDefragResultBytesParseResultBytesSplitResultBytes ZftphttpZgopherZnntpZimapZwaisfileZhttpsZshttpZmmsZprosperoZrtspZrtspuZsftpZsvnzsvn+sshZwsZwssZtelnetZsnewsZrsyncZnfsZgitzgit+sshZhdlZsipZsipsZtelZmailtoZnewszAabcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789+-.
c C s t j tj dS )z,Clear the parse cache and the quoters cache.N)_parse_cacheclear
_safe_quoters r! r! 1/opt/alt/python36/lib64/python3.6/urllib/parse.pyclear_cacheV s r# asciistrictc C s | S )Nr! )objr! r! r"