Skip to content

Commit 2ccbe5b

Browse files
author
harisbal
committed
Rebase
1 parent 61a243b commit 2ccbe5b

File tree

1,413 files changed

+185190
-142306
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

1,413 files changed

+185190
-142306
lines changed

.github/CODE_OF_CONDUCT.md

+63
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,63 @@
1+
# Contributor Code of Conduct
2+
3+
As contributors and maintainers of this project, and in the interest of
4+
fostering an open and welcoming community, we pledge to respect all people who
5+
contribute through reporting issues, posting feature requests, updating
6+
documentation, submitting pull requests or patches, and other activities.
7+
8+
We are committed to making participation in this project a harassment-free
9+
experience for everyone, regardless of level of experience, gender, gender
10+
identity and expression, sexual orientation, disability, personal appearance,
11+
body size, race, ethnicity, age, religion, or nationality.
12+
13+
Examples of unacceptable behavior by participants include:
14+
15+
* The use of sexualized language or imagery
16+
* Personal attacks
17+
* Trolling or insulting/derogatory comments
18+
* Public or private harassment
19+
* Publishing other's private information, such as physical or electronic
20+
addresses, without explicit permission
21+
* Other unethical or unprofessional conduct
22+
23+
Project maintainers have the right and responsibility to remove, edit, or
24+
reject comments, commits, code, wiki edits, issues, and other contributions
25+
that are not aligned to this Code of Conduct, or to ban temporarily or
26+
permanently any contributor for other behaviors that they deem inappropriate,
27+
threatening, offensive, or harmful.
28+
29+
By adopting this Code of Conduct, project maintainers commit themselves to
30+
fairly and consistently applying these principles to every aspect of managing
31+
this project. Project maintainers who do not follow or enforce the Code of
32+
Conduct may be permanently removed from the project team.
33+
34+
This Code of Conduct applies both within project spaces and in public spaces
35+
when an individual is representing the project or its community.
36+
37+
A working group of community members is committed to promptly addressing any
38+
reported issues. The working group is made up of pandas contributors and users.
39+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
40+
reported by contacting the working group by e-mail ([email protected]).
41+
Messages sent to this e-mail address will not be publicly visible but only to
42+
the working group members. The working group currently includes
43+
44+
- Safia Abdalla
45+
- Tom Augspurger
46+
- Joris Van den Bossche
47+
- Camille Scott
48+
- Nathaniel Smith
49+
50+
All complaints will be reviewed and investigated and will result in a response
51+
that is deemed necessary and appropriate to the circumstances. Maintainers are
52+
obligated to maintain confidentiality with regard to the reporter of an
53+
incident.
54+
55+
This Code of Conduct is adapted from the [Contributor Covenant][homepage],
56+
version 1.3.0, available at
57+
[http://contributor-covenant.org/version/1/3/0/][version],
58+
and the [Swift Code of Conduct][swift].
59+
60+
[homepage]: http://contributor-covenant.org
61+
[version]: http://contributor-covenant.org/version/1/3/0/
62+
[swift]: https://swift.org/community/#code-of-conduct
63+

.github/CONTRIBUTING.md

+14-505
Large diffs are not rendered by default.

.github/ISSUE_TEMPLATE.md

+12-1
Original file line numberDiff line numberDiff line change
@@ -8,11 +8,22 @@
88

99
[this should explain **why** the current behaviour is a problem and why the expected output is a better solution.]
1010

11+
**Note**: We receive a lot of issues on our GitHub tracker, so it is very possible that your issue has been posted before. Please check first before submitting so that we do not have to handle and close duplicates!
12+
13+
**Note**: Many problems can be resolved by simply upgrading `pandas` to the latest version. Before submitting, please check if that solution works for you. If possible, you may want to check if `master` addresses this issue, but that is not necessary.
14+
15+
For documentation-related issues, you can check the latest versions of the docs on `master` here:
16+
17+
https://pandas-docs.github.io/pandas-docs-travis/
18+
19+
If the issue has not been resolved there, go ahead and file it in the issue tracker.
20+
1121
#### Expected Output
1222

1323
#### Output of ``pd.show_versions()``
1424

1525
<details>
16-
# Paste the output here pd.show_versions() here
26+
27+
[paste the output of ``pd.show_versions()`` here below this line]
1728

1829
</details>

.github/PULL_REQUEST_TEMPLATE.md

+28-4
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,28 @@
1-
- [ ] closes #xxxx
2-
- [ ] tests added / passed
3-
- [ ] passes ``git diff upstream/master | flake8 --diff``
4-
- [ ] whatsnew entry
1+
Checklist for the pandas documentation sprint (ignore this if you are doing
2+
an unrelated PR):
3+
4+
- [ ] PR title is "DOC: update the <your-function-or-method> docstring"
5+
- [ ] The validation script passes: `scripts/validate_docstrings.py <your-function-or-method>`
6+
- [ ] The PEP8 style check passes: `git diff upstream/master -u -- "*.py" | flake8 --diff`
7+
- [ ] The html version looks good: `python doc/make.py --single <your-function-or-method>`
8+
- [ ] It has been proofread on language by another sprint participant
9+
10+
Please include the output of the validation script below between the "```" ticks:
11+
12+
```
13+
# paste output of "scripts/validate_docstrings.py <your-function-or-method>" here
14+
# between the "```" (remove this comment, but keep the "```")
15+
16+
```
17+
18+
If the validation script still gives errors, but you think there is a good reason
19+
to deviate in this case (and there are certainly such cases), please state this
20+
explicitly.
21+
22+
23+
Checklist for other PRs (remove this part if you are doing a PR for the pandas documentation sprint):
24+
25+
- [ ] closes #xxxx
26+
- [ ] tests added / passed
27+
- [ ] passes `git diff upstream/master -u -- "*.py" | flake8 --diff`
28+
- [ ] whatsnew entry

.gitignore

+8-2
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,7 @@
77
*$
88
*.bak
99
*flymake*
10+
*.iml
1011
*.kdev4
1112
*.log
1213
*.swp
@@ -20,6 +21,7 @@
2021
.ipynb_checkpoints
2122
.tags
2223
.cache/
24+
.vscode/
2325

2426
# Compiled source #
2527
###################
@@ -86,8 +88,9 @@ scikits
8688
*.c
8789
*.cpp
8890

89-
# Performance Testing #
90-
#######################
91+
# Unit / Performance Testing #
92+
##############################
93+
.pytest_cache/
9194
asv_bench/env/
9295
asv_bench/html/
9396
asv_bench/results/
@@ -103,3 +106,6 @@ doc/source/index.rst
103106
doc/build/html/index.html
104107
# Windows specific leftover:
105108
doc/tmp.sv
109+
doc/source/styled.xlsx
110+
doc/source/templates/
111+
env/

.pep8speaks.yml

+12
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
# File : .pep8speaks.yml
2+
3+
scanner:
4+
diff_only: True # If True, errors caused by only the patch are shown
5+
6+
pycodestyle:
7+
max-line-length: 79
8+
ignore: # Errors and warnings to ignore
9+
- E402, # module level import not at top of file
10+
- E731, # do not assign a lambda expression, use a def
11+
- E741, # do not use variables named 'l', 'O', or 'I'
12+
- W503 # line break before binary operator

0 commit comments

Comments
 (0)