Edit File: psycopg2.cpython-37.pyc
B ��4]Av � @ s� d Z ddlmZ ddlZddlZddlZddlmZ ddlmZ ddlm Z ddlm Z dd lm Z dd lm Z dd lm Z dd lmZ dd lmZ ddlmZ ddlmZ ddlmZ ddlmZ ddlmZ ddlmZ ddlmZ ddlm Z ddlm Z ydd l mZ W n e!k �r* dZ Y nX e�"d�Z#G dd� dej$�Z%G dd � d e �Z&G d d � d e�Z'G d d � d e�Z(G d!d"� d"e�Z)G d#d$� d$e�Z*e�+� Z,G d%d&� d&e �Z-G d'd(� d(e �Z.G d)d*� d*e�Z/G d+d,� d,e �Z0e0Z1dS )-a�9 .. dialect:: postgresql+psycopg2 :name: psycopg2 :dbapi: psycopg2 :connectstring: postgresql+psycopg2://user:password@host:port/dbname[?key=value&key=value...] :url: http://pypi.python.org/pypi/psycopg2/ psycopg2 Connect Arguments ----------------------------------- psycopg2-specific keyword arguments which are accepted by :func:`.create_engine()` are: * ``server_side_cursors``: Enable the usage of "server side cursors" for SQL statements which support this feature. What this essentially means from a psycopg2 point of view is that the cursor is created using a name, e.g. ``connection.cursor('some name')``, which has the effect that result rows are not immediately pre-fetched and buffered after statement execution, but are instead left on the server and only retrieved as needed. SQLAlchemy's :class:`~sqlalchemy.engine.ResultProxy` uses special row-buffering behavior when this feature is enabled, such that groups of 100 rows at a time are fetched over the wire to reduce conversational overhead. Note that the :paramref:`.Connection.execution_options.stream_results` execution option is a more targeted way of enabling this mode on a per-execution basis. * ``use_native_unicode``: Enable the usage of Psycopg2 "native unicode" mode per connection. True by default. .. seealso:: :ref:`psycopg2_disable_native_unicode` * ``isolation_level``: This option, available for all PostgreSQL dialects, includes the ``AUTOCOMMIT`` isolation level when using the psycopg2 dialect. .. seealso:: :ref:`psycopg2_isolation_level` * ``client_encoding``: sets the client encoding in a libpq-agnostic way, using psycopg2's ``set_client_encoding()`` method. .. seealso:: :ref:`psycopg2_unicode` * ``use_batch_mode``: This flag allows ``psycopg2.extras.execute_batch`` for ``cursor.executemany()`` calls performed by the :class:`.Engine`. It is currently experimental but may well become True by default as it is critical for executemany performance. .. seealso:: :ref:`psycopg2_batch_mode` Unix Domain Connections ------------------------ psycopg2 supports connecting via Unix domain connections. When the ``host`` portion of the URL is omitted, SQLAlchemy passes ``None`` to psycopg2, which specifies Unix-domain communication rather than TCP/IP communication:: create_engine("postgresql+psycopg2://user:password@/dbname") By default, the socket file used is to connect to a Unix-domain socket in ``/tmp``, or whatever socket directory was specified when PostgreSQL was built. This value can be overridden by passing a pathname to psycopg2, using ``host`` as an additional keyword argument:: create_engine("postgresql+psycopg2://user:password@/dbname?host=/var/lib/postgresql") .. seealso:: `PQconnectdbParams \ <http://www.postgresql.org/docs/9.1/static/libpq-connect.html#LIBPQ-PQCONNECTDBPARAMS>`_ Empty DSN Connections / Environment Variable Connections --------------------------------------------------------- The psycopg2 DBAPI can connect to PostgreSQL by passing an empty DSN to the libpq client library, which by default indicates to connect to a localhost PostgreSQL database that is open for "trust" connections. This behavior can be further tailored using a particular set of environment variables which are prefixed with ``PG_...``, which are consumed by ``libpq`` to take the place of any or all elements of the connection string. For this form, the URL can be passed without any elements other than the initial scheme:: engine = create_engine('postgresql+psycopg2://') In the above form, a blank "dsn" string is passed to the ``psycopg2.connect()`` function which in turn represents an empty DSN passed to libpq. .. versionadded:: 1.3.2 support for parameter-less connections with psycopg2. .. seealso:: `Environment Variables\ <https://www.postgresql.org/docs/current/libpq-envars.html>`_ - PostgreSQL documentation on how to use ``PG_...`` environment variables for connections. .. _psycopg2_execution_options: Per-Statement/Connection Execution Options ------------------------------------------- The following DBAPI-specific options are respected when used with :meth:`.Connection.execution_options`, :meth:`.Executable.execution_options`, :meth:`.Query.execution_options`, in addition to those not specific to DBAPIs: * ``isolation_level`` - Set the transaction isolation level for the lifespan of a :class:`.Connection` (can only be set on a connection, not a statement or query). See :ref:`psycopg2_isolation_level`. * ``stream_results`` - Enable or disable usage of psycopg2 server side cursors - this feature makes use of "named" cursors in combination with special result handling methods so that result rows are not fully buffered. If ``None`` or not set, the ``server_side_cursors`` option of the :class:`.Engine` is used. * ``max_row_buffer`` - when using ``stream_results``, an integer value that specifies the maximum number of rows to buffer at a time. This is interpreted by the :class:`.BufferedRowResultProxy`, and if omitted the buffer will grow to ultimately store 1000 rows at a time. .. versionadded:: 1.0.6 .. _psycopg2_batch_mode: Psycopg2 Batch Mode (Fast Execution) ------------------------------------ Modern versions of psycopg2 include a feature known as `Fast Execution Helpers \ <http://initd.org/psycopg/docs/extras.html#fast-execution-helpers>`_, which have been shown in benchmarking to improve psycopg2's executemany() performance with INSERTS by multiple orders of magnitude. SQLAlchemy allows this extension to be used for all ``executemany()`` style calls invoked by an :class:`.Engine` when used with :ref:`multiple parameter sets <execute_multiple>`, by adding the ``use_batch_mode`` flag to :func:`.create_engine`:: engine = create_engine( "postgresql+psycopg2://scott:tiger@host/dbname", use_batch_mode=True) Batch mode is considered to be **experimental** at this time, however may be enabled by default in a future release. .. seealso:: :ref:`execute_multiple` - demonstrates how to use DBAPI ``executemany()`` with the :class:`.Connection` object. .. versionadded:: 1.2.0 .. _psycopg2_unicode: Unicode with Psycopg2 ---------------------- By default, the psycopg2 driver uses the ``psycopg2.extensions.UNICODE`` extension, such that the DBAPI receives and returns all strings as Python Unicode objects directly - SQLAlchemy passes these values through without change. Psycopg2 here will encode/decode string values based on the current "client encoding" setting; by default this is the value in the ``postgresql.conf`` file, which often defaults to ``SQL_ASCII``. Typically, this can be changed to ``utf8``, as a more useful default:: # postgresql.conf file # client_encoding = sql_ascii # actually, defaults to database # encoding client_encoding = utf8 A second way to affect the client encoding is to set it within Psycopg2 locally. SQLAlchemy will call psycopg2's :meth:`psycopg2:connection.set_client_encoding` method on all new connections based on the value passed to :func:`.create_engine` using the ``client_encoding`` parameter:: # set_client_encoding() setting; # works for *all* PostgreSQL versions engine = create_engine("postgresql://user:pass@host/dbname", client_encoding='utf8') This overrides the encoding specified in the PostgreSQL client configuration. When using the parameter in this way, the psycopg2 driver emits ``SET client_encoding TO 'utf8'`` on the connection explicitly, and works in all PostgreSQL versions. Note that the ``client_encoding`` setting as passed to :func:`.create_engine` is **not the same** as the more recently added ``client_encoding`` parameter now supported by libpq directly. This is enabled when ``client_encoding`` is passed directly to ``psycopg2.connect()``, and from SQLAlchemy is passed using the :paramref:`.create_engine.connect_args` parameter:: engine = create_engine( "postgresql://user:pass@host/dbname", connect_args={'client_encoding': 'utf8'}) # using the query string is equivalent engine = create_engine("postgresql://user:pass@host/dbname?client_encoding=utf8") The above parameter was only added to libpq as of version 9.1 of PostgreSQL, so using the previous method is better for cross-version support. .. _psycopg2_disable_native_unicode: Disabling Native Unicode ^^^^^^^^^^^^^^^^^^^^^^^^ SQLAlchemy can also be instructed to skip the usage of the psycopg2 ``UNICODE`` extension and to instead utilize its own unicode encode/decode services, which are normally reserved only for those DBAPIs that don't fully support unicode directly. Passing ``use_native_unicode=False`` to :func:`.create_engine` will disable usage of ``psycopg2.extensions.UNICODE``. SQLAlchemy will instead encode data itself into Python bytestrings on the way in and coerce from bytes on the way back, using the value of the :func:`.create_engine` ``encoding`` parameter, which defaults to ``utf-8``. SQLAlchemy's own unicode encode/decode functionality is steadily becoming obsolete as most DBAPIs now support unicode fully. Bound Parameter Styles ---------------------- The default parameter style for the psycopg2 dialect is "pyformat", where SQL is rendered using ``%(paramname)s`` style. This format has the limitation that it does not accommodate the unusual case of parameter names that actually contain percent or parenthesis symbols; as SQLAlchemy in many cases generates bound parameter names based on the name of a column, the presence of these characters in a column name can lead to problems. There are two solutions to the issue of a :class:`.schema.Column` that contains one of these characters in its name. One is to specify the :paramref:`.schema.Column.key` for columns that have such names:: measurement = Table('measurement', metadata, Column('Size (meters)', Integer, key='size_meters') ) Above, an INSERT statement such as ``measurement.insert()`` will use ``size_meters`` as the parameter name, and a SQL expression such as ``measurement.c.size_meters > 10`` will derive the bound parameter name from the ``size_meters`` key as well. .. versionchanged:: 1.0.0 - SQL expressions will use :attr:`.Column.key` as the source of naming when anonymous bound parameters are created in SQL expressions; previously, this behavior only applied to :meth:`.Table.insert` and :meth:`.Table.update` parameter names. The other solution is to use a positional format; psycopg2 allows use of the "format" paramstyle, which can be passed to :paramref:`.create_engine.paramstyle`:: engine = create_engine( 'postgresql://scott:tiger@localhost:5432/test', paramstyle='format') With the above engine, instead of a statement like:: INSERT INTO measurement ("Size (meters)") VALUES (%(Size (meters))s) {'Size (meters)': 1} we instead see:: INSERT INTO measurement ("Size (meters)") VALUES (%s) (1, ) Where above, the dictionary style is converted into a tuple with positional style. Transactions ------------ The psycopg2 dialect fully supports SAVEPOINT and two-phase commit operations. .. _psycopg2_isolation_level: Psycopg2 Transaction Isolation Level ------------------------------------- As discussed in :ref:`postgresql_isolation_level`, all PostgreSQL dialects support setting of transaction isolation level both via the ``isolation_level`` parameter passed to :func:`.create_engine`, as well as the ``isolation_level`` argument used by :meth:`.Connection.execution_options`. When using the psycopg2 dialect, these options make use of psycopg2's ``set_isolation_level()`` connection method, rather than emitting a PostgreSQL directive; this is because psycopg2's API-level setting is always emitted at the start of each transaction in any case. The psycopg2 dialect supports these constants for isolation level: * ``READ COMMITTED`` * ``READ UNCOMMITTED`` * ``REPEATABLE READ`` * ``SERIALIZABLE`` * ``AUTOCOMMIT`` .. seealso:: :ref:`postgresql_isolation_level` :ref:`pg8000_isolation_level` NOTICE logging --------------- The psycopg2 dialect will log PostgreSQL NOTICE messages via the ``sqlalchemy.dialects.postgresql`` logger. When this logger is set to the ``logging.INFO`` level, notice messages will be logged:: import logging logging.getLogger('sqlalchemy.dialects.postgresql').setLevel(logging.INFO) Above, it is assumed that logging is configured externally. If this is not the case, configuration such as ``logging.basicConfig()`` must be utilized:: import logging logging.basicConfig() # log messages to stdout logging.getLogger('sqlalchemy.dialects.postgresql').setLevel(logging.INFO) .. seealso:: `Logging HOWTO <https://docs.python.org/3/howto/logging.html>`_ - on the python.org website .. _psycopg2_hstore: HSTORE type ------------ The ``psycopg2`` DBAPI includes an extension to natively handle marshalling of the HSTORE type. The SQLAlchemy psycopg2 dialect will enable this extension by default when psycopg2 version 2.4 or greater is used, and it is detected that the target database has the HSTORE type set up for use. In other words, when the dialect makes the first connection, a sequence like the following is performed: 1. Request the available HSTORE oids using ``psycopg2.extras.HstoreAdapter.get_oids()``. If this function returns a list of HSTORE identifiers, we then determine that the ``HSTORE`` extension is present. This function is **skipped** if the version of psycopg2 installed is less than version 2.4. 2. If the ``use_native_hstore`` flag is at its default of ``True``, and we've detected that ``HSTORE`` oids are available, the ``psycopg2.extensions.register_hstore()`` extension is invoked for all connections. The ``register_hstore()`` extension has the effect of **all Python dictionaries being accepted as parameters regardless of the type of target column in SQL**. The dictionaries are converted by this extension into a textual HSTORE expression. If this behavior is not desired, disable the use of the hstore extension by setting ``use_native_hstore`` to ``False`` as follows:: engine = create_engine("postgresql+psycopg2://scott:tiger@localhost/test", use_native_hstore=False) The ``HSTORE`` type is **still supported** when the ``psycopg2.extensions.register_hstore()`` extension is not used. It merely means that the coercion between Python dictionaries and the HSTORE string format, on both the parameter side and the result side, will take place within SQLAlchemy's own marshalling logic, and not that of ``psycopg2`` which may be more performant. � )�absolute_importN� )�_DECIMAL_TYPES)� _FLOAT_TYPES)� _INT_TYPES)�ENUM)� PGCompiler)� PGDialect)�PGExecutionContext)�PGIdentifierPreparer)�UUID)�HSTORE)�JSON)�JSONB� )�exc)� processors)�types)�util)�result)�collections_abcz sqlalchemy.dialects.postgresqlc @ s e Zd Zdd� Zdd� ZdS )� _PGNumericc C s d S )N� )�self�dialectr r �Z/opt/alt/python37/lib64/python3.7/site-packages/sqlalchemy/dialects/postgresql/psycopg2.py�bind_processor� s z_PGNumeric.bind_processorc C sv | j rB|tkr t�tj| j�S |tks.|tkr2d S t � d| ��n0|tkrNd S |tks^|tkrdtj S t � d| ��d S )NzUnknown PG numeric type: %d) Z asdecimalr r Z to_decimal_processor_factory�decimalZDecimalZ _effective_decimal_return_scaler r r ZInvalidRequestErrorZto_float)r r �coltyper r r �result_processor� s z_PGNumeric.result_processorN)�__name__� __module__� __qualname__r r r r r r r � s r c s e Zd Z� fdd�Z� ZS )�_PGEnumc s( t jr| jdkrd| _tt| ��||�S )NTZ force_nocheck)r �py2kZ_expect_unicode�superr# r )r r r )� __class__r r r � s z_PGEnum.result_processor)r r! r" r � __classcell__r r )r& r r# � s r# c s( e Zd Z� fdd�Z� fdd�Z� ZS )� _PGHStorec s |j r d S tt| ��|�S d S )N)�_has_native_hstorer% r( r )r r )r& r r r � s z_PGHStore.bind_processorc s |j r d S tt| ��||�S d S )N)r) r% r( r )r r r )r& r r r � s z_PGHStore.result_processor)r r! r" r r r' r r )r& r r( � s r( c s e Zd Z� fdd�Z� ZS )�_PGJSONc s |j r d S tt| ��||�S d S )N)�_has_native_jsonr% r* r )r r r )r& r r r � s z_PGJSON.result_processor)r r! r" r r' r r )r& r r* � s r* c s e Zd Z� fdd�Z� ZS )�_PGJSONBc s |j r d S tt| ��||�S d S )N)�_has_native_jsonbr% r, r )r r r )r& r r r � s z_PGJSONB.result_processor)r r! r" r r' r r )r& r r, � s r, c @ s e Zd Zdd� Zdd� ZdS )�_PGUUIDc C s | j s|jrdd� }|S d S )Nc S s | d k rt | �} | S )N)� _python_UUID)�valuer r r �process� s z'_PGUUID.bind_processor.<locals>.process)�as_uuid�use_native_uuid)r r r1 r r r r � s z_PGUUID.bind_processorc C s | j s|jrdd� }|S d S )Nc S s | d k rt | �} | S )N)�str)r0 r r r r1 � s z)_PGUUID.result_processor.<locals>.process)r2 r3 )r r r r1 r r r r � s z_PGUUID.result_processorN)r r! r" r r r r r r r. � s r. c @ s$ e Zd Zdd� Zdd� Zdd� ZdS )�PGExecutionContext_psycopg2c C s6 dt t| ��dd � t t� �dd � f }| j�|�S )Nzc_%s_%s� )�hex�id�_server_side_idZ_dbapi_connection�cursor)r �identr r r �create_server_side_cursor s *z5PGExecutionContext_psycopg2.create_server_side_cursorc C s* | � | j� | jr t�| �S t�| �S d S )N)� _log_noticesr: Z_is_server_side�_resultZBufferedRowResultProxyZ ResultProxy)r r r r �get_result_proxy s z,PGExecutionContext_psycopg2.get_result_proxyc C sP |j jrt|j jtj�s d S x |j jD ]}t�|�� � q&W g |j jd d �< d S )N)� connectionZnotices� isinstancer �Iterable�logger�info�rstrip)r r: Znoticer r r r= s z(PGExecutionContext_psycopg2._log_noticesN)r r! r" r< r? r= r r r r r5 s r5 c @ s e Zd ZdS )�PGCompiler_psycopg2N)r r! r" r r r r rF ) s rF c @ s e Zd ZdS )� PGIdentifierPreparer_psycopg2N)r r! r" r r r r rG - s rG c s e Zd ZdZejrdZdZdZdZ e Z e Z eZdZedddd d d �ZdZdZdZej�d ejfg�Ze�eje j e e e e j!e e"e#e$e%e j$e%e&e'e(e)i�Zd&dd�Z*� fdd�Z+e,dd� �Z-e,dd� �Z.e,dd� �Z/ej0dd� �Z1dd� Z2d d � Z3d'd d �Z4ej5d d!� �Z6d"d#� Z7d$d%� Z8� Z9S )(�PGDialect_psycopg2�psycopg2FTZpyformat)r r )r6 � )r6 rJ � )r6 r � )r6 rK r )r6 rK )� native_json� native_jsonb�sane_multi_rowcount� array_oid�hstore_adapter�use_native_unicodeNc K s� t j| f|� || _|| _|| _|| _|| _|| _|| _| j r|t | j d�r|t � d| j j �}|r|tdd� |�ddd�D ��| _d S )N� __version__z(\d+)\.(\d+)(?:\.(\d+))?c s s | ]}|d k rt |�V qd S )N)�int)�.0�xr r r � <genexpr>t s z.PGDialect_psycopg2.__init__.<locals>.<genexpr>r r6 r )r �__init__�server_side_cursorsrR �use_native_hstorer3 Zsupports_unicode_binds�client_encoding�psycopg2_batch_mode�dbapi�hasattr�re�matchrS �tuple�group�psycopg2_version) r rY rR r[ rZ r3 Zuse_batch_mode�kwargs�mr r r rX ^ s zPGDialect_psycopg2.__init__c sj t t| ��|� | jo$| �|j�d k | _| j| jd k| _ | j| jd k| _ | j| jd kob| j | _ d S )NrM rN rO ) r% rH � initializerZ � _hstore_oidsr@ r) rc �FEATURE_VERSION_MAPr+ r- r\ � supports_sane_multi_rowcount)r r@ )r& r r rf w s z PGDialect_psycopg2.initializec C s dd l }|S )Nr )rI )�clsrI r r r r] � s zPGDialect_psycopg2.dbapic C s ddl m} |S )Nr )� extensions)rI rk )rj rk r r r �_psycopg2_extensions� s z'PGDialect_psycopg2._psycopg2_extensionsc C s ddl m} |S )Nr )�extras)rI rm )rj rm r r r �_psycopg2_extras� s z#PGDialect_psycopg2._psycopg2_extrasc C s" | � � }|j|j|j|j|jd�S )N)Z AUTOCOMMITzREAD COMMITTEDzREAD UNCOMMITTEDzREPEATABLE READZ SERIALIZABLE)rl ZISOLATION_LEVEL_AUTOCOMMITZ ISOLATION_LEVEL_READ_COMMITTEDZ ISOLATION_LEVEL_READ_UNCOMMITTEDZ ISOLATION_LEVEL_REPEATABLE_READZ ISOLATION_LEVEL_SERIALIZABLE)r rk r r r �_isolation_lookup� s z$PGDialect_psycopg2._isolation_lookupc C sX y| j |�dd� }W n2 tk rH t�d|| jd�| j �f ��Y nX |�|� d S )N�_� zLInvalid value '%s' for isolation_level. Valid isolation levels for %s are %sz, )ro �replace�KeyErrorr � ArgumentError�name�join�set_isolation_level)r r@ �levelr r r rw � s z&PGDialect_psycopg2.set_isolation_levelc s� �� � ���� � g ��jd k r4�fdd�}��|� �jd k rT�fdd�}��|� �jrv�jrv�fdd�}��|� �jr��jr�� fdd�}��|� �jr��jr���fdd�}��|� �jr�j r��fdd�}��|� �r�fdd�}|S d S d S ) Nc s | � � j� d S )N)Zset_client_encodingr[ )�conn)r r r � on_connect� s z1PGDialect_psycopg2.on_connect.<locals>.on_connectc s � � | � j� d S )N)rw �isolation_level)ry )r r r rz � s c s � � d | � d S )N)Z register_uuid)ry )rm r r rz � s c s � � � j| � � � � j| � d S )N)Z register_type�UNICODEZ UNICODEARRAY)ry )rk r r rz � s c sZ �� | �}|d k rV|\}}d|i}tjr0d|d< �j�jd krH||d< � j| f|� d S )N�oidT�unicoderP )rg r r$ rc rh Zregister_hstore)ry Z hstore_oidsr} rP �kw)rm r r r rz � s c s0 �j r� j| �jd� �jr,� j| �jd� d S )N)�loads)r+ Zregister_default_json�_json_deserializerr- Zregister_default_jsonb)ry )rm r r r rz � s c s x� D ] }|| � qW d S )Nr )ry �fn)�fnsr r rz � s ) rn rl r[ �appendr{ r] r3 rR rZ r� )r rz r )rk rm r� r r rz � s2 z PGDialect_psycopg2.on_connectc C s. | j r | �� }|�|||� n |�||� d S )N)r\ rn Z execute_batchZ executemany)r r: � statement� parameters�contextrm r r r �do_executemany s z!PGDialect_psycopg2.do_executemanyc C sD | j | jd kr@| �� }|j�|�}|d k r@|d r@|dd� S d S )NrQ r r6 )rc rh rn Z HstoreAdapterZget_oids)r ry rm Zoidsr r r rg s z PGDialect_psycopg2._hstore_oidsc C sd |j dd�}|r<d|kr(t|d �|d< |�|j� g |fS |jrV|�|j� g |fS dg|fS d S )N�user)�username�port� )Ztranslate_connect_argsrT �update�query)r �url�optsr r r �create_connect_args s z&PGDialect_psycopg2.create_connect_argsc C sh t || jj�rdt|dd�r dS t|��d�d }x2dD ]*}|�|�}|dkr6d|d |� kr6dS q6W dS )N�closedFT� r ) zterminating connectionzclosed the connectionzconnection not openz"could not receive data from serverz could not send data to serverzconnection already closedzcursor already closedz!losed the connection unexpectedlyz'connection has been closed unexpectedlyz&SSL SYSCALL error: Bad file descriptorz SSL SYSCALL error: EOF detectedz.SSL error: decryption failed or bad record macz&SSL SYSCALL error: Operation timed out�")rA r] �Error�getattrr4 � partition�find)r �er@ r: Zstr_e�msg�idxr r r � is_disconnect" s z PGDialect_psycopg2.is_disconnect)FTNTTF)N):r r! r" Zdriverr r$ Zsupports_unicode_statementsZ supports_server_side_cursorsZdefault_paramstyleri r5 Zexecution_ctx_clsrF Zstatement_compilerrG Zpreparerrc �dictrh r) r+ r- r Zengine_config_types�unionZasboolZ update_copyZcolspecs�sqltypes�Numericr r r# �Enumr r( r r* r r, r r. rX rf � classmethodr] rl rn Zmemoized_propertyro rw rz r� Zmemoized_instancemethodrg r� r� r' r r )r& r rH 1 s` L rH )2�__doc__� __future__r r �loggingr_ �baser r r r r r r r r Zhstorer �jsonr r r� r r r r� r Zenginer r> r �uuidr/ � ImportError� getLoggerrC r� r r# r( r* r, r. �counterr9 r5 rF rG rH r r r r r �<module>� sR !