semvec/pypi-packages huggingface dataset:
pygt3x 0.7.1
Python module for reading GT3X/AGDC file format data
Requires Python: <=3.13,>3.9

# pygt3x
![Tests](https://github.com/actigraph/pygt3x/actions/workflows/tests.yml/badge.svg)

Python module for reading GT3X/AGDC file format data generated by ActiGraph devices.

## Example Usage

To read calibrated accelerometer data, you can use the code snippet below:

```python
from pygt3x.reader import FileReader

# Read raw data and calibrate, then export to pandas data frame
with FileReader("FILENAME") as reader:
    was_idle_sleep_mode_used = reader.idle_sleep_mode_activated
    df = reader.to_pandas()
    print(df.head(5))
```

If your AGDC file contains temperature data, you can read it using:

```python
from pygt3x.reader import FileReader

with FileReader("FILENAME") as reader:
    df = reader.temperature_to_pandas()
    print(df.head(5))
```
post_train 0.0.0a0
Post-training framework
Requires Python: <4.0,>=3.8

# post-train

[![Release](https://img.shields.io/github/v/release/nlile/post-train)](https://img.shields.io/github/v/release/nlile/post-train)
[![Build status](https://img.shields.io/github/actions/workflow/status/nlile/post-train/master.yml?branch=master)](https://github.com/nlile/post-train/actions/workflows/master.yml?query=branch%3Amaster)
[![codecov](https://codecov.io/gh/nlile/post-train/branch/master/graph/badge.svg)](https://codecov.io/gh/nlile/post-train)
[![Commit activity](https://img.shields.io/github/commit-activity/m/nlile/post-train)](https://img.shields.io/github/commit-activity/m/nlile/post-train)
[![License](https://img.shields.io/github/license/nlile/post-train)](https://img.shields.io/github/license/nlile/post-train)

Post-training framework

- **Github repository**: <https://github.com/nlile/post-train/>
- **Documentation** <https://nlile.github.io/post-train/>

## Getting started with your project

First, create a repository on GitHub with the same name as this project, and then run the following commands:

```bash
git init -b master
git add .
git commit -m "init commit"
git remote add origin git@github.com:nlile/post-train.git
git push -u origin master
```

Finally, install the environment and the pre-commit hooks with

```bash
make install
```

You are now ready to start development on your project!
The CI/CD pipeline will be triggered when you open a pull request, merge to master, or when you create a new release.

To finalize the set-up for publishing to PyPI or Artifactory, see [here](https://fpgmaas.github.io/cookiecutter-poetry/features/publishing/#set-up-for-pypi).
For activating the automatic documentation with MkDocs, see [here](https://fpgmaas.github.io/cookiecutter-poetry/features/mkdocs/#enabling-the-documentation-on-github).
To enable the code coverage reports, see [here](https://fpgmaas.github.io/cookiecutter-poetry/features/codecov/).

## Releasing a new version

- Create an API Token on [PyPI](https://pypi.org/).
- Add the API Token to your projects secrets with the name `PYPI_TOKEN` by visiting [this page](https://github.com/nlile/post-train/settings/secrets/actions/new).
- Create a [new release](https://github.com/nlile/post-train/releases/new) on Github.
- Create a new tag in the form `*.*.*`.
- For more details, see [here](https://fpgmaas.github.io/cookiecutter-poetry/features/cicd/#how-to-trigger-a-release).

---

Repository initiated with [fpgmaas/cookiecutter-poetry](https://github.com/fpgmaas/cookiecutter-poetry).
rss-digger 0.1.3
Retrieve a RSS feed given an URL.
Requires Python: >=3.12

# RSS Digger

RSS Digger is a Python library designed to help you discover RSS feeds from any given URL.
Whether you're working with YouTube channels, subreddits, blogs, or other platforms, RSS Digger simplifies the process
of finding and extracting RSS feed links.

With RSS Digger, you can:

- Automatically detect RSS feeds from a variety of sources.
- Handle complex URLs like YouTube channels, subreddits, and more.
- Easily integrate RSS feed discovery into your projects.

```bash
pip install rss-digger
```

## Quickstart

```python
import asyncio

from rss_digger import get_rss_feeds_for


async def main():
  rss_url = "https://realpython.com"
  rss_links = await get_rss_feeds_for(url=rss_url)

  print(rss_links)  # ["https://realpython.com/atom.xml", ]


if __name__ == "__main__":
  asyncio.run(main())
```

## Features

- YouTube Support: Extract RSS feeds from YouTube channel URLs.
  Example: https://www.youtube.com/@ExampleChannel → https://www.youtube.com/feeds/videos.xml?channel_id=...


- Reddit Support: Find RSS feeds for subreddits.
  Example: https://www.reddit.com/r/python/ → https://www.reddit.com/r/python.rss

...
Blogs and Websites: Detect RSS feeds from blogs and news websites.

Asynchronous: Built with asyncio for efficient, non-blocking operations.
python-pgp-check 0.3.2
A CLI tool to verify file hashes
Requires Python: >=3.6

# Python PGP Check

[![PyPI Version](https://img.shields.io/pypi/v/python-pgp-check)](https://pypi.org/project/python-pgp-check/)
[![PyPI Downloads](https://img.shields.io/pypi/dm/python-pgp-check)](https://pypi.org/project/python-pgp-check/)

[![License](https://img.shields.io/pypi/l/python-pgp-check)](https://pypi.org/project/python-pgp-check/)
[![Format](https://img.shields.io/pypi/format/python-pgp-check)](https://pypi.org/project/python-pgp-check/)
[![Implementation](https://img.shields.io/pypi/implementation/python-pgp-check)](https://pypi.org/project/python-pgp-check/)
[![Package Size](https://img.shields.io/github/repo-size/iiroan/python-pgp-check)](https://github.com/iiroan/python-pgp-check)

A quick python CLI tool to verify file PGP hashes


### Installation and usage

Install it with python pip using 

``` bash
pip install python-pgp-check
```

### Usage
Calculate Hash

to calculate the hash of a file:
```bash
python-pgp-check <file_path>
``` 

Verify Hash

To verify a file against an expected hash:
```bash
python-pgp-check <file_path> <expected_hash>
```

Specifying Hash Algorithm

By default, SHA-256 is used. To use a different algorithm:

```bash
python-pgp-check <file_path> [<expected_hash>] --algorithm <algorithm>
```

Supported algorithms: md5, sha1, sha256, sha512

### Examples

Calculate SHA-256 hash:
```bash
python-pgp-check /path/to/file
```
Verify file with SHA-256 hash:
```bash
python-pgp-check /path/to/file 5e884898da28047151d0e56f8dc6292773603d0d6aabbdd62a11ef721d1542d8
```

Calculate MD5 hash:
```bash
python-pgp-check /path/to/file --algorithm md5
```
Verify file with SHA-512 hash:
```bash
python-pgp-check /path/to/file 3c9909afec25354d551dae21590bb26e38d53f2173b8d3dc3eee4c047e7ab1c1eb8b85103e3be7ba613b31bb5c9c36214dc9f14a42fd7a2fdb84856bca5c44c2 --algorithm sha512
```



### Dev Setup

1. Create a virtual environment:
```bash
# On Windows
python -m venv venv

# On macOS/Linux
python3 -m venv venv
```

2. Activate the virtual environment:
```bash
# On Windows
venv\Scripts\activate

# On macOS/Linux
source venv/bin/activate
```

## Installation Options

### Option 1: Development Installation

1. Install dependencies:
```bash
pip install -r requirements.txt
```

2. Run the CLI directly for testing:
```bash
python src/pgp_check/cli.py
```

### Option 2: Package Installation

1. Install the package in editable mode:
```bash
pip install -e .
```

## Verification

Test the it installed correctly:
```bash
# If installed with Option 2
python-pgp-check --version
```

## Notes
- Always ensure your virtual environment is activated before running commands (you should see `(venv)` in your terminal prompt)
- Use `deactivate` to exit the virtual environment when done
- If you encounter permission errors, you may need to use `sudo` (Linux/macOS) or run as administrator (Windows)
gradable 0.0.1a0
Gradable reward signals
Requires Python: <4.0,>=3.8

# gradable

[![Release](https://img.shields.io/github/v/release/nlile/gradable)](https://img.shields.io/github/v/release/nlile/gradable)
[![Build status](https://img.shields.io/github/actions/workflow/status/nlile/gradable/master.yml?branch=master)](https://github.com/nlile/gradable/actions/workflows/master.yml?query=branch%3Amaster)
[![codecov](https://codecov.io/gh/nlile/gradable/branch/master/graph/badge.svg)](https://codecov.io/gh/nlile/gradable)
[![Commit activity](https://img.shields.io/github/commit-activity/m/nlile/gradable)](https://img.shields.io/github/commit-activity/m/nlile/gradable)
[![License](https://img.shields.io/github/license/nlile/gradable)](https://img.shields.io/github/license/nlile/gradable)

Gradable reward signals

- **Github repository**: <https://github.com/nlile/gradable/>
- **Documentation** <https://nlile.github.io/gradable/>

## Getting started with your project

First, create a repository on GitHub with the same name as this project, and then run the following commands:

```bash
git init -b master
git add .
git commit -m "init commit"
git remote add origin git@github.com:nlile/gradable.git
git push -u origin master
```

Finally, install the environment and the pre-commit hooks with

```bash
make install
```

You are now ready to start development on your project!
The CI/CD pipeline will be triggered when you open a pull request, merge to master, or when you create a new release.

To finalize the set-up for publishing to PyPI or Artifactory, see [here](https://fpgmaas.github.io/cookiecutter-poetry/features/publishing/#set-up-for-pypi).
For activating the automatic documentation with MkDocs, see [here](https://fpgmaas.github.io/cookiecutter-poetry/features/mkdocs/#enabling-the-documentation-on-github).
To enable the code coverage reports, see [here](https://fpgmaas.github.io/cookiecutter-poetry/features/codecov/).

## Releasing a new version

- Create an API Token on [PyPI](https://pypi.org/).
- Add the API Token to your projects secrets with the name `PYPI_TOKEN` by visiting [this page](https://github.com/nlile/gradable/settings/secrets/actions/new).
- Create a [new release](https://github.com/nlile/gradable/releases/new) on Github.
- Create a new tag in the form `*.*.*`.
- For more details, see [here](https://fpgmaas.github.io/cookiecutter-poetry/features/cicd/#how-to-trigger-a-release).

---

Repository initiated with [fpgmaas/cookiecutter-poetry](https://github.com/fpgmaas/cookiecutter-poetry).
check-bump 1.1.1
Check if pyproject.toml version was bumped
Requires Python: >=3.11
Keywords: versioning, check, CI, CD, version, bump

<p align="center"></p>
<h2 align="center">Check Bump</h2>
<p align="center">
<a href="https://github.com/rgryta/Check-Bump/actions/workflows/main.yml"><img alt="Build" src="https://github.com/rgryta/Check-Bump/actions/workflows/main.yml/badge.svg?branch=main"></a>
<a href="https://pypi.org/project/check-bump/"><img alt="PyPI" src="https://img.shields.io/pypi/v/check-bump"></a>
<a href="https://github.com/psf/black"><img alt="Code style: black" src="https://img.shields.io/badge/code%20style-black-000000.svg"></a>
<a href="https://github.com/PyCQA/pylint"><img alt="pylint" src="https://img.shields.io/badge/linting-pylint-yellowgreen"></a>
<a href="https://github.com/rgryta/NoPrint"><img alt="NoPrint" src="https://img.shields.io/badge/NoPrint-enabled-blueviolet"></a>
</p>

## About

Want to add version bump checks to your CI/CD pipeline? This packages makes it easy.
Simply execute `check-bump` within a directory where your `pyproject.toml` is located.

If there was a version bump, process will finish with exit code 0 - read stdout for the new version.
Otherwise, process will finish with exit code 1.

## Requirements

This package requires `tomlkit` package.

## Usage

### Command

Simply execute `check-bump` within a directory where your `pyproject.toml` is located. Or provide a path using `--path` argument.

```bash
user$ check-bump --help
usage: check-bump [-h] {toml,regex,touch} ...

Detect and retrieve version bump

options:
  -h, --help          show this help message and exit

Methods:
  {toml,regex,touch}  Different methods for parsing files
    toml              Parsing toml file
    regex             Regex file parsing
    touch             Touch file check
```

### Github Actions

#### Inputs

##### `method`

**Required** Select which method to use for detecting version bumps.

##### `path`

**Optional** Relative path of versioning file. Example: `'python_src/pyproject.toml'`

##### `prefix`

**Optional** Prefix to provide for version output. Example: `'v'`

#### Outputs

##### `bump`

**always** Whether there was a bump or not. Values: `'true'`|`'false'`

##### `version`

**optional** Current (if bumped) version with prefix. If there was no version bump - no output is provided.

## Example usage

```yml
- name: Check bump
  id: vbump
  uses: rgryta/Check-Bump@main
  with:
    method: 'toml'
    prefix: 'v'
```

And then you can later reference like:
```yml
- name: Tag repository
  if: steps.vbump.outputs.bump == 'true'
  run: |
    echo "I was bumped to version: ${{ steps.vbump.outputs.version }}"
```

## Development

### Installation

Install virtual environment and check_bump package in editable mode with dev dependencies.

```bash
python -m venv venv
source venv/bin/activate
pip install -e .[dev]
```


### How to?

Automate as much as we can, see configuration in `pyproject.toml` file to see what are the flags used.

```bash
staging format  # Reformat the code
staging lint    # Check for linting issues
staging test    # Run unit tests and coverage report
```