Dashboard
PHP:
8.2.30
OS:
Linux
User:
dh_nv8b2m
/
/
usr
/
local
/
lib
/
python3.10
/
dist-packages
/
sqlalchemy
/
testing
/
__pycache__
📤 Upload
📝 New File
📁 New Folder
Close
Editing: requirements.cpython-310.pyc
o [�h�o � @ sH d Z ddlZddlmZ ddlmZ G dd� de�ZG d d � d e�ZdS ) z�Global database feature support policy. Provides decorators to mark tests requiring specific feature support from the target database. External dialect test suites should subclass SuiteRequirements to provide specific inclusion/exclusions. � N� )� exclusions� )�utilc @ s e Zd ZdS )� RequirementsN)�__name__� __module__� __qualname__� r r �J/usr/local/lib/python3.10/dist-packages/sqlalchemy/testing/requirements.pyr s r c @ s| e Zd Zedd� �Zedd� �Zedd� �Zedd� �Zed d � �Zed d � �Z ed d� �Z edd� �Z edd� �Z edd� �Z edd� �Zedd� �Zedd� �Zedd � �Zed d � �Zed d � �Zed!d"� �Zed#d$� �Zed%d&� �Zed'd(� �Zed)d*� �Zed+d,� �Zed-d.� �Zed/d0� �Zed1d2� �Z ed3d4� �Z ed5d6� �Z ed7d8� �Z ed9d:� �Z ed;d<� �Z!ed=d>� �Z"ed?d@� �Z#edAdB� �Z$edCdD� �Z%edEdF� �Z&edGdH� �Z'edIdJ� �Z(edKdL� �Z)edMdN� �Z*edOdP� �Z+edQdR� �Z,edSdT� �Z-edUdV� �Z.edWdX� �Z/edYdZ� �Z0ed[d\� �Z1ed]d^� �Z2ed_d`� �Z3edadb� �Z4edcdd� �Z5ededf� �Z6edgdh� �Z7edidj� �Z8edkdl� �Z9edmdn� �Z:edodp� �Z;edqdr� �Z<edsdt� �Z=edudv� �Z>edwdx� �Z?edydz� �Z@ed{d|� �ZAed}d~� �ZBedd�� �ZCed�d�� �ZDed�d�� �ZEed�d�� �ZFed�d�� �ZGed�d�� �ZHed�d�� �ZIed�d�� �ZJed�d�� �ZKed�d�� �ZLed�d�� �ZMed�d�� �ZNed�d�� �ZOed�d�� �ZPed�d�� �ZQed�d�� �ZRed�d�� �ZSed�d�� �ZTed�d�� �ZUed�d�� �ZVed�d�� �ZWed�d�� �ZXed�d�� �ZYed�d�� �ZZed�d�� �Z[ed�d�� �Z\ed�d�� �Z]ed�d�� �Z^ed�d�� �Z_ed�d�� �Z`ed�d�� �Zaed�d�� �Zbed�d�� �Zced�d �Zded�dĄ �Zeed�dƄ �Zfed�dȄ �Zged�dʄ �Zhed�d̄ �Zied�d΄ �Zjed�dЄ �Zked�d҄ �Zled�dԄ �Zmed�dք �Zned�d �Zoed�dڄ �Zped�d܄ �Zqed�dބ �Zred�d� �Zsed�d� �Zted�d� �Zud�d� Zved�d� �Zwed�d� �Zxed�d� �Zyed�d� �Zzed�d� �Z{ed�d� �Z|ed�d� �Z}ed�d�� �Z~ed�d�� �Zed�d�� �Z�ed�d�� �Z�ed�d�� �Z�ed��d � �Z�e�d�d� �Z��d�d� Z��d�d� Z�e�d�d� �Z�e�d �d � �Z��d �d � Z��d �d� Z�e�d�d� �Z��dS ( �SuiteRequirementsc C � t �� S )z/target platform can emit basic CreateTable DDL.�r �open��selfr r r � create_table � z SuiteRequirements.create_tablec C r )z-target platform can emit basic DropTable DDL.r r r r r � drop_table# r z SuiteRequirements.drop_tablec C r )z*Target database must support foreign keys.r r r r r � foreign_keys) r z SuiteRequirements.foreign_keysc C r )zR"target database must support ON UPDATE..CASCADE behavior in foreign keys.r r r r r �on_update_cascade/ � z#SuiteRequirements.on_update_cascadec C r )zWtarget database must *not* support ON UPDATE..CASCADE behavior in foreign keys.�r �closedr r r r �non_updating_cascade6 r z&SuiteRequirements.non_updating_cascadec C r �Nr r r r r �deferrable_fks< � z SuiteRequirements.deferrable_fksc � t �� fdd��S )Nc s � j jp� jjS r )r �enabledr r r r r �<lambda>F s z?SuiteRequirements.on_update_or_deferrable_fks.<locals>.<lambda>�r �only_ifr r r r �on_update_or_deferrable_fks@ s �z-SuiteRequirements.on_update_or_deferrable_fksc C r )z;Target database must support self-referential foreign keys.r r r r r � self_referential_foreign_keysJ r z/SuiteRequirements.self_referential_foreign_keysc C r )z=Target database must support the DDL phrases for FOREIGN KEY.r r r r r �foreign_key_ddlP r z!SuiteRequirements.foreign_key_ddlc C r )z3target database must support names for constraints.r r r r r �named_constraintsV r z#SuiteRequirements.named_constraintsc C r )z(Target database must support subqueries.r r r r r � subqueries\ r z SuiteRequirements.subqueriesc C r )zRtarget database can render OFFSET, or an equivalent, in a SELECT. r r r r r �offsetb � zSuiteRequirements.offsetc C r )zWtarget database can render LIMIT and/or OFFSET using a bound parameter r r r r r �bound_limit_offsetj r) z$SuiteRequirements.bound_limit_offsetc C r )z�target database can render LIMIT and/or OFFSET with a complete SQL expression, such as one that uses the addition operator. parameter r r r r r �sql_expression_limit_offsetr � z-SuiteRequirements.sql_expression_limit_offsetc C r )z�Target database must support parenthesized SELECT in UNION when LIMIT/OFFSET is specifically present. E.g. (SELECT ...) UNION (SELECT ..) This is known to fail on SQLite. r r r r r �/parens_in_union_contained_select_w_limit_offset{ � zASuiteRequirements.parens_in_union_contained_select_w_limit_offsetc C r )al Target database must support parenthesized SELECT in UNION when OFFSET/LIMIT is specifically not present. E.g. (SELECT ... LIMIT ..) UNION (SELECT .. OFFSET ..) This is known to fail on SQLite. It also fails on Oracle because without LIMIT/OFFSET, there is currently no step that creates an additional subquery. r r r r r �0parens_in_union_contained_select_wo_limit_offset� s zBSuiteRequirements.parens_in_union_contained_select_wo_limit_offsetc C r )z;Target database must support boolean expressions as columnsr r r r r �boolean_col_expressions� r z)SuiteRequirements.boolean_col_expressionsc C r )z5Target database allows boolean columns to store NULL.r r r r r �nullable_booleans� r z#SuiteRequirements.nullable_booleansc C r )z,Target backends that support nulls ordering.r r r r r � nullsordering� r z SuiteRequirements.nullsorderingc C r )z�target database/driver supports bound parameters as column expressions without being in the context of a typed column. r r r r r �standalone_binds� r) z"SuiteRequirements.standalone_bindsc C r )z�target database/driver supports bound parameters with NULL in the WHERE clause, in situations where it has to be typed. r r r r r �!standalone_null_binds_whereclause� r) z3SuiteRequirements.standalone_null_binds_whereclausec C r )z5Target database must support INTERSECT or equivalent.r r r r r � intersect� � zSuiteRequirements.intersectc C r )z?Target database must support EXCEPT or equivalent (i.e. MINUS).r r r r r �except_� r6 zSuiteRequirements.except_c C r )z.Target database must support window functions.r r r r r �window_functions� r6 z"SuiteRequirements.window_functionsc C r )z Target database supports CTEsr r r r r �ctes� r zSuiteRequirements.ctesc C r )z�target database supports CTES that ride on top of a normal UPDATE or DELETE statement which refers to the CTE in a correlated subquery. r r r r r �ctes_with_update_delete� r, z)SuiteRequirements.ctes_with_update_deletec C r )z}target database supports CTES which consist of INSERT, UPDATE or DELETE *within* the CTE, e.g. WITH x AS (UPDATE....)r r r r r � ctes_on_dml� r z SuiteRequirements.ctes_on_dmlc C r )z~target platform generates new surrogate integer primary key values when insert() is executed, excluding the pk column.r r r r r �autoincrement_insert� r z&SuiteRequirements.autoincrement_insertc C r )a# target platform will allow cursor.fetchone() to proceed after a COMMIT. Typically this refers to an INSERT statement with RETURNING which is invoked within "autocommit". If the row can be returned after the autocommit, then this rule can be open. r r r r r �fetch_rows_post_commit� s z(SuiteRequirements.fetch_rows_post_commitc C r )z�target platform supports SQL expressions in GROUP BY e.g. SELECT x + y AS somelabel FROM table GROUP BY x + y r r r r r �group_by_complex_expression� r. z-SuiteRequirements.group_by_complex_expressionc C � t �dd� d�S )Nc S � | j jj S r )�db�dialect�supports_sane_rowcount��configr r r r � � z1SuiteRequirements.sane_rowcount.<locals>.<lambda>z&driver doesn't support 'sane' rowcount�r �skip_ifr r r r � sane_rowcount� � �z SuiteRequirements.sane_rowcountc C r? )Nc S r@ r )rA rB � supports_sane_multi_rowcountrD r r r r rF z7SuiteRequirements.sane_multi_rowcount.<locals>.<lambda>z;driver %(driver)s %(doesnt_support)s 'sane' multi row count�r �fails_ifr r r r �sane_multi_rowcount rJ z%SuiteRequirements.sane_multi_rowcountc C r? )Nc S r@ r )rA rB � supports_sane_rowcount_returningrD r r r r s �z=SuiteRequirements.sane_rowcount_w_returning.<locals>.<lambda>z;driver doesn't support 'sane' rowcount when returning is onrL r r r r �sane_rowcount_w_returning s �z+SuiteRequirements.sane_rowcount_w_returningc C r? )zatarget platform supports INSERT with no values, i.e. INSERT DEFAULT VALUES or equivalent.c S s | j jjp | j jjS r )rA rB �supports_empty_insert�supports_default_valuesrD r r r r � z1SuiteRequirements.empty_inserts.<locals>.<lambda>zempty inserts not supportedr! r r r r � empty_inserts s �z SuiteRequirements.empty_insertsc C r )z.target platform supports INSERT from a SELECT.r r r r r �insert_from_select r z$SuiteRequirements.insert_from_selectc C r? )z#target platform supports RETURNING.c S � | j jjS r )rA rB �implicit_returningrD r r r r ) � z-SuiteRequirements.returning.<locals>.<lambda>z)%(database)s %(does_support)s 'returning'r! r r r r � returning$ s �zSuiteRequirements.returningc C r )zZTarget platform supports the syntax "(x, y) IN ((x1, y1), (x2, y2), ...)" r r r r r �tuple_in- r) zSuiteRequirements.tuple_inc C r )zwtarget platform supports a SELECT statement that has the same name repeated more than once in the columns list.r r r r r �%duplicate_names_in_cursor_description5 r z7SuiteRequirements.duplicate_names_in_cursor_descriptionc C r? )z[Target database must have 'denormalized', i.e. UPPERCASE as case insensitive names.c S r@ r )rA rB �requires_name_normalizerD r r r r B rF z6SuiteRequirements.denormalized_names.<locals>.<lambda>z,Backend does not require denormalized names.rG r r r r �denormalized_names< � �z$SuiteRequirements.denormalized_namesc C r? )zTtarget database must support multiple VALUES clauses in an INSERT statement.c S r@ r )rA rB �supports_multivalues_insertrD r r r r L rF z7SuiteRequirements.multivalues_inserts.<locals>.<lambda>z*Backend does not support multirow inserts.rG r r r r �multivalues_insertsF r^ z%SuiteRequirements.multivalues_insertsc C r )zw"target dialect implements the executioncontext.get_lastrowid() method without reliance on RETURNING. r r r r r �implements_get_lastrowidP r) z*SuiteRequirements.implements_get_lastrowidc C r )a= "target dialect retrieves cursor.lastrowid, or fetches from a database-side function after an insert() construct executes, within the get_lastrowid() method. Only dialects that "pre-execute", or need RETURNING to get last inserted id, would return closed/fail/skip for this. r r r r r �emulated_lastrowidX r. z$SuiteRequirements.emulated_lastrowidc C r )z^"target platform includes a 'lastrowid' accessor on the DBAPI cursor object. r r r r r �dbapi_lastrowidd r) z!SuiteRequirements.dbapi_lastrowidc C r )z#Target database must support VIEWs.r r r r r �viewsl r zSuiteRequirements.viewsc C r )zXTarget database must support external schemas, and have one named 'test_schema'.r r r r r �schemasr r zSuiteRequirements.schemasc C r )zLtarget system must support reflection of inter-schema foreign keys r r r r r �cross_schema_fk_reflectiony r z,SuiteRequirements.cross_schema_fk_reflectionc C r )z�target system has a strong concept of 'default' schema that can be referred to implicitly. basically, PostgreSQL. r r r r r �implicit_default_schema� � z)SuiteRequirements.implicit_default_schemac C � t �dd� gd�S )z0Target dialect must support server side cursors.c S rV r )rA rB � supports_server_side_cursorsrD r r r r � rX z7SuiteRequirements.server_side_cursors.<locals>.<lambda>z no server side cursors supportr! r r r r �server_side_cursors� � �z%SuiteRequirements.server_side_cursorsc C ri )z'Target database must support SEQUENCEs.c S rV r )rA rB �supports_sequencesrD r r r r � rX z-SuiteRequirements.sequences.<locals>.<lambda>zno sequence supportr! r r r r � sequences� rl zSuiteRequirements.sequencesc C ri )zgTarget database supports sequences, but also optionally as a means of generating new PK values.c S s | j jjo | j jjS r )rA rB rm �sequences_optionalrD r r r r � rS z6SuiteRequirements.sequences_optional.<locals>.<lambda>z.no sequence support, or sequences not optionalr! r r r r ro � s ��z$SuiteRequirements.sequences_optionalc C r r r r r r r �reflects_pk_names� r z#SuiteRequirements.reflects_pk_namesc C r r r r r r r �table_reflection� r z"SuiteRequirements.table_reflectionc C r r r r r r r �comment_reflection� r z$SuiteRequirements.comment_reflectionc C � | j S )z�target database must support retrieval of the columns in a view, similarly to how a table is inspected. This does not include the full CREATE VIEW definition. �rd r r r r �view_column_reflection� s z(SuiteRequirements.view_column_reflectionc C rs )zTtarget database must support inspection of the full CREATE VIEW definition. rt r r r r �view_reflection� s z!SuiteRequirements.view_reflectionc C rs r )re r r r r �schema_reflection� s z#SuiteRequirements.schema_reflectionc C r r r r r r r �!primary_key_constraint_reflection� r z3SuiteRequirements.primary_key_constraint_reflectionc C r r r r r r r �!foreign_key_constraint_reflection� r z3SuiteRequirements.foreign_key_constraint_reflectionc C r r r r r r r �1foreign_key_constraint_option_reflection_ondelete� r zCSuiteRequirements.foreign_key_constraint_option_reflection_ondeletec C r r r r r r r �1foreign_key_constraint_option_reflection_onupdate� r zCSuiteRequirements.foreign_key_constraint_option_reflection_onupdatec C r r r r r r r �temp_table_reflection� r z'SuiteRequirements.temp_table_reflectionc C r )z8target dialect supports listing of temporary table namesr r r r r �temp_table_names� r6 z"SuiteRequirements.temp_table_namesc C r )z)target database supports temporary tablesr r r r r �temporary_tables� r6 z"SuiteRequirements.temporary_tablesc C r )z(target database supports temporary viewsr r r r r �temporary_views� r6 z!SuiteRequirements.temporary_viewsc C r r r r r r r �index_reflection� r z"SuiteRequirements.index_reflectionc C r )z>target database supports CREATE INDEX against SQL expressions.r r r r r �indexes_with_expressions� r6 z*SuiteRequirements.indexes_with_expressionsc C r )z8target dialect supports reflection of unique constraintsr r r r r � unique_constraint_reflection� r6 z.SuiteRequirements.unique_constraint_reflectionc C r )z7target dialect supports reflection of check constraintsr r r r r �check_constraint_reflection� r6 z-SuiteRequirements.check_constraint_reflectionc C r )z�target dialect raises IntegrityError when reporting an INSERT with a primary key violation. (hint: it should) r r r r r �$duplicate_key_raises_integrity_error� r) z6SuiteRequirements.duplicate_key_raises_integrity_errorc C r )z3Target database must support VARCHAR with no lengthr r r r r �unbounded_varchar r z#SuiteRequirements.unbounded_varcharc C r )z�Target database/dialect must support Python unicode objects with non-ASCII characters represented, delivered as bound parameters as well as in result rows. r r r r r � unicode_data r, z SuiteRequirements.unicode_datac C r )zRTarget driver must support some degree of non-ascii symbol names. r r r r r � unicode_ddl r z SuiteRequirements.unicode_ddlc C r )z�target dialect supports rendering of a date, time, or datetime as a literal string, e.g. via the TypeEngine.literal_processor() method. r r r r r �datetime_literals r, z#SuiteRequirements.datetime_literalsc C r )zUtarget dialect supports representation of Python datetime.datetime() objects.r r r r r �datetime& r zSuiteRequirements.datetimec C r )zftarget dialect supports representation of Python datetime.datetime() with microsecond objects.r r r r r �datetime_microseconds- r z'SuiteRequirements.datetime_microsecondsc C r )z�target dialect supports representation of Python datetime.datetime() with microsecond objects but only if TIMESTAMP is used.r r r r r �timestamp_microseconds4 r z(SuiteRequirements.timestamp_microsecondsc C r �zutarget dialect supports representation of Python datetime.datetime() objects with historic (pre 1970) values.r r r r r �datetime_historic; r z#SuiteRequirements.datetime_historicc C r )zQtarget dialect supports representation of Python datetime.date() objects.r r r r r �dateB r zSuiteRequirements.datec C r )zPtarget dialect accepts a datetime object as the target of a date column.r r r r r �date_coerces_from_datetimeI r z,SuiteRequirements.date_coerces_from_datetimec C r r� r r r r r � date_historicP r z SuiteRequirements.date_historicc C r )zQtarget dialect supports representation of Python datetime.time() objects.r r r r r �timeW r zSuiteRequirements.timec C r )zbtarget dialect supports representation of Python datetime.time() with microsecond objects.r r r r r �time_microseconds^ r z#SuiteRequirements.time_microsecondsc C r )zttarget database/driver can allow BLOB/BINARY fields to be compared against a bound parameter value. r r r r r �binary_comparisonse r) z$SuiteRequirements.binary_comparisonsc C r )a! target backend supports simple binary literals, e.g. an expression like:: SELECT CAST('foo' AS BINARY) Where ``BINARY`` is the type emitted from :class:`.LargeBinary`, e.g. it could be ``BLOB`` or similar. Basically fails on Oracle. r r r r r �binary_literalsm � z!SuiteRequirements.binary_literalsc C r )z:target dialect supports 'AUTOCOMMIT' as an isolation_levelr r r r r � autocommit} r6 z SuiteRequirements.autocommitc C r )z.target platform implements a native JSON type.r r r r r � json_type� r zSuiteRequirements.json_typec C rs )zO"target platform supports numeric array indexes within a JSON structure)r� r r r r �json_array_indexes� s z$SuiteRequirements.json_array_indexesc C r r r r r r r �(json_index_supplementary_unicode_element� r z:SuiteRequirements.json_index_supplementary_unicode_elementc C r )zRtarget backend has general support for moderately high-precision numerics.r r r r r �precision_numerics_general� r z,SuiteRequirements.precision_numerics_generalc C r )zbtarget backend supports Decimal() objects using E notation to represent very small values.r r r r r �"precision_numerics_enotation_small� r z4SuiteRequirements.precision_numerics_enotation_smallc C r )zbtarget backend supports Decimal() objects using E notation to represent very large values.r r r r r �"precision_numerics_enotation_large� r z4SuiteRequirements.precision_numerics_enotation_largec C r )z�target backend supports values with many digits on both sides, such as 319438950232418390.273596, 87673.594069654243 r r r r r �*precision_numerics_many_significant_digits� r) z<SuiteRequirements.precision_numerics_many_significant_digitsc C r )a- target backend will return a selected Decimal as a Decimal, not a string. e.g.:: expr = decimal.Decimal("15.7563") value = e.scalar( select([literal(expr)]) ) assert value == expr See :ticket:`4036` r r r r r �implicit_decimal_binds� s z(SuiteRequirements.implicit_decimal_bindsc C r )zhtarget database can select an aggregate from a subquery that's also using an aggregate r r r r r �nested_aggregates� r) z#SuiteRequirements.nested_aggregatesc C r )zbtarget database must support ON DELETE CASCADE on a self-referential foreign key r r r r r �recursive_fk_cascade� r) z&SuiteRequirements.recursive_fk_cascadec C r )z�A precision numeric type will return empty significant digits, i.e. a value such as 10.000 will come back in Decimal form with the .000 maintained.r r r r r �-precision_numerics_retains_significant_digits� r) z?SuiteRequirements.precision_numerics_retains_significant_digitsc C r )z�target backend will return native floating point numbers with at least seven decimal places when using the generic Float type. r r r r r � precision_generic_float_type� r) z.SuiteRequirements.precision_generic_float_typec C r )z�target backend can return a floating-point number with four significant digits (such as 15.7563) accurately (i.e. without FP inaccuracies, such as 15.75629997253418). r r r r r �floats_to_four_decimals� r, z)SuiteRequirements.floats_to_four_decimalsc C r )z�target backend doesn't crash when you try to select a NUMERIC value that has a value of NULL. Added to support Pyodbc bug #351. r r r r r �fetch_null_from_numeric� rh z)SuiteRequirements.fetch_null_from_numericc C r )zUTarget database must support an unbounded Text() " "type such as TEXT or CLOBr r r r r � text_type� r zSuiteRequirements.text_typec C r )zTtarget database can persist/return an empty string with a varchar. r r r r r �empty_strings_varchar� r) z'SuiteRequirements.empty_strings_varcharc C r )zRtarget database can persist/return an empty string with an unbounded text.r r r r r �empty_strings_text r z$SuiteRequirements.empty_strings_textc C r )zUtarget database supports use of an unbounded textual field in a WHERE clause.r r r r r �"expressions_against_unbounded_text r z4SuiteRequirements.expressions_against_unbounded_textc C r )z;target driver must support the literal statement 'select 1'r r r r r � selectone r6 zSuiteRequirements.selectonec C r )z(Target database must support savepoints.r r r r r � savepoints r z SuiteRequirements.savepointsc C r )z4Target database must support two-phase transactions.r r r r r �two_phase_transactions r z(SuiteRequirements.two_phase_transactionsc C r )z'Target must support UPDATE..FROM syntaxr r r r r � update_from# r6 z SuiteRequirements.update_fromc C r )z=Target must support DELETE FROM..FROM or DELETE..USING syntaxr r r r r � delete_from( r6 z SuiteRequirements.delete_fromc C r )a� Target must support UPDATE (or DELETE) where the same table is present in a subquery in the WHERE clause. This is an ANSI-standard syntax that apparently MySQL can't handle, such as:: UPDATE documents SET flag=1 WHERE documents.title IN (SELECT max(documents.title) AS title FROM documents GROUP BY documents.user_id ) r r r r r � update_where_target_in_subquery- r� z1SuiteRequirements.update_where_target_in_subqueryc C r )zOtarget database must use a plain percent '%' as the 'modulus' operator.r r r r r � mod_operator_as_percent_sign= r z.SuiteRequirements.mod_operator_as_percent_signc C r )a target backend supports weird identifiers with percent signs in them, e.g. 'some % column'. this is a very weird use case but often has problems because of DBAPIs that use python formatting. It's not a critical use case either. r r r r r �percent_schema_namesC r. z&SuiteRequirements.percent_schema_namesc C r )z�target database supports ordering by a column from a SELECT inside of a UNION E.g. (SELECT id, ...) UNION (SELECT id, ...) ORDER BY id r r r r r �order_by_col_from_unionO rh z)SuiteRequirements.order_by_col_from_unionc C r )a target backend supports ORDER BY a column label within an expression. Basically this:: select data as foo from test order by foo || 'bar' Lots of databases including PostgreSQL don't support this, so this is off by default. r r r r r � order_by_label_with_expressionY s z0SuiteRequirements.order_by_label_with_expressionc s � fdd�}t �|�S )Nc s& z� � | � W dS ty Y dS w )NFT)�get_order_by_collation�NotImplementedErrorrD r r r �checkj s �z3SuiteRequirements.order_by_collation.<locals>.checkrG )r r� r r r �order_by_collationh s z$SuiteRequirements.order_by_collationc C s t � �r )r� �r rE r r r r� s s z(SuiteRequirements.get_order_by_collationc C r )zUTarget driver must support non-ASCII characters being passed at all. r r r r r �unicode_connectionsv r z%SuiteRequirements.unicode_connectionsc C r )z�Target driver must raise a DBAPI-level exception, such as InterfaceError, when the underlying connection has been closed and the execute() method is called. r r r r r �graceful_disconnects} r) z&SuiteRequirements.graceful_disconnectsc C r )zU Target must support simultaneous, independent database connections. r r r r r �independent_connections� r z)SuiteRequirements.independent_connectionsc C r )z9Catchall for a large variety of MySQL on Windows failuresr r r r r �skip_mysql_on_windows� r6 z'SuiteRequirements.skip_mysql_on_windowsc C s t �dd� �S )a Test environment must allow ad-hoc engine/connection creation. DBs that scale poorly for many connections, even when closed, i.e. Oracle, may use the "--low-connections" option which flags this requirement as not present. c S � | j jS r )�options�low_connectionsrD r r r r � � z2SuiteRequirements.ad_hoc_engines.<locals>.<lambda>rG r r r r �ad_hoc_engines� s �z SuiteRequirements.ad_hoc_enginesc C � t �d�S )N�timing_intensive�r � requires_tagr r r r r� � � z"SuiteRequirements.timing_intensivec C r� )N�memory_intensiver� r r r r r� � r� z"SuiteRequirements.memory_intensivec C r? )z�Mark tests that use threading and mock at the same time - stability issues have been observed with coverage + python 3.3 c S s t jo| jjS r )r �py3kr� � has_coveragerD r r r r � s z7SuiteRequirements.threading_with_mock.<locals>.<lambda>z%Stability issues with coverage + py3krG r r r r �threading_with_mock� s �z%SuiteRequirements.threading_with_mockc C r? )Nc S s t jdkS �N)� ��sys� version_infor r r r r � rX z+SuiteRequirements.python2.<locals>.<lambda>z Python version 2.xx is required.rG r r r r �python2� rJ zSuiteRequirements.python2c C r? )Nc S s t jdk S r� r� r r r r r � rX z+SuiteRequirements.python3.<locals>.<lambda>z Python version 3.xx is required.rG r r r r �python3� � �zSuiteRequirements.python3c C r? )Nc S s t jS r )r �cpythonr r r r r � s z+SuiteRequirements.cpython.<locals>.<lambda>zcPython interpreter neededr! r r r r r� � r� zSuiteRequirements.cpythonc s ddl m� t�� fdd�d�S )Nr ��picklec s t j r � jdkp tjdkS )N�cPickle)r� r )r �pypyr r� r� r r� r r r � s � z5SuiteRequirements.non_broken_pickle.<locals>.<lambda>z.Needs cPickle+cPython or newer Python 3 pickle)�sqlalchemy.utilr� r r" r r r� r �non_broken_pickle� s �z#SuiteRequirements.non_broken_picklec C rs )z�target platform must remove all cycles unconditionally when gc.collect() is called, as well as clean out unreferenced subclasses. )r� r r r r �predictable_gc� s z SuiteRequirements.predictable_gcc C r? )z�Test should be skipped if coverage is enabled. This is to block tests that exercise libraries that seem to be sensitive to coverage, such as PostgreSQL notice logging. c S r� r )r� r� rD r r r r � r� z/SuiteRequirements.no_coverage.<locals>.<lambda>z(Issues observed when coverage is enabledrG r r r r � no_coverage� s �z SuiteRequirements.no_coveragec C � dS �NFr r� r r r �_has_mysql_on_windows� � z'SuiteRequirements._has_mysql_on_windowsc C r� r� r r� r r r � _has_mysql_fully_case_sensitive� r� z1SuiteRequirements._has_mysql_fully_case_sensitivec r )Nc � � � � S r )� _has_sqliter r r r r � rX z*SuiteRequirements.sqlite.<locals>.<lambda>rG r r r r �sqlite� s zSuiteRequirements.sqlitec s t �� fdd�d�S )Nc r� r )�_has_cextensionsr r r r r � rX z/SuiteRequirements.cextensions.<locals>.<lambda>zC extensions not installedrG r r r r � cextensions� s �z SuiteRequirements.cextensionsc C s0 ddl m} z|d� W dS ty Y dS w )Nr )� create_enginez sqlite://TF)� sqlalchemyr� � ImportError)r r� r r r r� � s �z SuiteRequirements._has_sqlitec C s, z ddl m}m} W dS ty Y dS w )Nr )� cresultproxy� cprocessorsTF)r� r� r� r� )r r� r� r r r r� � s �z"SuiteRequirements._has_cextensionsc C r r r r r r r �computed_columns r z"SuiteRequirements.computed_columnsN)�r r r �propertyr r r r r r r# r$ r% r& r' r( r* r+ r- r/ r0 r1 r2 r3 r4 r5 r7 r8 r9 r: r; r< r= r> rI rN rP rT rU rY rZ r[ r] r` ra rb rc rd re rf rg rk rn ro rp rq rr ru rv rw rx ry rz r{ r| r} r~ r r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r r r r r s r )�__doc__r� � r r �objectr r r r r r �<module> s
Save
Cancel