summaryrefslogtreecommitdiff
path: root/README.dialects.rst
diff options
context:
space:
mode:
authorGord Thompson <gord@gordthompson.com>2020-04-16 16:06:36 -0600
committerGord Thompson <gord@gordthompson.com>2020-04-16 16:06:36 -0600
commit405fc9717048b0adc852a72da540048df7a8142a (patch)
tree95ad55122e2437d2d49f45ea9c5054f26fb48d79 /README.dialects.rst
parent2f617f56f2acdce00b88f746c403cf5ed66d4d27 (diff)
downloadsqlalchemy-405fc9717048b0adc852a72da540048df7a8142a.tar.gz
Rename py.test to pytest
Change-Id: I431e1ef41e26d490343204a75a5c097768749768
Diffstat (limited to 'README.dialects.rst')
-rw-r--r--README.dialects.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/README.dialects.rst b/README.dialects.rst
index b300128bb..e4bf7f2d2 100644
--- a/README.dialects.rst
+++ b/README.dialects.rst
@@ -6,7 +6,7 @@ Developing new Dialects
When studying this file, it's probably a good idea to also
familiarize with the README.unittests.rst file, which discusses
- SQLAlchemy's usage and extension of the py.test test runner.
+ SQLAlchemy's usage and extension of the pytest test runner.
While SQLAlchemy includes many dialects within the core distribution, the
trend for new dialects should be that they are published as external
@@ -154,7 +154,7 @@ Key aspects of this file layout include:
test runner so that exclusions specific to the dialect take place::
cd /path/to/sqlalchemy
- py.test -v \
+ pytest -v \
--requirements sqlalchemy_access.requirements:Requirements \
--dburi access+pyodbc://admin@access_test