semvec/pypi-packages huggingface dataset:
phinity 0.1.2
A framework for fine-tuning language models with preference data
Requires Python: >=3.7

# Phinity

A self-improvement SDK for language models.

## Installation

```bash
pip install -e .
```

## Usage

```python
from phinity import LLMGenerator
from phinity.utils.config import Config

# Setup OpenAI
Config.setup_openai()  # Or provide key: Config.setup_openai("your-api-key")

# Create generator
generator = LLMGenerator()

# Generate pairs
instructions = ["Write a haiku about programming"]
pairs = generator.generate_pairs(instructions=instructions)
```
```

Now let's create and activate a virtual environment:

```bash:create_project.sh
# Create project structure
mkdir -p phinity/phinity/{core,generators,evaluators,utils}
mkdir -p phinity/examples
touch phinity/README.md
touch phinity/setup.py
touch phinity/requirements.txt
touch phinity/phinity/__init__.py
touch phinity/phinity/core/__init__.py
touch phinity/phinity/generators/__init__.py
touch phinity/phinity/evaluators/__init__.py
touch phinity/phinity/utils/__init__.py
touch phinity/.env.template
touch phinity/.gitignore

# Create and activate virtual environment
cd phinity
python -m venv venv
source venv/bin/activate  # On Windows, use: venv\Scripts\activate

# Install package in development mode
pip install -e .
```

Now you should be able to:

1. Create the virtual environment and install the package:
```bash
cd phinity
python -m venv venv
source venv/bin/activate  # On Windows, use: venv\Scripts\activate
pip install -e .
```

2. Copy the template and add your API key:
```bash
cp .env.template .env
# Edit .env and add your API key
```

3. Run the test:
```bash
python examples/openai_test.py
```

Would you like me to make any adjustments to these files or add any additional setup steps?
baymesh 0.7.3
Baymesh command line and library for members of Bayme.sh
Requires Python: >=3.11

# Baymesh CLI and Python library

A WIP and unofficial [baymesh](http://bayme.sh) CLI and Python library for validating nodes that are a part of the [Meshtastic Bay Area Group's](https://bayme.sh/) mesh network. It's most useful as a way to doublecheck your work after following the [Bayme.sh Getting Started Guide](https://bayme.sh/docs/getting-started/), since the settings can be fiddly and easy to get wrong.

## Status

This project is in an experimental state. No support is offered yet!

## Requirements

* Python 3.11+
* macOS, Linux, or Windows

## Installing

To install the `baymesh` CLI, install via Homebrew:

```shell
brew install gtaylor/baymesh/baymesh
```

Or PyPi:

```shell
pypi install baymesh
```

## Usage

### Setting your node up to work with the Bay Mesh

To run your node through a guided setup flow, connect it via USB and run:

```shell
baymesh setup
```

This will leave you with a set of reasonable defaults applied to your node.

### Validating your node's configs

If you'd like to make sure that your node is compliant with the [Bay Mesh Recommended Settings](https://bayme.sh/docs/getting-started/recommended-settings/), connect it via USB and run:

```shell
baymesh validate
```

The CLI will recommend settings changes if it finds anything out of spec.

## Contributing

To get your environment set up, you'll need the `uv` package manager. See [Installing uv](https://docs.astral.sh/uv/getting-started/installation/). Once `uv` is installed, do the following:

```shell
git clone git@github.com:gtaylor/baymesh-cli.git
cd baymesh-cli
make setup-dev
# Do your dev work here and run linters and tests afterwards:
make
```

## License

The contents of this repository are licensed under the GPLv3. A copy of the license may be found in the [LICENSE](./LICENSE) file in the repo root.
slurm-workflow-utils 0.1.1
Collection of Python scripts to facilitate creation and dispatching of computational jobs
Requires Python: >=3.10
Keywords: slurm_workflow_utils

=====================
Slurm Workflow Utils
=====================

Collection of Python scripts to facilitate creation and dispatching of computational jobs via SLURM sbatch scripts.


Features
--------

To following exported console scripts are available:

- workflow-builder
- workflow-launcher


=======
History
=======

0.1.0 (2024-02-01)
------------------

* First release on PyPI.
data-file-profiler-utils 0.1.7
A Python module for simple data file profiling.
Requires Python: >=3.10
Keywords: data_file_profiler_utils

========================
Data File Profiler Utils
========================

A Python module for simple data file profiling.


Usage
-----

Installation
------------

.. code-block:: shell

    pip install data-file-profiler-utils


Integration
-----------

.. code-block:: python

    from import data_file_profiler_utils import Manager as ProfileManager

    pm = ProfileManager()
    pm.profile_file("/tmp/patient002.vcf")


Exported Console Script
-----------------------

Contents of sample data file:

.. code-block:: shell

    cat -n sample.tsv                      
    1  #CHROM  POS     ID      REF     ALT     QUAL    FILTER  INFO
    2  1       12345   rs567   A       G       50      PASS    DP=30;AF=0.2;AN=1000;CSQ=missense_variant|HIGH|GeneA|ENSG00000112345|transcriptA|ENST00000234567|protein_coding|1/10|c.123C>T|p.Arg41Trp|123/1000|ensembl
    3  2       56789   rs890   T       C       44      PASS    DP=25;AF=0.1;AN=1200;CSQ=synonymous_variant|MEDIUM|GeneB|ENSG00000123456|transcriptB|ENST00000345678|protein_coding|5/20|c.567A>G|p.Ala189Ala|567/1200|ensembl
    4  3       98765   rs123   G       T       60      PASS    DP=40;AF=0.3;AN=800;CSQ=splice_acceptor_variant|HIGH|GeneC|ENSG00000134567|transcriptC|ENST00000456789|protein_coding|2/15|c.987+1G>T|p.?|987/800|ensembl
    5  1       34567   rs456   C       A       55      PASS    DP=35;AF=0.15;AN=900;CSQ=frameshift_variant|HIGH|GeneX|ENSG00000145678|transcriptX|ENST00000567890|protein_coding|8/25|c.345_346insT|p.Leu116Phefs*12|345/900|ensembl


Invocation of the exported console script:

.. code-block:: shell
  
    profile-data-file --infile /tmp/demo-data-file-profiler-utils/sample.tsv --verbose --outdir /tmp/demo-data-file-profiler-utils/
    --logfile was not specified and therefore was set to '/tmp/demo-data-file-profiler-utils/profile_data_file.log'
    Wrote profile metadata file '/tmp/demo-data-file-profiler-utils/sample.tsv.profile.txt'
    The log file is '/tmp/demo-data-file-profiler-utils/profile_data_file.log'
    Execution of '/tmp/data-file-profiler-utils/venv/lib/python3.10/site-packages/data_file_profiler_utils/profile_data_file.py' completed


Contents of the profile report:

.. code-block:: shell

    cat -n /tmp/demo-data-file-profiler-utils/sample.tsv.profile.txt
    1  ## method-profiled: /tmp/data-file-profiler-utils/venv/lib/python3.10/site-packages/data_file_profiler_utils/manager.py
    2  ## date-profiled: 2025-02-15-142732
    3  ## profiled-by: sundaram
    4  file: /tmp/demo-data-file-profiler-utils/sample.tsv
    5  md5sum: 786b82b2414d3acf7af34c068e358759
    6  date_created: 2025-02-15 14:06:37.202165
    7  file_size: 776
    8  line_count: 5


=======
History
=======

0.1.0 (2024-02-10)
------------------

* First release on PyPI.