Skip to content

Commit 924c132

Browse files
timgates42bluetech
authored andcommitted
docs: Fix a few typos
There are small typos in: - docs/database.rst - docs/managing_python_path.rst - tests/test_manage_py_scan.py Fixes: - Should read `implicitly` rather than `impliclity`. - Should read `implicitly` rather than `implicilty`. - Should read `explicitly` rather than `explictly`.
1 parent cf6b229 commit 924c132

File tree

3 files changed

+4
-4
lines changed

3 files changed

+4
-4
lines changed

docs/database.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -386,7 +386,7 @@ Populate the test database if you don't use transactional or live_server
386386
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
387387

388388
If you are using the :func:`pytest.mark.django_db` marker or :fixture:`db`
389-
fixture, you probably don't want to explictly handle transactions in your
389+
fixture, you probably don't want to explicitly handle transactions in your
390390
tests. In this case, it is sufficient to populate your database only
391391
once. You can put code like this in ``conftest.py``::
392392

docs/managing_python_path.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ Managing the Python path
55

66
pytest needs to be able to import the code in your project. Normally, when
77
interacting with Django code, the interaction happens via ``manage.py``, which
8-
will implicilty add that directory to the Python path.
8+
will implicitly add that directory to the Python path.
99

1010
However, when Python is started via the ``pytest`` command, some extra care is
1111
needed to have the Python path setup properly. There are two ways to handle

tests/test_manage_py_scan.py

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,9 +4,9 @@
44
@pytest.mark.django_project(project_root="django_project_root", create_manage_py=True)
55
def test_django_project_found(django_testdir) -> None:
66
# XXX: Important: Do not chdir() to django_project_root since runpytest_subprocess
7-
# will call "python /path/to/pytest.py", which will impliclity add cwd to
7+
# will call "python /path/to/pytest.py", which will implicitly add cwd to
88
# the path. By instead calling "python /path/to/pytest.py
9-
# django_project_root", we avoid impliclity adding the project to sys.path
9+
# django_project_root", we avoid implicitly adding the project to sys.path
1010
# This matches the behaviour when pytest is called directly as an
1111
# executable (cwd is not added to the Python path)
1212

0 commit comments

Comments
 (0)