@@ -14,11 +14,11 @@ All contributions, bug reports, bug fixes, documentation improvements,
14
14
enhancements and ideas are welcome.
15
15
16
16
If you are simply looking to start working with the *pandas * codebase, navigate to the
17
- `GitHub "issues" tab <https://github.com/pydata /pandas/issues >`_ and start looking through
17
+ `GitHub "issues" tab <https://github.com/pandas-dev /pandas/issues >`_ and start looking through
18
18
interesting issues. There are a number of issues listed under `Docs
19
- <https://github.com/pydata /pandas/issues?labels=Docs&sort=updated&state=open> `_
19
+ <https://github.com/pandas-dev /pandas/issues?labels=Docs&sort=updated&state=open> `_
20
20
and `Difficulty Novice
21
- <https://github.com/pydata /pandas/issues?q=is%3Aopen+is%3Aissue+label%3A%22Difficulty+Novice%22> `_
21
+ <https://github.com/pandas-dev /pandas/issues?q=is%3Aopen+is%3Aissue+label%3A%22Difficulty+Novice%22> `_
22
22
where you could start out.
23
23
24
24
Or maybe through using *pandas * you have an idea of your own or are looking for something
@@ -27,7 +27,7 @@ about it!
27
27
28
28
Feel free to ask questions on the `mailing list
29
29
<https://groups.google.com/forum/?fromgroups#!forum/pydata> `_ or on `Gitter
30
- <https://gitter.im/pydata /pandas> `_.
30
+ <https://gitter.im/pandas-dev /pandas> `_.
31
31
32
32
Bug reports and enhancement requests
33
33
====================================
@@ -79,7 +79,7 @@ It can very quickly become overwhelming, but sticking to the guidelines below wi
79
79
straightforward and mostly trouble free. As always, if you are having difficulties please
80
80
feel free to ask for help.
81
81
82
- The code is hosted on `GitHub <https://www.github.com/pydata /pandas >`_. To
82
+ The code is hosted on `GitHub <https://www.github.com/pandas-dev /pandas >`_. To
83
83
contribute you will need to sign up for a `free GitHub account
84
84
<https://github.com/signup/free> `_. We use `Git <http://git-scm.com/ >`_ for
85
85
version control to allow many people to work together on the project.
@@ -103,12 +103,12 @@ Forking
103
103
-------
104
104
105
105
You will need your own fork to work on the code. Go to the `pandas project
106
- page <https://github.com/pydata /pandas> `_ and hit the ``Fork `` button. You will
106
+ page <https://github.com/pandas-dev /pandas> `_ and hit the ``Fork `` button. You will
107
107
want to clone your fork to your machine::
108
108
109
109
git clone git@github.com:your-user-name/pandas.git pandas-yourname
110
110
cd pandas-yourname
111
- git remote add upstream git://github.com/pydata /pandas.git
111
+ git remote add upstream git://github.com/pandas-dev /pandas.git
112
112
113
113
This creates the directory `pandas-yourname ` and connects your repository to
114
114
the upstream (main project) *pandas * repository.
@@ -467,7 +467,7 @@ and make these changes with::
467
467
pep8radius master --diff --in-place
468
468
469
469
Additional standards are outlined on the `code style wiki
470
- page <https://github.com/pydata /pandas/wiki/Code-Style-and-Conventions> `_.
470
+ page <https://github.com/pandas-dev /pandas/wiki/Code-Style-and-Conventions> `_.
471
471
472
472
Please try to maintain backward compatibility. *pandas * has lots of users with lots of
473
473
existing code, so don't break it if at all possible. If you think breakage is required,
@@ -501,7 +501,7 @@ All tests should go into the ``tests`` subdirectory of the specific package.
501
501
This folder contains many current examples of tests, and we suggest looking to these for
502
502
inspiration. If your test requires working with files or
503
503
network connectivity, there is more information on the `testing page
504
- <https://github.com/pydata /pandas/wiki/Testing> `_ of the wiki.
504
+ <https://github.com/pandas-dev /pandas/wiki/Testing> `_ of the wiki.
505
505
506
506
The ``pandas.util.testing `` module has many special ``assert `` functions that
507
507
make it easier to make statements about whether Series or DataFrame objects are
@@ -639,7 +639,7 @@ on Travis-CI. The first step is to create a `service account
639
639
Integration tests for ``pandas.io.gbq `` are skipped in pull requests because
640
640
the credentials that are required for running Google BigQuery integration
641
641
tests are `encrypted <https://docs.travis-ci.com/user/encrypting-files/ >`__
642
- on Travis-CI and are only accessible from the pydata /pandas repository. The
642
+ on Travis-CI and are only accessible from the pandas-dev /pandas repository. The
643
643
credentials won't be available on forks of pandas. Here are the steps to run
644
644
gbq integration tests on a forked repository:
645
645
@@ -688,7 +688,7 @@ performance regressions.
688
688
689
689
You can run specific benchmarks using the ``-r `` flag, which takes a regular expression.
690
690
691
- See the `performance testing wiki <https://github.com/pydata /pandas/wiki/Performance-Testing >`_ for information
691
+ See the `performance testing wiki <https://github.com/pandas-dev /pandas/wiki/Performance-Testing >`_ for information
692
692
on how to write a benchmark.
693
693
694
694
Documenting your code
@@ -712,8 +712,8 @@ directive is used. The sphinx syntax for that is:
712
712
713
713
This will put the text *New in version 0.17.0 * wherever you put the sphinx
714
714
directive. This should also be put in the docstring when adding a new function
715
- or method (`example <https://github.com/pydata /pandas/blob/v0.16.2/pandas/core/generic.py#L1959 >`__)
716
- or a new keyword argument (`example <https://github.com/pydata /pandas/blob/v0.16.2/pandas/core/frame.py#L1171 >`__).
715
+ or method (`example <https://github.com/pandas-dev /pandas/blob/v0.16.2/pandas/core/generic.py#L1959 >`__)
716
+ or a new keyword argument (`example <https://github.com/pandas-dev /pandas/blob/v0.16.2/pandas/core/frame.py#L1171 >`__).
717
717
718
718
Contributing your changes to *pandas *
719
719
=====================================
@@ -806,8 +806,8 @@ like::
806
806
807
807
origin git@github.com:yourname/pandas.git (fetch)
808
808
origin git@github.com:yourname/pandas.git (push)
809
- upstream git://github.com/pydata /pandas.git (fetch)
810
- upstream git://github.com/pydata /pandas.git (push)
809
+ upstream git://github.com/pandas-dev /pandas.git (fetch)
810
+ upstream git://github.com/pandas-dev /pandas.git (push)
811
811
812
812
Now your code is on GitHub, but it is not yet a part of the *pandas * project. For that to
813
813
happen, a pull request needs to be submitted on GitHub.
0 commit comments