semvec/pypi-packages huggingface dataset:
optionlab 1.5.1
Python library for evaluating options trading strategies
Requires Python: <4.0,>=3.10

![OptionLab](https://raw.githubusercontent.com/rgaveiga/optionlab/refs/heads/main/optionlab.png)

# OptionLab

This package is a lightweight library designed to provide quick evaluation of options trading 
strategies. It produces various outputs:

- the profit/loss profile of the strategy on a user-defined target date

- the range of stock prices for which the strategy is profitable (i.e., generating a return of 
at least \$0.01)

- the Greeks (delta, theta, rho, vega and gamma) associated with each leg of the strategy 

- the resulting debit or credit on the trading account 

- the maximum and minimum returns within a specified lower and higher price 
range of the underlying asset 

- The expected profit when the strategy is profitable and the expected loss if it proves unprofitable 

- the strategy's probability of profit.

## Contact

If you have any questions, corrections, comments or suggestions, just 
[drop a message](mailto:roberto.veiga@ufabc.edu.br).

You can also reach me on [Linkedin](https://www.linkedin.com/in/roberto-gomes-phd-8a718317b/) or 
follow me on [X](https://x.com/rgaveiga).

> [!NOTE]
> If you want to support this and other open source projects that I maintain, become a 
>[sponsor on Github](https://github.com/sponsors/rgaveiga).

## Installation

The easiest way to install **OptionLab** is using **pip**:

```
pip install optionlab
```

## Documentation

You can access the API documentation for **OptionLab** on the [project's GitHub Pages site](https://rgaveiga.github.io/optionlab).

## Contributions

Contributions are definitely welcome. However, it should be mentioned that this 
repository uses [poetry](https://python-poetry.org/) as a package manager and 
[git hooks](https://git-scm.com/book/en/v2/Customizing-Git-Git-Hooks) with 
[pre-commit](https://pre-commit.com/) to customize actions on the repository. Source 
code must be formatted using [black](https://github.com/psf/black).

## Disclaimer

This is free software and is provided as is. The author makes no guarantee that its 
results are accurate and is not responsible for any losses caused by the use of the 
code.

Bugs can be reported as issues.

> [!CAUTION]
> Options are very risky derivatives and, like any other type of financial vehicle, 
> trading options requires due diligence. This code is provided for educational and 
> research purposes only.
open-ff 0.1.0
OpenFF: Fetch FF account info and ban status
Requires Python: >=3.7

OpenFF

Introduction

OpenFF is a Python package that allows users to fetch any FF account info directly from Python.

Created by Abdul Moeez in Pakistan.

Example FF UID: 12544204952.



---

Usage

OpenFF contains two functions:

1. show_info(uid, region)


2. is_ban(uid)




---

Function: show_info()

Parameters:

uid (int) → FF UID (example: 12544204952)

region (str) → Region code (example: "PK")


Returns:

Account information in JSON format.


Example:


import OpenFF

info = OpenFF.show_info(12544204952, "PK")
print(info)


---

Function: is_ban()

Parameters:

uid (int) → FF UID (example: 12544204952)


Returns:

Ban status of the account in JSON format.


Example:


import OpenFF

ban_status = OpenFF.is_ban(12544204952)
print(ban_status)


---

Notes

UID must be an integer (11 digits)

Region must be a string

Functions have automatic error handling



---

Thanks

Thanks for using my Python package! 🎉
uv-outdated 1.0.4
Show uv outdated packages in a nicer way
Requires Python: >=3.12
Keywords: requirements, packaging

# uv-outdated

Show outdated packages in your [uv](https://github.com/astral-sh/uv) projects with
better formatting and dependency context.

While `uv pip list --outdated` shows which packages have newer versions available,
`uv-outdated` adds useful context like dependency relationships, constraint information,
and organizes output by dependency groups.

## Usage

Run in any directory with a `uv.lock` file:

```bash
uvx uv-outdated [OPTIONS]
```

### Options

- `--show-headers/--no-headers`: Include table headers (default: no headers)
- `--why/--no-why`: Show constraint and dependents columns (default: show)
- `--direct/--all`: Only show direct dependencies (default: all)
- `--transitive/--all`: Only show transitive dependencies (default: all)
- `--group-by-ancestor`: Group transitive dependencies under their direct ancestors

### Example Output

```
Package         Current  Latest   Constraint  Dependents      Description
requests        2.28.0   2.31.0   >=2.25.0    mypy, pytest   HTTP library for Python
urllib3         1.26.0   2.0.7    <2.0.0      requests        HTTP library with thread-safe connection pooling

[group:dev]
pytest          7.0.0    8.0.0    ^7.0.0      pytest-cov     Simple and scalable testing
pytest-cov      4.0.0    5.0.0                               Coverage plugin for pytest
```

## What it shows you

**Dependency groups**: Packages are organized by their groups from `pyproject.toml` (main dependencies, optional dependencies, development groups).

**Why packages can't upgrade**: 
- Yellow versions indicate the package is constrained by version specifiers
- Red versions show packages that can be freely upgraded
- The Constraint column shows the limiting specifier

**Dependency relationships**: The Dependents column shows which other packages require each outdated package.

**Hierarchical view**: With `--group-by-ancestor`, transitive dependencies are grouped under their direct dependency parents.

## How it works

The tool combines information from:
- `uv.lock` for exact versions and dependency relationships
- `pyproject.toml` for dependency groups and constraints  
- `uv pip list --outdated` for available updates
- Site-packages metadata for descriptions (when available)

It works even when your virtual environment isn't activated or available.

## Requirements

- Python 3.12+
- A project with `uv.lock`
- Optional: `pyproject.toml` for dependency group information

## Why this exists

`uv pip list --outdated` gives you the basics, but when you're managing a project with many dependencies across different groups, it helps to see:
- Which outdated packages are your direct dependencies vs. transitive
- Why certain packages can't be upgraded (version constraints)
- How dependencies relate to each other
- Packages organized by their purpose (dev, test, optional features, etc.)

This is particularly useful for larger projects where understanding the dependency tree matters for upgrade decisions.