semvec/pypi-packages huggingface dataset:
wgl001package 0.1.0
A short description
License: MIT
Requires Python: >=3.9

myproject/
├── setup.py              # 打包配置文件
├── README.md             # 项目说明
├── LICENSE               # 许可证文件
├── mypackage/            # 主模块目录
│   ├── __init__.py       # 模块初始化文件
│   └── module_file.py    # 代码文件
└── tests/                # 测试目录（可选）


使用说明
解压后，进入项目根目录（gethub_demo/）
# 升级 packaging
pip install -U packaging
安装打包工具：pip install build twine
生成包文件：python -m build
上传到 PyPI：python -m twine upload dist/*（需先注册 PyPI 账号）

PyPI 账号在 Windows 系统的命令提示符中，执行以下命令：
set TWINE_USERNAME=your_pypi_username
set TWINE_PASSWORD=your_pypi_password

PyPI 账号在 Linux 或 macOS 系统的终端中，执行以下命令：
export TWINE_USERNAME=your_pypi_username
export TWINE_PASSWORD=your_pypi_password

https://blog.csdn.net/QIDAL/article/details/148013142
enrichment-tools 0.2.3
MCP Server for catering to Enrichment APIs of Apollo.io
License: MIT
Requires Python: >=3.9

# Enrichment Tools MCP Server

A FastMCP server that exposes Apollo.io enrichment APIs as MCP tools, using an OpenAPI specification. This server is designed for remote, programmatic use as a managed MCP server, and is configurable via environment variables.

---

## Features

- Exposes Apollo.io enrichment endpoints as MCP tools
- Loads OpenAPI specification from an embedded YAML file
- Supports remote configuration and deployment as an MCP server
- Secure: API credentials are provided via environment variables (`API_KEY`, `ACCESS_TOKEN`)
- Health check endpoint for server monitoring
- Built on top of FastMCP and httpx for async, robust API proxying

---

## Supported API Endpoints

The following Apollo.io enrichment APIs are exposed as MCP tools:

- **POST /api/v1/people/match** &mdash; Enrich data for a single person                       (API Reference: [https://docs.apollo.io/reference/people-enrichment])
- **POST /api/v1/organizations/enrich** &mdash; Enrich data for a single organization         (API Reference: [https://docs.apollo.io/reference/organization-enrichment])

---

## Requirements
Run as a remote host config


## Running as a Remote MCP Server

To run this server as a remote MCP server, add the following to your MCP configuration:

## MCP Client Integration

You can use this server with Cursor by adding in global `mcp.json` config

```json
{
  "mcpServers": {
    "Apollo.io": {
      "command": "uvx",
      "args": [
        "enrichment_tools"
      ],
      "env":{
        "API_KEY": "abcd",
        "ACCESS_TOKEN": "abcd"
      }
    }
  }
}
```
_Requires passing either API_KEY or ACCESS_TOKEN for authorization_

This will allow your MCP client to launch and connect to the enrichment tools server automatically.
pytest-typing-runner 0.6.2
Pytest plugin to make it easier to run and check python code against static type checkers
License: MIT
Requires Python: >=3.10

Pytest Typing Runner
====================

This is a plugin for pytest to assist in generating scenarios to run static
type checking against.

History
-------

This plugin comes out of a `fork`_ of the `pytest_mypy_plugins`_ pytest plugin
for writing tests that pytest can use to run mypy against sets of files.

The difference for this plugin is that it provides a pytest fixture to do work from
rather than exposing a ``yml`` interface for writing tests. It also allows for running
mypy multiple times in the same test with changes to the code being statically type
checked. And also has some different mechanisms for expressing the expected output
from mypy.

.. _pytest_mypy_plugins: https://pypi.org/project/pytest-mypy-plugins/
.. _fork: https://github.com/typeddjango/pytest-mypy-plugins/issues/144

Features
--------

* Provides pytest fixtures to help create scenarios for testing a type checker
* Each scenario is a set of files and a set of expectations around the behaviour
  of the type checker
* Scenarios may comprise of multiple runs of the type checker to check the
  behaviour of the type checker when changes are made against a warm cache
* Possible to run the same tests with different "strategies" where a strategy
  is a combination of specific type checker and default arguments
* Currently only supports ``mypy`` by default but should be possible to easily
  add more type checkers.
* Adds the ability to create files using a syntax for representing expectations
  in both the style used by ``mypy`` tests and a format introduced by this project
  that in some ways is a bit clearer and more expressive.

Built Docs
----------

https://pytest-typing-runner.readthedocs.io