Skip to content

Commit fb408b8

Browse files
fardynfardyn
fardyn
and
fardyn
authored
fix typos (#13038)
* fix typos * fix typos --------- Co-authored-by: fardyn <fa.alizadeh@pm.me>
1 parent b7a8ea1 commit fb408b8

61 files changed

Lines changed: 98 additions & 98 deletions

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎doc/build/changelog/changelog_09.rst‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -76,7 +76,7 @@
7676
Fixed bug where when using extended attribute instrumentation system,
7777
the correct exception would not be raised when :func:`.class_mapper`
7878
were called with an invalid input that also happened to not
79-
be weak referencable, such as an integer.
79+
be weak referenceable, such as an integer.
8080

8181
.. change::
8282
:tags: bug, tests, pypy

‎doc/build/changelog/changelog_14.rst‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6691,7 +6691,7 @@ This document details individual issue-level changes made throughout
66916691
:tickets: 5735
66926692

66936693
Improved the unit of work topological sorting system such that the
6694-
toplogical sort is now deterministic based on the sorting of the input set,
6694+
topological sort is now deterministic based on the sorting of the input set,
66956695
which itself is now sorted at the level of mappers, so that the same inputs
66966696
of affected mappers should produce the same output every time, among
66976697
mappers / tables that don't have any dependency on each other. This further
@@ -7946,7 +7946,7 @@ This document details individual issue-level changes made throughout
79467946
The bulk update and delete methods :meth:`.Query.update` and
79477947
:meth:`.Query.delete`, as well as their 2.0-style counterparts, now make
79487948
use of RETURNING when the "fetch" strategy is used in order to fetch the
7949-
list of affected primary key identites, rather than emitting a separate
7949+
list of affected primary key identities, rather than emitting a separate
79507950
SELECT, when the backend in use supports RETURNING. Additionally, the
79517951
"fetch" strategy will in ordinary cases not expire the attributes that have
79527952
been updated, and will instead apply the updated values directly in the

‎doc/build/changelog/changelog_20.rst‎

Lines changed: 21 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -577,7 +577,7 @@
577577
:tags: bug, postgresql
578578
:tickets: 12728
579579

580-
Re-raise catched ``CancelledError`` in the terminate method of the
580+
Re-raise caught ``CancelledError`` in the terminate method of the
581581
asyncpg dialect to avoid possible hangs of the code execution.
582582

583583

@@ -738,7 +738,7 @@
738738
into a SQL expression in a boolean context, for programs where future
739739
annotations mode was not enabled. This case is now handled explicitly and
740740
a new error message has also been tailored for this case. In addition, as
741-
there are at least half a dozen distinct error scenarios for intepretation
741+
there are at least half a dozen distinct error scenarios for interpretation
742742
of the :class:`.Mapped` construct, these scenarios have all been unified
743743
under a new subclass of :class:`.ArgumentError` called
744744
:class:`.MappedAnnotationError`, to provide some continuity between these
@@ -978,7 +978,7 @@
978978
``connection.transaction()`` call sent to asyncpg sends ``None`` for
979979
``isolation_level`` if not otherwise set in the SQLAlchemy dialect/wrapper,
980980
thereby allowing asyncpg to make use of the server level setting for
981-
``isolation_level`` in the absense of a client-level setting. Previously,
981+
``isolation_level`` in the absence of a client-level setting. Previously,
982982
this behavior of asyncpg was blocked by a hardcoded ``read_committed``.
983983

984984
.. change::
@@ -1581,7 +1581,7 @@
15811581
versioned table needs to default to the most recent version number in the
15821582
history table on INSERT, to suit the use case of a table where rows are
15831583
deleted, and can then be replaced by new rows that re-use the same primary
1584-
key identity. This fix adds an additonal SELECT query per INSERT in the
1584+
key identity. This fix adds an additional SELECT query per INSERT in the
15851585
main table, which may be inefficient; for cases where primary keys are not
15861586
re-used, the default function may be omitted. Patch courtesy Philipp H.
15871587
v. Loewenfeld.
@@ -1761,7 +1761,7 @@
17611761

17621762
Fixed internal typing issues to establish compatibility with mypy 1.11.0.
17631763
Note that this does not include issues which have arisen with the
1764-
deprecated mypy plugin used by SQLAlchemy 1.4-style code; see the addiional
1764+
deprecated mypy plugin used by SQLAlchemy 1.4-style code; see the additional
17651765
change note for this plugin indicating revised compatibility.
17661766

17671767
.. changelog::
@@ -1943,8 +1943,8 @@
19431943
:tickets: 11306
19441944

19451945
Fixed issue in cursor handling which affected handling of duplicate
1946-
:class:`_sql.Column` or similar objcts in the columns clause of
1947-
:func:`_sql.select`, both in combination with arbitary :func:`_sql.text()`
1946+
:class:`_sql.Column` or similar objects in the columns clause of
1947+
:func:`_sql.select`, both in combination with arbitrary :func:`_sql.text()`
19481948
clauses in the SELECT list, as well as when attempting to retrieve
19491949
:meth:`_engine.Result.mappings` for the object, which would lead to an
19501950
internal error.
@@ -2055,7 +2055,7 @@
20552055

20562056
Fixed issue in :ref:`engine_insertmanyvalues` feature where using a primary
20572057
key column with an "inline execute" default generator such as an explicit
2058-
:class:`.Sequence` with an explcit schema name, while at the same time
2058+
:class:`.Sequence` with an explicit schema name, while at the same time
20592059
using the
20602060
:paramref:`_engine.Connection.execution_options.schema_translate_map`
20612061
feature would fail to render the sequence or the parameters properly,
@@ -2078,7 +2078,7 @@
20782078
"Can't match sentinel values in result set to parameter sets". Rather than
20792079
attempt to further explain and document this implementation detail of the
20802080
"insertmanyvalues" feature including a public version of the new
2081-
method, the approach is intead revised to no longer need this extra
2081+
method, the approach is instead revised to no longer need this extra
20822082
conversion step, and the logic that does the comparison now works on the
20832083
pre-converted bound parameter value compared to the post-result-processed
20842084
value, which should always be of a matching datatype. In the unusual case
@@ -2094,7 +2094,7 @@
20942094

20952095
Fixed regression from version 2.0.28 caused by the fix for :ticket:`11085`
20962096
where the newer method of adjusting post-cache bound parameter values would
2097-
interefere with the implementation for the :func:`_orm.subqueryload` loader
2097+
interfere with the implementation for the :func:`_orm.subqueryload` loader
20982098
option, which has some more legacy patterns in use internally, when
20992099
the additional loader criteria feature were used with this loader option.
21002100

@@ -2674,7 +2674,7 @@
26742674
parameter for new style bulk ORM inserts, allowing ``render_nulls=True`` as
26752675
an execution option. This allows for bulk ORM inserts with a mixture of
26762676
``None`` values in the parameter dictionaries to use a single batch of rows
2677-
for a given set of dicationary keys, rather than breaking up into batches
2677+
for a given set of dictionary keys, rather than breaking up into batches
26782678
that omit the NULL columns from each INSERT.
26792679

26802680
.. seealso::
@@ -2857,7 +2857,7 @@
28572857
However, mariadb-connector does not support invoking ``cursor.rowcount``
28582858
after the cursor itself is closed, raising an error instead. Generic test
28592859
support has been added to ensure all backends support the allowing
2860-
:attr:`.Result.rowcount` to succceed (that is, returning an integer
2860+
:attr:`.Result.rowcount` to succeed (that is, returning an integer
28612861
value with -1 for "not available") after the result is closed.
28622862

28632863

@@ -3006,7 +3006,7 @@
30063006
:class:`.Update` and :class:`.Delete` to not interfere with the target
30073007
"from" object passed to the statement, such as when passing an ORM-mapped
30083008
:class:`_orm.aliased` construct that should be maintained within a phrase
3009-
like "UPDATE FROM". Cases like ORM session synchonize using "SELECT"
3009+
like "UPDATE FROM". Cases like ORM session synchronize using "SELECT"
30103010
statements such as with MySQL/ MariaDB will still have issues with
30113011
UPDATE/DELETE of this form so it's best to disable synchonize_session when
30123012
using DML statements of this type.
@@ -3360,7 +3360,7 @@
33603360
Fixed regression caused by improvements to PostgreSQL URL parsing in
33613361
:ticket:`10004` where "host" query string arguments that had colons in
33623362
them, to support various third party proxy servers and/or dialects, would
3363-
not parse correctly as these were evaluted as ``host:port`` combinations.
3363+
not parse correctly as these were evaluated as ``host:port`` combinations.
33643364
Parsing has been updated to consider a colon as indicating a ``host:port``
33653365
value only if the hostname contains only alphanumeric characters with dots
33663366
or dashes only (e.g. no slashes), followed by exactly one colon followed by
@@ -3735,13 +3735,13 @@
37353735
Fixed issue where the :paramref:`.ColumnOperators.like.escape` and similar
37363736
parameters did not allow an empty string as an argument that would be
37373737
passed through as the "escape" character; this is a supported syntax by
3738-
PostgreSQL. Pull requset courtesy Martin Caslavsky.
3738+
PostgreSQL. Pull request courtesy Martin Caslavsky.
37393739

37403740
.. change::
37413741
:tags: bug, orm
37423742
:tickets: 9869
37433743

3744-
Improved the argument chacking on the
3744+
Improved the argument checking on the
37453745
:paramref:`_orm.registry.map_imperatively.local_table` parameter of the
37463746
:meth:`_orm.registry.map_imperatively` method, ensuring only a
37473747
:class:`.Table` or other :class:`.FromClause` is passed, and not an
@@ -5209,7 +5209,7 @@
52095209
:paramref:`_orm.Mapper.primary_key` parameter to be specified within
52105210
``__mapper_args__`` when using :func:`_orm.mapped_column`. Despite this
52115211
usage being directly in the 2.0 documentation, the :class:`_orm.Mapper` was
5212-
not accepting the :func:`_orm.mapped_column` construct in this context. Ths
5212+
not accepting the :func:`_orm.mapped_column` construct in this context. This
52135213
feature was already working for the :paramref:`_orm.Mapper.version_id_col`
52145214
and :paramref:`_orm.Mapper.polymorphic_on` parameters.
52155215

@@ -6439,7 +6439,7 @@
64396439
Improved the typing for :class:`.sessionmaker` and
64406440
:class:`.async_sessionmaker`, so that the default type of their return value
64416441
will be :class:`.Session` or :class:`.AsyncSession`, without the need to
6442-
type this explicitly. Previously, Mypy would not automaticaly infer these
6442+
type this explicitly. Previously, Mypy would not automatically infer these
64436443
return types from its generic base.
64446444

64456445
As part of this change, arguments for :class:`.Session`,
@@ -6590,7 +6590,7 @@
65906590
:tickets: 8718
65916591

65926592
Fixed issue in new dataclass mapping feature where a column declared on the
6593-
decalrative base / abstract base / mixin would leak into the constructor
6593+
declarative base / abstract base / mixin would leak into the constructor
65946594
for an inheriting subclass under some circumstances.
65956595

65966596
.. change::
@@ -6746,7 +6746,7 @@
67466746
being mentioned in other parts of the query. If other elements of the
67476747
:class:`_sql.Select` also generate FROM clauses, such as the columns clause
67486748
or WHERE clause, these will render after the clauses delivered by
6749-
:meth:`_sql.Select.select_from` assuming they were not explictly passed to
6749+
:meth:`_sql.Select.select_from` assuming they were not explicitly passed to
67506750
:meth:`_sql.Select.select_from` also. This improvement is useful in those
67516751
cases where a particular database generates a desirable query plan based on
67526752
a particular ordering of FROM clauses and allows full control over the
@@ -7233,7 +7233,7 @@
72337233
visible in messaging as well as typing, have been changed to more succinct
72347234
names which also match the name of their constructing function (with
72357235
different casing), in all cases maintaining aliases to the old names for
7236-
the forseeable future:
7236+
the foreseeable future:
72377237

72387238
* :class:`_orm.RelationshipProperty` becomes an alias for the primary name
72397239
:class:`_orm.Relationship`, which is constructed as always from the

‎doc/build/changelog/migration_20.rst‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2192,7 +2192,7 @@ Therefore the best strategy for migrating from "dynamic" is to **wait until
21922192
the application is fully running on 2.0**, then migrate directly from
21932193
:class:`.AppenderQuery`, which is the collection type used by the "dynamic"
21942194
strategy, to :class:`.WriteOnlyCollection`, which is the collection type
2195-
used by hte "write_only" strategy.
2195+
used by the "write_only" strategy.
21962196

21972197
Some techniques are available to use ``lazy="dynamic"`` under 1.4 in a more
21982198
"2.0" style however. There are two ways to achieve 2.0 style querying that's in

‎doc/build/changelog/unreleased_21/10821.rst‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,5 +7,5 @@
77
type are now deprecated for removal; these two methods along with
88
:func:`_postgresql.Any` and :func:`_postgresql.All` have been legacy for
99
some time as they are superseded by the :func:`_sql.any_` and
10-
:func:`_sql.all_` functions, which feature more intutive use.
10+
:func:`_sql.all_` functions, which feature more intuitive use.
1111

‎doc/build/changelog/unreleased_21/11349.rst‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,6 @@
66
interface to correctly raise ``TypeError`` for invalid use of the ``|``,
77
``&``, ``^``, and ``-`` operators, as well as the in-place mutation
88
versions of these methods, to match the behavior of standard Python
9-
``set()`` as well as SQLAlchemy ORM's "intstrumented" set implementation.
9+
``set()`` as well as SQLAlchemy ORM's "instrumented" set implementation.
1010

1111

‎doc/build/changelog/unreleased_21/12195.rst‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@
1212
(so-called NewSQL) or other novel styles of database that introduce new
1313
clauses to these statements. A new example suite is included which
1414
illustrates the ``QUALIFY`` SQL construct used by several NewSQL databases
15-
which includes a cachable implementation as well as a test suite.
15+
which includes a cacheable implementation as well as a test suite.
1616

1717
.. seealso::
1818

‎doc/build/changelog/unreleased_21/7066.rst‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@
66
similar statements, via a new statement-only
77
:meth:`.ExecutableStatement.params` method which works more efficiently and
88
correctly than the previous implementations available from
9-
:class:`.ClauseElement`, by assocating the given parameter dictionary with
9+
:class:`.ClauseElement`, by associating the given parameter dictionary with
1010
the statement overall rather than cloning the statement and rewriting its
1111
bound parameters. The :meth:`_sql.ClauseElement.params` and
1212
:meth:`_sql.ClauseElement.unique_params` methods, when called on an object

‎doc/build/changelog/unreleased_21/8047.rst‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,8 +7,8 @@
77
on a common base :class:`.EmulatedDBAPIException`, which is now what's
88
available from the :attr:`.StatementException.orig` attribute on a
99
SQLAlchemy :class:`.DBAPIError` object. Within :class:`.EmulatedDBAPIException`
10-
and the subclasses in its hiearchy, the original driver-level exception is
11-
also now avaliable via the :attr:`.EmulatedDBAPIException.orig` attribute,
10+
and the subclasses in its hierarchy, the original driver-level exception is
11+
also now available via the :attr:`.EmulatedDBAPIException.orig` attribute,
1212
and is also available from :class:`.DBAPIError` directly using the
1313
:attr:`.DBAPIError.driver_exception` attribute.
1414

‎doc/build/orm/basic_relationships.rst‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -804,10 +804,10 @@ and ``Child.parent_associations -> Association.parent``::
804804
)
805805
extra_data: Mapped[Optional[str]]
806806

807-
# association between Assocation -> Child
807+
# association between Association -> Child
808808
child: Mapped["Child"] = relationship(back_populates="parent_associations")
809809

810-
# association between Assocation -> Parent
810+
# association between Association -> Parent
811811
parent: Mapped["Parent"] = relationship(back_populates="child_associations")
812812

813813

0 commit comments

Comments
 (0)