forked from spyder-ide/spyder
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge remote-tracking branch 'spyder-ide/3.x' into Spyder--Fix-to-issue-
- Loading branch information
Showing
116 changed files
with
5,379 additions
and
2,714 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,135 @@ | ||
# Contributing to Spyder-IDE | ||
|
||
:+1::tada: First off, thanks for taking the time to contribute to Spyder! :tada::+1: | ||
|
||
## General Guidelines | ||
|
||
This page documents at a very high level how to contribute to Spyder. | ||
Please Check the | ||
[Spyder IDE Contributor Documentation](https://github.com/spyder-ide/spyder/wiki/Contributing-to-Spyder) | ||
for a more detailed guide on how to contribute to the Spyder. | ||
|
||
|
||
## Setting Up a Development Environment | ||
|
||
|
||
### Cloning the repo | ||
|
||
```bash | ||
$ git clone https://github.com/spyder-ide/spyder.git | ||
``` | ||
|
||
### Creating a conda environment or virtualenv | ||
|
||
If you use Anaconda you can create a conda environment with | ||
these instructions | ||
|
||
```bash | ||
$ conda create -n spyder-dev python=3 | ||
$ source activate spyder-dev | ||
``` | ||
|
||
You can also use `virtualenv` on Linux, but `conda` is preferred: | ||
|
||
```bash | ||
$ mkvirtualenv spyder-dev | ||
$ workon spyder-dev | ||
``` | ||
|
||
### Installing dependencies | ||
|
||
After you have created your development environment, you need to install | ||
Spyder necessary dependencies. For that you need to go to the directory | ||
where your git clone is placed and run: | ||
|
||
```bash | ||
$ conda install --file requirements/requirements.txt | ||
``` | ||
|
||
or using pip and virtualenv: | ||
|
||
```bash | ||
$ pip install -r requirements/requirements.txt | ||
``` | ||
|
||
*Note*: If you are using pip, you also need to install a Qt binding | ||
package. This can be achieved by running | ||
|
||
```bash | ||
$ pip install pyqt5 | ||
``` | ||
|
||
### Running Spyder | ||
|
||
To start Spyder directly from your clone, i.e. without installing it to your | ||
environment, you need to run | ||
|
||
```bash | ||
$ python bootstrap.py | ||
``` | ||
|
||
**Important Note**: You need to restart Spyder after any change you do to its | ||
source code. This is the only way to test your new code. | ||
|
||
## Spyder Branches | ||
|
||
When you start to work on a new pull request (PR), you need to be sure that your | ||
feature branch is a child of the right Spyder branch, and also that you make | ||
your PR on Github against it. | ||
|
||
Besides, issues are marked with a milestone that indicates the correct branch | ||
to use, like this: | ||
|
||
* Use the `3.1.x` branch for bugfixes only (milestones `v3.1.1`, `v3.1.2`, `v3.1.3`, | ||
etc) | ||
|
||
* Use the `3.x` branch to introduce new features that don't require major internal | ||
changes (milestones `v3.1`, `v3.2`, `v3.3`, etc). | ||
|
||
* Use `master` to introduce new features that break compatibility with previous | ||
Spyder versions (Milestone `v4.0beta1`, `v4.0beta2`, etc). | ||
|
||
|
||
You can also submit bugfixes to `3.x` or `master` for errors that are only present in | ||
those branches. | ||
|
||
So to start working on a new PR, you need to follow these commands: | ||
|
||
```bash | ||
$ git checkout <branch> | ||
$ git pull upstream <branch> | ||
$ git checkout -b name-new-branch | ||
``` | ||
|
||
### Changing base branch | ||
|
||
If you started your work in the wrong branch, or want to backport it, you could | ||
change the base branch using `git rebase --onto`, like this: | ||
|
||
```bash | ||
$ git rebase --onto <new_base> <old_base> <branch> | ||
``` | ||
|
||
For example, backporting `my_branch` from `master` to `3.x`: | ||
|
||
```bash | ||
$ git rebase --onto 3.x master my_branch | ||
``` | ||
|
||
## Running Tests | ||
|
||
Install our test dependencies: | ||
|
||
```bash | ||
$ conda install --file requirements/test_requirements.txt -c spyder-ide | ||
``` | ||
|
||
or using pip | ||
```bash | ||
$ pip install -r requirements/test_requirements.txt | ||
``` | ||
|
||
To run Spyder test suite, please use: | ||
```bash | ||
$ python runtests.py | ||
``` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,21 @@ | ||
#!/bin/bash | ||
|
||
export CONDA_DEPENDENCIES_FLAGS="--quiet" | ||
export CONDA_DEPENDENCIES="rope pyflakes sphinx pygments pylint psutil nbconvert \ | ||
qtawesome pickleshare qtpy pyzmq chardet mock nomkl pandas \ | ||
pytest pytest-cov numpydoc scipy cython pillow" | ||
export PIP_DEPENDENCIES="coveralls pytest-qt pytest-xvfb flaky jedi pycodestyle" | ||
|
||
# Download and install miniconda and conda/pip dependencies | ||
# with astropy helpers | ||
export PY_VERSIONS=($PY_VERSIONS) | ||
export TRAVIS_PYTHON_VERSION=${PY_VERSIONS[$CIRCLE_NODE_INDEX]} | ||
|
||
echo -e "PYTHON = $TRAVIS_PYTHON_VERSION \n============" | ||
git clone git://github.com/astropy/ci-helpers.git > /dev/null | ||
source ci-helpers/travis/setup_conda_$TRAVIS_OS_NAME.sh | ||
export PATH="$HOME/miniconda/bin:$PATH" | ||
source activate test | ||
|
||
# Install ciocheck (not working right now) | ||
#conda install -q ciocheck -c spyder-ide --no-update-deps |
Oops, something went wrong.