@@ -309,22 +309,22 @@ To run the tests locally, install the ``test`` dependencies specified in the
309
309
file. See :ref: `installation ` instructions for more information.
310
310
311
311
pvlib's unit tests can easily be run by executing ``pytest `` on the
312
- pvlib directory:
312
+ pvlib directory::
313
313
314
- `` pytest pvlib ``
314
+ pytest pvlib
315
315
316
- or, for a single module:
316
+ or, for a single module::
317
317
318
- `` pytest pvlib/test/test_clearsky.py ``
318
+ pytest pvlib/test/test_clearsky.py
319
319
320
- or, for a single test:
320
+ or, for a single test::
321
321
322
- `` pytest pvlib/test/test_clearsky.py::test_ineichen_nans ``
322
+ pytest pvlib/test/test_clearsky.py::test_ineichen_nans
323
323
324
324
We suggest using pytest's ``--pdb `` flag to debug test failures rather
325
- than using ``print `` or ``logging `` calls. For example:
325
+ than using ``print `` or ``logging `` calls. For example::
326
326
327
- `` pytest pvlib --pdb ``
327
+ pytest pvlib --pdb
328
328
329
329
will drop you into the
330
330
`pdb debugger <https://docs.python.org/3/library/pdb.html >`_ at the
@@ -333,9 +333,9 @@ code does not use ``print`` or ``logging`` calls, and this also applies
333
333
to the test suite (with rare exceptions).
334
334
335
335
To include all network-dependent tests, include the ``--remote-data `` flag to
336
- your ``pytest `` call:
336
+ your ``pytest `` call::
337
337
338
- `` pytest pvlib --remote-data ``
338
+ pytest pvlib --remote-data
339
339
340
340
And consider adding ``@pytest.mark.remote_data `` to any network dependent test
341
341
you submit for a PR.
@@ -460,3 +460,8 @@ If this documentation is unclear, help us improve it! Consider looking
460
460
at the `pandas
461
461
documentation <http://pandas.pydata.org/pandas-docs/stable/
462
462
contributing.html> `_ for inspiration.
463
+
464
+ Code of Conduct
465
+ ~~~~~~~~~~~~~~~
466
+ All contributors are expected to adhere to the `Contributor Code of Conduct
467
+ <https://github.com/pvlib/pvlib-python/blob/master/CODE_OF_CONDUCT.md#contributor-covenant-code-of-conduct> `_.
0 commit comments