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: README.rst
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -325,7 +325,7 @@ Tests are written in the ``tests`` directory and processed using `PyTest <https:
325
325
Python Version
326
326
--------------
327
327
328
-
STUMPY supports `Python 3.8+ <https://python3statement.org/>`__ and, due to the use of unicode variable names/identifiers, is not compatible with Python 2.x. Given the small dependencies, STUMPY may work on older versions of Python but this is beyond the scope of our support and we strongly recommend that you upgrade to the most recent version of Python.
328
+
STUMPY supports `Python 3.9+ <https://python3statement.org/>`__ and, due to the use of unicode variable names/identifiers, is not compatible with Python 2.x. Given the small dependencies, STUMPY may work on older versions of Python but this is beyond the scope of our support and we strongly recommend that you upgrade to the most recent version of Python.
":::{admonition} Instructions for Pulling Main into a Development Branch\n",
178
+
":class: toggle\n",
179
+
"1. Open a terminal\n",
180
+
"2. Change the current working directory to your local development repository (e.g., cd Git/stumpy_dev.git)\n",
181
+
"3. Check out your local development branch (e.g., git switch some_new_feature)\n",
182
+
"4. Commit all changes in your local development branch (e.g., git add some_file.py and git commit)\n",
183
+
"5. Fetch the branches and their respective commits from the upstream repository (e.g., git fetch upstream)\n",
184
+
"6. Check out your fork's local default branch (e.g., git checkout main)\n",
185
+
"7. Merge the changes from the upstream default branch - in this case, upstream/main - into your local default branch (e.g., git merge upstream/main). This brings your fork's default branch into sync with the upstream repository, without losing your local changes.\n",
186
+
"8. If your local main branch didn't have any unique commits, Git will perform a fast-forward. Otherwise, if your local main branch had unique commits, you may need to resolve conflicts. Note that this does not affect your development branch!\n",
187
+
"9. Next, switch over to your development branch (e.g., git switch some_new_feature)\n",
188
+
"10. Finally, merge the main branch into your development branch (e.g., git merge main)\n",
189
+
" - You may see something like the following, if you do, you will need to open up the files tagged with CONFLICT and resolve the merge conflicts. Once that's done, you will need to commit the changes and push the commit (e.g., git push) back to Github.\n",
190
+
"\n",
191
+
"```\n",
192
+
"git merge main\n",
193
+
"Auto-merging stumpy/aamp_stimp.py\n",
194
+
"Auto-merging stumpy/core.py\n",
195
+
"Auto-merging stumpy/mpdist.py\n",
196
+
"CONFLICT (content): Merge conflict in stumpy/mpdist.py\n",
197
+
"Auto-merging stumpy/mstumped.py\n",
198
+
"CONFLICT (content): Merge conflict in stumpy/mstumped.py\n",
199
+
"Auto-merging stumpy/ostinato.py\n",
200
+
"Auto-merging stumpy/stimp.py\n",
201
+
"CONFLICT (content): Merge conflict in stumpy/stimp.py\n",
202
+
"Auto-merging stumpy/stumped.py\n",
203
+
"CONFLICT (content): Merge conflict in stumpy/stumped.py\n",
204
+
"Automatic merge failed; fix conflicts and then commit the result.\n",
205
+
"You will need to open up the files tagged with CONFLICT and resolve the merge conflicts. Once that's done, you will need to commit the changes and push the commit (e.g., git push) back to Github.\n",
0 commit comments