semvec/pypi-packages huggingface dataset:
s-coda 1.0
A library for handling and modifying MIDI files
License: MIT


# S-Coda

[![Python](https://img.shields.io/badge/Python-3.10-blue)](
https://doi.org/10.34726/hss.2023.103585)
[![DOI](https://img.shields.io/badge/DOI-10.34726%2Fhss.2023.103585-blue)](
https://doi.org/10.34726/hss.2023.103585)

S-Coda is a Python library for handling MIDI files.
S-Coda supports a plethora of different MIDI manipulation operations, such as:

- quantisation of notes
- quantisation of notelengths
- splitting sequences into bars
- transposing of sequences
- creating piano-roll visualisations of pieces
- judging the difficulty of pieces

S-Coda was used in our project [PAUL-2](https://github.com/FelixSchoen/PAUL-2) to process MIDI files.
For information about how to use S-Coda we refer to chapter 5 of the [thesis](https://doi.org/10.34726/hss.2023.103585) in which S-Coda was introduced.
xontrib-term-integrations 0.2.0
Support shell integration of terminal programs iTerm2, Kitty...
License: MIT
Requires Python: >=3.8
Keywords: xontrib,xonsh

# Terminal Emulators integration
[Shell integration](https://iterm2.com/documentation-escape-codes.html) for Xonsh.

The following terminal emulators are supported
- [iTerm2](https://iterm2.com/documentation-shell-integration.html)
- [kitty](https://sw.kovidgoyal.net/kitty/shell-integration/)
- [WezTerm](https://wezfurlong.org/wezterm/shell-integration.html) with CWD; Input, Output, and Prompt zones; and User Vars for tracking additional shell state

**Note**: If identifying current terminal fails, `iTerm2` hooks are loaded.

PRs welcome on improving the support to more terminal programs :)


## Installation

To install use pip:

``` bash
xpip install xontrib-term-integrations
# or: xpip install -U git+https://github.com/jnoortheen/xontrib-term-integrations
```


## Usage

``` bash
# this modifies the $PROMPT function. So load it after setting $PROMPT if you have a custom value
xontrib load term_integration
```


## Contributing

Please make sure that you
* Document the purpose of functions and classes.
* When adding a new feature, please mention it in the `README.md`. Use screenshots when applicable.
* [Conventional Commit](https://www.conventionalcommits.org/en/v1.0.0/) style should be used
  for commit messages as it is used to generate changelog.
* Please use [pre-commit](https://pre-commit.com/) to run qa checks. Configure it with

```sh
pre-commit install-hooks
```
CoreEngineX 0.0.1
CoreEngineX fetches and displays Python files from a directory and sub-directories in a CLI menu. It executes the files sequentially and offers the option to check their pylint score.
License: MIT
Keywords: Python,Files,Execution,CoreEngineX,CLI,Command Line Interface,Menu,Pylint

# CoreEngineX
CoreEngineX will fetch the python files from the directory/sub-directories. Display those files in the command line interface menu. Execute the files sequentially. The option to check the pylint score of the files is provided and also the option to load the environment variables.

## Installation
```python -m pip install coreenginex```

## Example Usage

### Read input from command line
```python
import sys
from coreenginex import CoreEngineX

if __name__ == "__main__":
    ce = CoreEngineX()
    code_folder = sys.argv[1]
    ce.run_coreenginex(folder_path = code_folder)

```

### Read input from the script
```python
from coreenginex import CoreEngineX

if __name__ == "__main__":
    ce = CoreEngineX()
    code_folder = './test'
    ce.run_coreenginex(folder_path = code_folder)

```

### Load environment variables
```python
from coreenginex import CoreEngineX

if __name__ == "__main__":
    ce = CoreEngineX()
    code_folder = './test'
    ce.run_coreenginex(folder_path = code_folder)
    ce.load_environment_variables(key_value = {"key": "value"})

```