semvec/pypi-packages huggingface dataset:
relic-tool 1.0.1
A library which allows the reading/writing of Relic's proprietary file formats; SGA files (.sga), Relic Chunky files, and UCS language files (.ucs).

# Relic Tool
[![PyPI](https://img.shields.io/pypi/v/relic-tool)](https://pypi.org/project/Relic-Tool/)
[![PyPI - Python Version](https://img.shields.io/pypi/pyversions/relic-tool)](https://www.python.org/downloads/)
[![PyPI - License](https://img.shields.io/pypi/l/relic-tool)](https://github.com/MAK-Relic-Tool/Relic-Tool/blob/main/LICENSE.txt)
[![Checked with mypy](http://www.mypy-lang.org/static/mypy_badge.svg)](http://mypy-lang.org/)
[![Build Check](https://github.com/MAK-Relic-Tool/Relic-Tool/actions/workflows/build-check.yml/badge.svg)](https://github.com/MAK-Relic-Tool/Relic-Tool/actions/workflows/build-check.yml)
#### Disclaimer
Not affiliated with Sega, Relic Entertainment, or THQ.

#### Description
A library which allows the reading/writing of Relic's proprietary file formats; SGA files (.sga), Relic Chunky files, and UCS language files (.ucs).

## Installation (Pip)
### Installing from PyPI (Recommended)
```
pip install relic-tool
```
### Installing from GitHub
For more information, see [pip VCS support](https://pip.pypa.io/en/stable/topics/vcs-support/#git)
```
pip install git+https://github.com/MAK-Relic-Tool/Relic-Tool
```
relic-tool-chunky 1.0.0
A collection of libraries which allow reading/writing of Relic Chunky files.
Requires Python: >=3.9

# Relic Tool - Chunky
[![PyPI](https://img.shields.io/pypi/v/relic-tool-chunky)](https://pypi.org/project/Relic-Tool-Chunky/)
[![PyPI - Python Version](https://img.shields.io/pypi/pyversions/relic-tool-chunky)](https://www.python.org/downloads/)
[![PyPI - License](https://img.shields.io/pypi/l/relic-tool-chunky)](https://github.com/MAK-Relic-Tool/Relic-Tool-Chunky/blob/main/LICENSE.txt)
[![linting: pylint](https://img.shields.io/badge/linting-pylint-yellowgreen)](https://github.com/PyCQA/pylint)
[![Checked with mypy](http://www.mypy-lang.org/static/mypy_badge.svg)](http://mypy-lang.org/)
[![Code style: black](https://img.shields.io/badge/code%20style-black-000000.svg)](https://github.com/psf/black)
[![Builds](https://github.com/MAK-Relic-Tool/Relic-Tool-Chunky/actions/workflows/build-check.yml/badge.svg)](https://github.com/MAK-Relic-Tool/Relic-Tool-Chunky/actions/workflows/build-check.yml)
#### Disclaimer
Not affiliated with Sega, Relic Entertainment, or THQ.

#### Description
A library for reading/writing Relics' Chunky file format.

## Installation (Pip)
### Installing from PyPI (Recommended)
```
pip install relic-tool-chunky
```
### Installing from GitHub
For more information, see [pip VCS support](https://pip.pypa.io/en/stable/topics/vcs-support/#git)
```
pip install git+https://github.com/MAK-Relic-Tool/Relic-Tool-Chunky
```
Hot3nCoder 1.0.5
Encode your cpp file with whatever you want
Keywords: cpp,encode,emoji,funny

# Hot3nCoder
A tool to encode your .cpp file with whatever you want

## How to use
- open your terminal
- type "pip install Hot3nCoder" in your terminal
- type "Hot3nCoder -i \<YourCppFilePath\> -s \<Symbols you want\n>
  - notice that symbols should split with " "
- the Encoded file will generate in the same directory of your cpp file

### Example
Hot3nCoder -i "C:/ex.cpp" -s "🥵 😉 Hello"

#### ex.cpp  
> #include<bits/stdc++.h>  
> using namespace std;  
>  
> int main(){  
> 　　string str = "test";  
> 　　cout<<str<<'\n';  
> 　　for(int i=0;i<10;i++){  
> 　　　　cout<<i<<endl;  
> 　　}  
>  
> 　　return 0;  
> }

#### Hot3nCoder.cpp
> #include<bits/stdc++.h>  
> #define AAAHelloHello {    
> #define AA😉HelloHello namespace  
> #define AA🥵Hello ;  
> #define A😉AHelloHelloHello string　　
> #define A😉😉HelloHello endl  
> #define A😉🥵Hello main  
> #define A🥵AHelloHello ++   
> #define A🥵😉Hello 0   
> #define A🥵🥵HelloHello int   
> #define 😉AAHello i   
> #define 😉A😉 '\n'   
> #define 😉A🥵HelloHelloHello )  
> #define 😉😉AHelloHelloHello cout   
> #define 😉😉😉Hello using   
> #define 😉😉🥵HelloHello <  
> #define 😉🥵AHelloHello str   
> #define 😉🥵😉Hello return   
> #define 😉🥵🥵Hello "test"  
> #define 🥵AAHelloHello 10   
> #define 🥵A😉HelloHello std   
> #define 🥵A🥵 for   
> #define 🥵😉AHelloHello (  
> #define 🥵😉😉 =   
> #define 🥵😉🥵HelloHelloHello }   
> #define 🥵🥵AHello <<  
> 😉😉😉Hello AA😉HelloHello 🥵A😉HelloHello AA🥵Hello    
>     
>  A🥵🥵HelloHello A😉🥵Hello 🥵😉AHelloHello  😉A🥵HelloHelloHello  AAAHelloHello    
>      A😉AHelloHelloHello 😉🥵AHelloHello  🥵😉😉  😉🥵🥵Hello AA🥵Hello    
>      😉😉AHelloHelloHello 🥵🥵AHello 😉🥵AHelloHello 🥵🥵AHello 😉A😉 AA🥵Hello    
>      🥵A🥵 🥵😉AHelloHello A🥵🥵HelloHello 😉AAHello 🥵😉😉 A🥵😉Hello AA🥵Hello 😉AAHello 😉😉🥵HelloHello 🥵AAHelloHello AA🥵Hello 😉AAHello A🥵AHelloHello  😉A🥵HelloHelloHello  AAAHelloHello    
>          😉😉AHelloHelloHello 🥵🥵AHello 😉AAHello 🥵🥵AHello A😉😉HelloHello AA🥵Hello    
>       🥵😉🥵HelloHelloHello    
>     
>      😉🥵😉Hello A🥵😉Hello AA🥵Hello    
>   🥵😉🥵HelloHelloHello    
>  
>  /*Created by Jasoff*/  

#  Issue
- Some terminal doesn't support emoji encoding, using one that would show emoji will avoid an error.
prebuilt-binaries 0.5.0
A setuptools command for packaging pre-built binary python extension modules.
Keywords: packaging,extension,setuptools

prebuilt_binaries
=================
A setuptools command for packaging pre-built binary python extension modules.

If you are already using cmake as your build tool, having to then build your library 
with setuptools in order to package it can be annoying.  
 
prebuild_binaries allows you to pass an already built extension module (.pyd file) to setuptools 
for inclusion in a wheel.

Note that it is your responsibility to do this with the same python version as the file was created 
with - however this is pretty easy to get right when it's part of the same build chain. 

API
---

**class PrebuiltExtension** *(input_filename, package=None)*
    `input_filename` is the full path to the pre-built extension module (.pyd file)
    The stem of `input_filename` is used for the name of the extension module.

    If `package` is passed then the name of the extension module will be `<package>.<name>`

**class prebuilt_binary**
    setuptools command class that takes PrebuiltExtension instances as parameters and copies the input file to the correct location.  It is a replacement for the setuptools `build_ext` command.

Minimal setup.py example
------------------------
::

    import os
    from setuptools import setup
    from prebuilt_binaries import prebuilt_binary, PrebuiltExtension

    ext_module = PrebuiltExtension(os.environ['PREBUILT_FILE'])

    setup(
        name='my_package',
        version='version',
        cmdclass={
            'build_ext': prebuilt_binary,
        },
        ext_modules=[ext_module]
    )

In this example the `PREBUILT_FILE` environment variable contains the desired path.  The `cmdclass` mapping is required to tell
setuptools to use the `prebuilt_binary` class to "build" the extensions specified in `ext_modules`.

CMakeLists.txt example
----------------------
::

    find_package(Python REQUIRED)

    file(GLOB build_wheel_SOURCE_FILES pyproject.toml setup.py)

    add_custom_target(build_wheel
        COMMAND ${CMAKE_COMMAND} -E env PREBUILT_FILE=$<TARGET_FILE:py_module> ${Python_EXECUTABLE} ${CMAKE_CURRENT_SOURCE_DIR}/setup.py bdist_wheel
        SOURCES ${build_wheel_SOURCE_FILES}
        )

    add_dependencies(build_wheel py_module)

In this example cmake file `py_module` is the name of the target that builds the extension module.
It sets the `PREBUILT_FILE` environment variable used by `setup.py` to the output file of the `py_module` target.

Build dependencies
------------------
Don't forget to set `prebuilt_binaries` as a build-time dependancy in your `pyproject.toml` file::

    [build-system]
    requires = ["setuptools", "prebuilt_binaries"]


or in your `setup.cfg` file::

    [options]
    setup_requires =
        setuptools
        prebuilt_binaries