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
On how to fetch the latest updates from the pandas repository, follow the steps in `Syncing a Fork <https://help.github.com/articles/syncing-a-fork/>`_:
To fetch the latest updates from the pandas repository, follow the steps in
76
+
`Syncing a Fork <https://help.github.com/articles/syncing-a-fork/>`_: ::
77
+
78
+
git fetch upstream
79
+
git checkout master
80
+
git merge upstream/master
68
81
69
82
70
83
3. Set up a Python environment
@@ -76,19 +89,30 @@ On how to fetch the latest updates from the pandas repository, follow the steps
76
89
**Windows users**: run the next commands in the Anaconda Prompt (found in the Anaconda
77
90
folder of the Start menu).
78
91
79
-
* Activate conda by one of the next (or equivalent, if you know what you're doing):
80
-
* If you chose to prepend Anaconda to your PATH during install adding it to your ``~/.bashrc``, just restart your terminal.
81
-
* Otherwise, run ``export PATH="<path-to-anaconda>/bin:$PATH"`` in your terminal. Keep in mind that it will be active exclusively in the terminal you run this command.
@@ -97,16 +121,24 @@ Besides the Python `.py` files, pandas source code includes C/Cython files
97
121
which need to be compiled in order to run the development version of pandas.
98
122
99
123
.. note::
100
-
**Windows users**: to compile pandas, you need to install `Visual Studio 2017 <https://www.visualstudio.com/>`_. You need Visual Studio Community 2017 (2.5GB download during installation) as a minimum. Visual Studio Code does not support the required Build Tools and will not work.
101
-
Select the workload "Python development" and the option "Python native development tools" on the right side.
124
+
**Windows users**: to compile pandas, you need to install `Visual Studio
125
+
2017 <https://www.visualstudio.com/>`_. You need Visual Studio Community
126
+
2017 (2.5GB download during installation) as a minimum. Visual Studio Code
127
+
does not support the required Build Tools and will not work.
128
+
129
+
Select the workload "Python development" and the option "Python native
130
+
development tools" on the right side.
102
131
103
-
(Users of legacy Python 2.7 should install `Microsoft Visual C++ Compiler for Python 2.7 <https://www.microsoft.com/download/details.aspx?id=44266>`_ instead).
132
+
Users of legacy Python 2.7 should install `Microsoft Visual C++ Compiler
133
+
for Python 2.7 <https://www.microsoft.com/download/details.aspx?id=44266>`_
134
+
instead.
104
135
105
136
After the installation, run the following commands in Anaconda Prompt.
106
137
107
-
To compile these files simply run:
108
-
|``cd <pandas-dir>``
109
-
|``python setup.py build_ext --inplace``
138
+
To compile these files simply run: ::
139
+
140
+
cd <pandas-dir>
141
+
python setup.py build_ext --inplace
110
142
111
143
The process will take several minutes.
112
144
@@ -119,27 +151,30 @@ changes. This will be useful when you have finished your changes, and you want
119
151
to submit a pull request, so they are included in pandas.
120
152
121
153
.. note::
122
-
**Windows users**: run the next commands with Git Bash started at the cloned
154
+
**Windows users**: run the next commands with Git Bash started in the cloned
123
155
pandas folder.
124
156
125
157
Before creating a branch, make sure that you fetched the latest master version
126
-
of the upstream pandas repository. You can do this with:
158
+
of the upstream pandas repository. You can do this with: ::
159
+
160
+
git checkout master
161
+
git pull upstream master --ff-only
127
162
128
-
|``git checkout master``
129
-
|``git pull upstream master --ff-only``
163
+
Then, you can create a new git branch running: ::
130
164
131
-
Then, you can create a new git branch running:
132
-
|``git checkout -b <new_branch_name>``
165
+
git checkout -b <new_branch_name>
133
166
134
167
The branch name should be descriptive of the feature you will work on. For
135
-
example, if you will work on the docstring of the method `head`, you can
136
-
name your branch `docstring_head`.
168
+
example, if you will work on the docstring of the method ``head``, you can
169
+
name your branch ``docstring_head``.
137
170
138
171
If during the sprint you work in more than one docstring, you will need a
0 commit comments