pyrcore 0.0.2

Creates an R core for Python

pyrcore

Python package aiming to create a core of R programming language to optimize time series management.

About	Information
Development Python version
Supported Python distributions
Packaging

Installation

You can install the pyrcore package from PyPI like so:

pip install pyrcore

Current features

Feature	PyPI	TestPyPI	Status
R atomic vectors	✅	✅	Stable
Combination function c()	✅	✅	Stable
R matrixes and matrix() function	✅	✅	Stable
R ts class	❌	❌
R mts class	❌	❌
ts() function	❌	❌

Dependency policy

This project aims to be as package independent as possible.

At the moment, this project depends on numpy for core functionalities and pandas for optional ones.

This project will NOT depend on pandas for core functionalities.

Contribution

This project is part of my Final Degree Project (in spanish: Trabajo de Fin de Grado or TFG), so I won't be accepting contributions to this repository until the project is finished and defended. However, no rule forbids me to learn from other people, so I'll be reading pull requests from forked repositories, but I will code any changes myself. I will not incorporate any changes that I don't understand.

Once the project is defended, contributions will be open. To contribute, fork this repository and clone it locally.

There are two branches:

• PyPI: the main branch, for releases.
• TestPyPI: for pre-releases or development versions.

Pull requests from TestPyPI to PyPI will only be done by the owner when a new release is ready.

Building

To build the project you only have to fork this repository and clone your fork.

Each code file starts with a comment legend. For this to be useful, you will need to install the "Colorful Comments Refreshed" extension for VSCode and change the last tag from todo to ¡.

The final configuration of the extension (in user's settings.json) is the following:

{
    "colorful-comments-refreshed.tags": [
        {
            "tag": "!",
            "color": "#FF2D00",
            "strikethrough": false,
            "backgroundColor": "transparent"
        },
        {
            "tag": "?",
            "color": "#0076FF",
            "strikethrough": false,
            "backgroundColor": "transparent"
        },
        {
            "tag": "//",
            "color": "#474747",
            "strikethrough": true,
            "backgroundColor": "transparent"
        },
        {
            "tag": "^",
            "color": "#EAF622",
            "strikethrough": false,
            "backgroundColor": "transparent"
        },
        {
            "tag": "*",
            "color": "#28FF00",
            "strikethrough": false,
            "backgroundColor": "transparent"
        },
        {
            "tag": "&",
            "color": "#FF06A0",
            "strikethrough": false,
            "backgroundColor": "transparent"
        },
        {
            "tag": "~",
            "color": "#BE00FF",
            "strikethrough": false,
            "backgroundColor": "transparent"
        },
        {
            "tag": "¡",
            "color": "#FF8C00",
            "strikethrough": false,
            "backgroundColor": "transparent"
        }
    ]
}

Branch merging

To merge branches properly with PyPI branch in your cloned repository, you will need to have the .gitattributes file in the PyPI branch and execute the following commands, while in repo directory, in your PowerShell:

git config merge.keepPyPIFiles.name "Keep README.md and setup.cfg from PyPI branch on merge"
git config merge.keepPyPIFiles.driver "bash -c 'cp $(git rev-parse --show-toplevel)/$3 $2'"

This way, README.md and setup.cfg files will not be overwritten in the PyPI branch.