pydata is a python package that allows you to handle several scientific file formats.

• Dependencies and installation
• Testing
• Authors and contributors
• How to contribute
• License

pydata requires only numpy, scipy, matplotlib. Other packages may be required in order to manipulate specific files. We provide a simple table to summarize the needed packages for supported files:

The official distribution is on GitHub, and you can clone the repository using

> git clone https://github.com/mathLab/pydata

To install the package just type:

> python setup.py install

To uninstall the package you have to rerun the installation and record the installed files in order to remove them:

> python setup.py install --record installed_files.txt
> cat installed_files.txt | xargs rm -rf

We are using Travis CI for continuous intergration testing. You can check out the current status here.

To run tests locally (the package nose is required):

> python test.py

pydata is currently developed and mantained at SISSA mathLab by

• Marco Tezzele
• Nicola Demo

under the supervision of Prof. Gianluigi Rozza.

Contact us by email for further information or questions about pydata, or suggest pull requests. Contributions improving either the code or the documentation are welcome!

We'd love to accept your patches and contributions to this project. There are just a few small guidelines you need to follow.

1. It's generally best to start by opening a new issue describing the bug or feature you're intending to fix. Even if you think it's relatively minor, it's helpful to know what people are working on. Mention in the initial issue that you are planning to work on that bug or feature so that it can be assigned to you.

2. Follow the normal process of forking the project, and setup a new branch to work in. It's important that each group of changes be done in separate branches in order to ensure that a pull request only includes the commits related to that bug or feature.

3. To ensure properly formatted code, please make sure to use 4 spaces to indent the code. The easy way is to run on your bash the provided script: ./code_formatter.sh. You should also run pylint over your code. It's not strictly necessary that your code be completely "lint-free", but this will help you find common style issues.

4. Any significant changes should almost always be accompanied by tests. The project already has good test coverage, so look at some of the existing tests if you're unsure how to go about it. We're using coveralls that is an invaluable tools for seeing which parts of your code aren't being exercised by your tests.

5. Do your best to have well-formed commit messages for each change. This provides consistency throughout the project, and ensures that commit messages are able to be formatted properly by various git tools.

6. Finally, push the commits to your fork and submit a pull request. Please, remember to rebase properly in order to maintain a clean, linear git history.

See the LICENSE file for license rights and limitations (MIT).