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
added timeMode argument for counting cbc wall-time. (#487)
* added `timeMode` argument for counting cbc wall-time.
* bump pypi version and history
* increased the timeLimit and added seed to be sure to pass the test.
Copy file name to clipboardExpand all lines: doc/source/develop/contribute.rst
+39-14Lines changed: 39 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,21 @@
1
1
How to contribute to PuLP
2
2
======================================
3
3
4
-
This is a minimalistic guid to setup pulp and help you modify the code and send a PR.
4
+
This is a minimalistic guide to setup pulp and help you modify the code and send a PR.
5
+
6
+
The quick summary is:
7
+
8
+
#. Fork the repo.
9
+
#. Clone your forked repo.
10
+
#. Install dependencies.
11
+
#. Make your changes.
12
+
#. Create a test for your changes if needed.
13
+
#. Make sure all the tests pass.
14
+
#. Lint your code with black.
15
+
#. Ensure the docs are accurate.
16
+
#. Submit a Pull Request.
17
+
18
+
5
19
On top of having python installed, we will be using git and the command line. Also, we assume you have a github account and know how to fork a project.
6
20
We will use plain git through the command line but feel free to use the git client of your choice.
7
21
@@ -35,19 +49,6 @@ To build pulp from source we wil get inside the pulp directory, then we will cre
35
49
36
50
This will link the pulp version on your virtual environment with the source files in the pulp directory. You can now use pulp from that virtual environment and you will be using the files in the pulp directory. We assume you have run this successfully for all further steps.
37
51
38
-
Building the documentation
39
-
----------------------------
40
-
41
-
The documentation is based in `Sphinx and reStructuredText <https://www.sphinx-doc.org/en/master/usage/restructuredtext/index.html>`_.
42
-
43
-
To build the documentation::
44
-
45
-
cd pulp/doc
46
-
make html
47
-
48
-
A folder named html will be created inside the ``build/`` directory. The home page for the documentation is ``doc/build/html/index.html`` which can be opened in a browser.
49
-
You only need to execute ``make html`` to rebuild the docs each time.
50
-
51
52
Running tests
52
53
----------------
53
54
@@ -63,6 +64,30 @@ Creating a test
63
64
64
65
When you fix an issue in pulp or add a functionality, you should add a test to the repository. For this you should go to the file `tests/test_pulp.py` and add a new method that tests your change.
We use `the black formatter <https://black.readthedocs.io/en/stable/>`_. Before sending your changes, be sure to execute the black package to style the resulting files.
71
+
The quickest way to do this is to run:
72
+
73
+
python -m black pulp
74
+
75
+
And it will do the changes directly on the files.
76
+
77
+
The easiest way is to integrate it inside your IDE so it runs every time you save a file. Learn how to do that `in the black integration docs <https://black.readthedocs.io/en/stable/integrations/editors.html>`_.
78
+
79
+
Building the documentation
80
+
----------------------------
81
+
82
+
The documentation is based in `Sphinx and reStructuredText <https://www.sphinx-doc.org/en/master/usage/restructuredtext/index.html>`_.
83
+
84
+
To build the documentation::
85
+
86
+
cd pulp/doc
87
+
make html
88
+
89
+
A folder named html will be created inside the ``build/`` directory. The home page for the documentation is ``doc/build/html/index.html`` which can be opened in a browser.
90
+
You only need to execute ``make html`` to rebuild the docs each time.
0 commit comments