diff options
author | Mike Bayer <classic@zzzcomputing.com> | 2015-05-04 12:57:13 -0400 |
---|---|---|
committer | Mike Bayer <classic@zzzcomputing.com> | 2015-05-04 12:57:13 -0400 |
commit | 0ea37679dd6132dc62aad14ef041f05e79c70d18 (patch) | |
tree | cd8eda19f6f6d644dff5f2507aaad3232d130092 | |
parent | c75be37640a19990d385a8059b61319af6818358 (diff) | |
parent | 239cf8030667d50790d104580286370efcb32cb7 (diff) | |
download | alembic-0ea37679dd6132dc62aad14ef041f05e79c70d18.tar.gz |
Merged in jdanjou/alembic/jd/typo-doc-comparator (pull request #44)
Fix typo in autogenerate documentation
-rw-r--r-- | docs/build/autogenerate.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/build/autogenerate.rst b/docs/build/autogenerate.rst index 93f6000..12790da 100644 --- a/docs/build/autogenerate.rst +++ b/docs/build/autogenerate.rst @@ -410,7 +410,7 @@ The order of precedence regarding the type itself implementing ``compare_against_backend`` is that the :paramref:`.EnvironmentContext.configure.compare_type` callable is favored first; if it returns ``None``, then the ``compare_against_backend`` method -will be used, if present on the metadata type. If that reutrns ``None``, +will be used, if present on the metadata type. If that returns ``None``, then a basic check for type equivalence is run. .. versionadded:: 0.7.6 - added support for the ``compare_against_backend()`` |