pax_global_header 0000666 0000000 0000000 00000000064 14571337522 0014523 g ustar 00root root 0000000 0000000 52 comment=f516cdff15434f9d0c1e348edab2c68285fcc5fb rdata-0.11.2/ 0000775 0000000 0000000 00000000000 14571337522 0012677 5 ustar 00root root 0000000 0000000 rdata-0.11.2/.all-contributorsrc 0000664 0000000 0000000 00000006063 14571337522 0016535 0 ustar 00root root 0000000 0000000 { "projectName": "rdata", "projectOwner": "VNMabus", "repoType": "github", "repoHost": "https://github.com", "files": [ "CONTRIBUTORS.md" ], "imageSize": 100, "commit": false, "commitConvention": "none", "contributors": [ { "login": "vnmabus", "name": "Carlos Ramos Carreño", "avatar_url": "https://avatars.githubusercontent.com/u/2364173?v=4", "profile": "https://github.com/vnmabus", "contributions": [ "code", "data", "doc", "example", "ideas", "infra", "maintenance", "projectManagement", "question", "review", "test", "tutorial" ] }, { "login": "", "name": "CSC - IT Center for Science Ltd", "avatar_url": "https://avatars.githubusercontent.com/u/5947494?v=4", "profile": "https://www.csc.fi", "contributions": [ { "type": "code", "url": "https://github.com/vnmabus/rdata/commits?author=trossi" } ] }, { "login": "trossi", "name": "Tuomas Rossi", "avatar_url": "https://avatars.githubusercontent.com/u/34502776?v=4", "profile": "https://github.com/trossi", "contributions": [ "code", "ideas", "bug" ] }, { "login": "VolodyaCO", "name": "Vladimir Vargas-Calderón", "avatar_url": "https://avatars.githubusercontent.com/u/31494271?v=4", "profile": "https://www.researchgate.net/profile/Vladimir_Vargas-Calderon", "contributions": [ "bug" ] }, { "login": "Jorgelindo238", "name": "Jorgelindo", "avatar_url": "https://avatars.githubusercontent.com/u/79350063?v=4", "profile": "https://jorgelindodaveiga.myportfolio.com/", "contributions": [ "bug" ] }, { "login": "zoj613", "name": "zoj613", "avatar_url": "https://avatars.githubusercontent.com/u/44142765?v=4", "profile": "https://github.com/zoj613", "contributions": [ "bug" ] }, { "login": "schlegelp", "name": "Philipp Schlegel", "avatar_url": "https://avatars.githubusercontent.com/u/7161148?v=4", "profile": "https://github.com/schlegelp", "contributions": [ "bug" ] }, { "login": "deeenes", "name": "deeenes", "avatar_url": "https://avatars.githubusercontent.com/u/2679889?v=4", "profile": "https://denes.omnipathdb.org/", "contributions": [ "bug" ] }, { "login": "soheila-sahami", "name": "Soheila", "avatar_url": "https://avatars.githubusercontent.com/u/9429831?v=4", "profile": "https://github.com/soheila-sahami", "contributions": [ "ideas" ] }, { "login": "userLUX", "name": "userLUX", "avatar_url": "https://avatars.githubusercontent.com/u/107994632?v=4", "profile": "https://github.com/userLUX", "contributions": [ "bug" ] } ], "contributorsPerLine": 7, "linkToUsage": true } rdata-0.11.2/.gitattributes 0000664 0000000 0000000 00000000235 14571337522 0015572 0 ustar 00root root 0000000 0000000 # Mark rda and rds files as binary. # Otherwise git might change the line endings of # ascii-formatted files, which breaks the tests *.rda -text *.rds -text rdata-0.11.2/.github/ 0000775 0000000 0000000 00000000000 14571337522 0014237 5 ustar 00root root 0000000 0000000 rdata-0.11.2/.github/ISSUE_TEMPLATE/ 0000775 0000000 0000000 00000000000 14571337522 0016422 5 ustar 00root root 0000000 0000000 rdata-0.11.2/.github/ISSUE_TEMPLATE/bug_report.yml 0000664 0000000 0000000 00000007161 14571337522 0021322 0 ustar 00root root 0000000 0000000 name: Bug report description: Create a report to help us reproduce and fix a bug labels: [bug] body: - type: markdown attributes: value: > #### Please check that the bug has not been previously notified before submitting, by searching through the [issues list](https://github.com/vnmabus/rdata/issues). - type: textarea attributes: label: Bug description summary description: > Please describe the bug in a brief paragraph(s). Be clear and concise. validations: required: true - type: textarea attributes: label: Code to reproduce the bug description: | Please add a minimal code example that can reproduce the error. If the bug does not require more code than loading a data file you can leave this empty. This will be automatically converted to a Python block. placeholder: | import rdata parsed = rdata.parser.parse_file("data.rda") converted = rdata.conversion.convert(parsed) converted render: Python - type: textarea attributes: label: Data file(s) description: > If the bug was caused by loading a particular data file, please attach it or paste a link to it here. - type: textarea attributes: label: Expected result description: > Paste or describe the result that you expected here. validations: required: true - type: textarea attributes: label: Actual result description: > Paste or describe the result that you obtained here. If the code raises an error, you can past it in the next field. validations: required: true - type: textarea attributes: label: Traceback (if an exception is raised) description: | If an exception is raised, copy and paste the traceback here. placeholder: | FileNotFoundError Traceback (most recent call last) Cell In[5], line 3 1 import rdata ----> 3 parsed = rdata.parser.parse_file("data.rda") 4 converted = rdata.conversion.convert(parsed) 5 converted File .../rdata/parser/_parser.py:1139, in parse_file(file_or_path, expand_altrep, altrep_constructor_dict, extension) 1137 if extension is None: 1138 extension = getattr(path, "suffix", None) -> 1139 data = path.read_bytes() 1141 return parse_data( 1142 data, 1143 expand_altrep=expand_altrep, 1144 altrep_constructor_dict=altrep_constructor_dict, 1145 extension=extension, 1146 ) File .../pathlib.py:1050, in Path.read_bytes(self) 1046 def read_bytes(self): 1047 """ 1048 Open the file in bytes mode, read it, and close the file. 1049 """ -> 1050 with self.open(mode='rb') as f: 1051 return f.read() File .../pathlib.py:1044, in Path.open(self, mode, buffering, encoding, errors, newline) 1042 if "b" not in mode: 1043 encoding = io.text_encoding(encoding) -> 1044 return io.open(self, mode, buffering, encoding, errors, newline) FileNotFoundError: [Errno 2] No such file or directory: 'data.rda' render: Python - type: textarea attributes: label: Software versions description: > Include the version of the library used (obtained with `rdata.__version__`). If relevant, you can include here the OS version and versions of related software. placeholder: | rdata version: 0.10.0 OS: Windows 10 validations: required: true - type: textarea attributes: label: Additional context description: > Add any other context about the problem here. rdata-0.11.2/.github/ISSUE_TEMPLATE/feature_request.yml 0000664 0000000 0000000 00000002001 14571337522 0022341 0 ustar 00root root 0000000 0000000 name: Feature request description: Suggest an idea for this project labels: [enhancement] body: - type: markdown attributes: value: > #### Please check that this idea has not been proposed previously, by searching through the [issues list](https://github.com/vnmabus/rdata/issues). - type: textarea attributes: label: Motivation description: > A clear and concise description of what the problem is. Ex. I am always frustrated when [...] validations: required: true - type: textarea attributes: label: Desired functionality description: > A clear and concise description of what you want to happen. validations: required: true - type: textarea attributes: label: Alternatives description: > A clear and concise description of any alternative solutions or features you have considered. validations: required: false - type: textarea attributes: label: Additional context description: > Add any other context about the problem here. rdata-0.11.2/.github/PULL_REQUEST_TEMPLATE.md 0000664 0000000 0000000 00000002230 14571337522 0020035 0 ustar 00root root 0000000 0000000 ## References to issues or other PRs ## Describe the proposed changes ## Additional information ## Checklist before requesting a review - [ ] I have performed a self-review of my code - [ ] The code conforms to the style used in this package (checked with [Ruff](https://docs.astral.sh/ruff/)) - [ ] The code is fully documented and typed (type-checked with [Mypy](https://mypy-lang.org/)) - [ ] I have added thorough tests for the new/changed functionality rdata-0.11.2/.github/workflows/ 0000775 0000000 0000000 00000000000 14571337522 0016274 5 ustar 00root root 0000000 0000000 rdata-0.11.2/.github/workflows/main.yml 0000664 0000000 0000000 00000001544 14571337522 0017747 0 ustar 00root root 0000000 0000000 name: Tests on: push: pull_request: jobs: build: runs-on: ${{ matrix.os }} name: Python ${{ matrix.python-version }} on ${{ matrix.os }} strategy: matrix: os: [ubuntu-latest, macos-latest, windows-latest] python-version: ['3.9', '3.10', '3.11', '3.12'] steps: - uses: actions/checkout@v4 - name: Set up Python ${{ matrix.python-version }} on ${{ matrix.os }} uses: actions/setup-python@v5 with: python-version: ${{ matrix.python-version }} - name: Install dependencies run: | pip3 install pytest-cov || pip3 install --user pytest-cov; - name: Run tests run: | pip3 debug --verbose . pip3 install ".[test]" pytest --cov=rdata/ --cov-report=xml - name: Upload coverage to Codecov uses: codecov/codecov-action@v3 rdata-0.11.2/.github/workflows/mypy.yml 0000664 0000000 0000000 00000001176 14571337522 0020022 0 ustar 00root root 0000000 0000000 name: Mypy on: pull_request: jobs: build: runs-on: ubuntu-latest name: Mypy steps: - uses: actions/checkout@v4 - name: Set up Python uses: actions/setup-python@v5 with: python-version: "3.11" - name: Install dependencies run: | pip3 install ".[test,typing]" mypy; rm -rf build; - uses: tsuyoshicho/action-mypy@v4 with: github_token: ${{ secrets.github_token }} reporter: github-pr-review install_types: false # The action will output fail if there are mypy errors level: error filter_mode: nofilter rdata-0.11.2/.github/workflows/python-publish.yml 0000664 0000000 0000000 00000002103 14571337522 0022000 0 ustar 00root root 0000000 0000000 # This workflow will upload a Python Package using Twine when a release is created # For more information see: https://help.github.com/en/actions/language-and-framework-guides/using-python-with-github-actions#publishing-to-package-registries # This workflow uses actions that are not certified by GitHub. # They are provided by a third-party and are governed by # separate terms of service, privacy policy, and support # documentation. name: Upload Python Package on: release: types: [published] permissions: contents: read jobs: deploy: runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 - name: Set up Python uses: actions/setup-python@v5 with: python-version: '3.x' - name: Install dependencies run: | python -m pip install --upgrade pip pip install build - name: Build package run: python -m build - name: Publish package uses: pypa/gh-action-pypi-publish@27b31702a0e7fc50959f5ad993c78deac1bdfc29 with: user: __token__ password: ${{ secrets.PYPI_API_TOKEN }} rdata-0.11.2/.github/workflows/ruff.yml 0000664 0000000 0000000 00000000316 14571337522 0017761 0 ustar 00root root 0000000 0000000 name: Ruff on: [push] jobs: ruff: runs-on: ubuntu-latest steps: - uses: actions/checkout@v3 - uses: chartboost/ruff-action@v1 with: args: check --output-format github rdata-0.11.2/.gitignore 0000664 0000000 0000000 00000002311 14571337522 0014664 0 ustar 00root root 0000000 0000000 # Byte-compiled / optimized / DLL files __pycache__/ *.py[cod] *$py.class # C extensions *.so # Distribution / packaging .Python build/ develop-eggs/ dist/ downloads/ eggs/ .eggs/ lib/ lib64/ parts/ sdist/ var/ wheels/ *.egg-info/ .installed.cfg *.egg MANIFEST # PyInstaller # Usually these files are written by a python script from a template # before PyInstaller builds the exe, so as to inject date/other infos into it. *.manifest *.spec # Installer logs pip-log.txt pip-delete-this-directory.txt # Unit test / coverage reports htmlcov/ .tox/ .coverage .coverage.* .cache nosetests.xml coverage.xml *.cover .hypothesis/ .pytest_cache/ # Translations *.mo *.pot # Django stuff: *.log local_settings.py db.sqlite3 # Flask stuff: instance/ .webassets-cache # Scrapy stuff: .scrapy # Sphinx documentation docs/_build/ # PyBuilder target/ # Jupyter Notebook .ipynb_checkpoints # pyenv .python-version # celery beat schedule file celerybeat-schedule # SageMath parsed files *.sage.py # Environments .env .venv env/ venv/ ENV/ env.bak/ venv.bak/ # Spyder project settings .spyderproject .spyproject # Rope project settings .ropeproject # mkdocs documentation /site # mypy .mypy_cache/ # ruff /.ruff_cache/ rdata-0.11.2/CITATION.cff 0000664 0000000 0000000 00000001376 14571337522 0014600 0 ustar 00root root 0000000 0000000 cff-version: 1.2.0 message: "If you use this software, please cite it as below." authors: - family-names: "Ramos-Carreño" given-names: "Carlos" orcid: "https://orcid.org/0000-0003-2566-7058" affiliation: "Universidad Autónoma de Madrid" email: vnmabus@gmail.com title: "rdata: Read R datasets from Python" date-released: 2022-03-24 doi: 10.5281/zenodo.6382237 url: "https://github.com/vnmabus/rdata" license: MIT keywords: - rdata - Python - R - parser - conversion identifiers: - description: "This is the collection of archived snapshots of all versions of rdata" type: doi value: 10.5281/zenodo.6382237 - description: "This is the archived snapshot of version 0.7 of rdata" type: doi value: 10.5281/zenodo.6382238 rdata-0.11.2/CODE_OF_CONDUCT.md 0000664 0000000 0000000 00000012153 14571337522 0015500 0 ustar 00root root 0000000 0000000 # Contributor Covenant Code of Conduct ## Our Pledge We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation. We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community. ## Our Standards Examples of behavior that contributes to a positive environment for our community include: * Demonstrating empathy and kindness toward other people * Being respectful of differing opinions, viewpoints, and experiences * Giving and gracefully accepting constructive feedback * Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience * Focusing on what is best not just for us as individuals, but for the overall community Examples of unacceptable behavior include: * The use of sexualized language or imagery, and sexual attention or advances of any kind * Trolling, insulting or derogatory comments, and personal or political attacks * Public or private harassment * Publishing others' private information, such as a physical or email address, without their explicit permission * Other conduct which could reasonably be considered inappropriate in a professional setting ## Enforcement Responsibilities Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful. Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate. ## Scope This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. ## Enforcement Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at carlosramosca@hotmail.com. All complaints will be reviewed and investigated promptly and fairly. All community leaders are obligated to respect the privacy and security of the reporter of any incident. ## Enforcement Guidelines Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct: ### 1. Correction **Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community. **Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested. ### 2. Warning **Community Impact**: A violation through a single incident or series of actions. **Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban. ### 3. Temporary Ban **Community Impact**: A serious violation of community standards, including sustained inappropriate behavior. **Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban. ### 4. Permanent Ban **Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals. **Consequence**: A permanent ban from any sort of public interaction within the community. ## Attribution This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.0, available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html. Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity). [homepage]: https://www.contributor-covenant.org For answers to common questions about this code of conduct, see the FAQ at https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations. rdata-0.11.2/CONTRIBUTING.md 0000664 0000000 0000000 00000003116 14571337522 0015131 0 ustar 00root root 0000000 0000000 # How to contribute Thank you for considering contributing to rdata! You can contribute to rdata in several ways. ## Opening issues Open a new issue if you find some bug or you want to propose a new feature. Please first check that nobody has asked that already! Make sure that your proposal is clearly written, preferably in English. In case you are reporting a bug, please include all relevant information, such as the software version and machine information. ## Discussing the project You can open a discussion for any topic related with this package. Do you have doubts about how to use the package? Open a discussion! Do you want to show related projects, recent research or some use case for this software? Open a discussion! You are also encouraged to answer the discussions of other users and participate actively in the discussions forum. ## Improving the documentation Do you feel that the documentation could be more clear? Did you found a typo? You can easily edit the documentation and make a pull request clicking the "Edit this page" link in the documentation. Advanced users can also propose the addition of new pages and examples. In case you want to do that, please open an issue to discuss that first. ## Contributing software You can improve this package by adding new functionality, solving pending bugs or implementing accepted feature requests. Please discuss that first to ensure that it will be accepted and to assign that to you and prevent duplicated efforts. In any case, make sure that you own the rights to the software and are ok with releasing it under a MIT license. rdata-0.11.2/CONTRIBUTORS.md 0000664 0000000 0000000 00000012453 14571337522 0015163 0 ustar 00root root 0000000 0000000 ## Contributors ✨ Thanks goes to these wonderful people ([emoji key](https://allcontributors.org/docs/en/emoji-key)):