You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: LICENSE
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
Copyright 2018 MGH & BWH Center for Clinical Data Science
1
+
Copyright 2020 MGH Computational Pathology
2
2
3
3
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The :mod:`dicomweb_client` package can be installed in *develop* mode for local development:
13
13
@@ -30,19 +30,25 @@ Before creating a pull request on Github, read the coding style guideline, run t
30
30
Coding style
31
31
------------
32
32
33
-
Code must comply with `PEP 8 <https://www.python.org/dev/peps/pep-0008/>`_. The `flake8 <http://flake8.pycqa.org/en/latest/>`_ package is used to enforce compliance.
33
+
Code must comply with `PEP 8 <https://www.python.org/dev/peps/pep-0008/>`_.
34
+
The `flake8 <http://flake8.pycqa.org/en/latest/>`_ package is used to enforce compliance.
34
35
35
-
The project uses `numpydoc <https://github.com/numpy/numpydoc/>`_ for documenting code according to `PEP 257 <https://www.python.org/dev/peps/pep-0257/>`_ docstring conventions. Further information and examples for the NumPy style can be found at the `NumPy Github repository <https://github.com/numpy/numpy/blob/master/doc/HOWTO_DOCUMENT.rst.txt>`_ and the website of the `Napoleon sphinx extension <https://sphinxcontrib-napoleon.readthedocs.io/en/latest/example_numpy.html#example-numpy>`_.
36
+
The project uses `numpydoc <https://github.com/numpy/numpydoc/>`_ for documenting code according to `PEP 257 <https://www.python.org/dev/peps/pep-0257/>`_ docstring conventions.
37
+
Further information and examples for the NumPy style can be found at the `NumPy Github repository <https://github.com/numpy/numpy/blob/master/doc/HOWTO_DOCUMENT.rst.txt>`_ and the website of the `Napoleon sphinx extension <https://sphinxcontrib-napoleon.readthedocs.io/en/latest/example_numpy.html#example-numpy>`_.
36
38
37
-
All API classes, functions and modules must be documented (including "private" functions and methods). Each docstring must describe input parameters and return values. Types must be specified using type hints as specified by `PEP 484 <https://www.python.org/dev/peps/pep-0484/>`_ (see `typing <https://docs.python.org/3/library/typing.html>`_ module).
39
+
All API classes, functions and modules must be documented (including "private" functions and methods).
40
+
Each docstring must describe input parameters and return values.
41
+
Types must be specified using type hints as specified by `PEP 484 <https://www.python.org/dev/peps/pep-0484/>`_ (see `typing <https://docs.python.org/3/library/typing.html>`_ module) in both the function definition as well as the docstring.
38
42
39
43
40
44
.. _running-tests:
41
45
42
46
Running tests
43
47
-------------
44
48
45
-
The project uses `pytest <http://doc.pytest.org/en/latest/>`_ to write and runs unit tests. Tests should be placed in a separate ``tests`` folder within the package root folder. Files containing actual test code should follow the pattern ``test_*.py``.
49
+
The project uses `pytest <http://doc.pytest.org/en/latest/>`_ to write and runs unit tests.
50
+
Tests should be placed in a separate ``tests`` folder within the package root folder.
51
+
Files containing actual test code should follow the pattern ``test_*.py``.
0 commit comments