-
-
Notifications
You must be signed in to change notification settings - Fork 18.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EuroScipy 2015 pandas sprint #10877
Comments
@jorisvandenbossche awesome! |
Some possible ideas that I would like to see tackled on the sprint (just some ideas, not restrictive, you are free to choose whatever you like!): Ensuring correct examples in the docstrings with doctest
Writing a really basic introduction to pandas (which would also fit in the scipy-lecture-notes: scipy-lectures/scientific-python-lectures#147) Contributing to the documentation
Getting our ASV benchmark suite up to speed
Do you use latex / DataFrame.to_latex? There are quite some, but rather easy bugs to fix!
Familiar with rpy2?
Using the SQL import/export functions?
Some other things:
|
Anyone interested in digging into regressions identified by An explicit regression list is here: http://qwhelan.github.io/pandas_asv/#regressions |
There are some other issues listed here as well: #8323 (from a previous sprint, so some of them can already be solved) |
There will be a pandas sprint at EuroScipy (https://www.euroscipy.org/2015/sprints/) on Sunday the 30th of August.
The sprints will take place at the Seminar Centre of the Hauser Forum (very near to the conference venue) from 10am to 5pm.
This issue will be the landing page for contributors.
pandas is an open source, BSD-licensed library providing high-performance, easy-to-use data structures and data analysis tools for the Python programming language.
See our shiny new Contributing Guidelines & Instructions
Here are various issues that are open and would like your attention:
Please comment on an issue if you are working on it.
Here is a link to the gitter dev chatroom.
How to prepare?
If you want to prepare the sprint, the most important is to set up a development environment: forking the pandas repo, cloning your fork locally, installing all development dependencies in an environment and testing that you can build pandas locally, ...
You can find some information about this in our contributing docs: http://pandas-docs.github.io/pandas-docs-travis/contributing.html
What to work on?
There is no plan to work on something specific, but the idea is that everybody can choose on something they would like to work, and that there is some guidance to do that (but of course, if some of the attendants want to work together on a specific topic, this is certainly possible!).
You can work on whatever you like, but to facilitate finding an appropriate issue, we have the 'Difficulty Novice / Intermediate / Advanced' labels.
I will also put some ideas of issues I would like to see tackled during the sprints here in the coming days.
Please comment on an issue if you are working on it.
The text was updated successfully, but these errors were encountered: