semvec/pypi-packages huggingface dataset:
mseep-mcp-atlassian 0.0.0
The Model Context Protocol (MCP) Atlassian integration is an open-source implementation that bridges Atlassian products (Jira and Confluence) with AI language models following Anthropic's MCP specification. This project enables secure, contextual AI interactions with Atlassian tools while maintaining data privacy and security. Key features include:
Requires Python: >=3.10

Package managed by MseeP.ai
python-takauma 0.6.3
Python-moduulien tiedostoversiointi
Requires Python: >=3.8

python-takauma
==============

Python-moduulien tiedostoversiointi


Luokkakohtainen versionmuodostus:
--------------------------------

Oletetaan, että paketti `python-foobar` on asennettu, ja sen versionumero on 1.2.3.

Olkoon tiedosto `spam.py` seuraavansisältöinen:
```python
# python-foobar/foobar/spam.py
from takauma import Versio

class Spam:
  __versio__ = Versio()

print(Foo.__versio__)
```

Tällöin komento `python -m foobar.spam` tulostaa `Version('1.2.3')`.


Aiemmat luokkaversiot:
---------------------

Oletetaan paketin asennus samoin kuin edellä.

Olkoon tiedosto `eggs.py` seuraavansisältöinen:
```python
# python-foobar/foobar/eggs.py
# versiointi: *
from takauma import etsi_versiot

class Eggs:
  luku = 42

Eggs._aiemmat_versiot = etsi_versiot(Eggs)

for versio in '1.2.4', '1.2.3', '1.2.2', '1.2.1', '1':
  try: print(Eggs._aiemmat_versiot[versio].luku)
  except Exception as exc: print(exc)
```

Oletetaan lisäksi, että levyllä on jäljellä aiempi versio samasta tiedostosta:
```python
# python-foobar/foobar/eggs-1.2.1.py
class Eggs:
  luku = 24
```

Silloin komento `python -m foobar.eggs` tulostaa seuraavasti:
```
42
42
24
24
KeyError: '1'
```

Aiempien versioiden luonti:
--------------------------

Aiempi tiedostoversio tunnistetaan tiedostonimen mukaan silloin, kun se on muotoa `<moduuli>-<versio>.py`, missä `<moduuli>.py` on viimeisin, ajossa oleva tiedostoversio.

Git-versiointi (https://pypi.org/project/git-versiointi/) tallentaa aiemmat versiot automaattisesti git-muutostietojen mukaan erityisen versiointimerkinnän perusteella: ks. edellä `eggs.py`-tiedostossa rivi 2.

Versiointimääritys (`# versiointi: x`) aiheuttaa sen, että kopiot tiedostosta tallennetaan git-versiohistorian mukaisesti git-revisioon `x` asti (poissulkevasti), tai historian alkuun saakka (`*`).

Huomaa, että aiempien tiedostoversioiden muodostus versiomäärityksen perusteella tapahtuu pip-asennuksen `build_py`-vaiheessa, eikä niitä siis synny automaattisesti kehitystilassa olevalle paketin sisälle. Sen sijaan aiemman version testaus onnistuu vaikkapa seuraavantyyppisen komennon avulla:
```bash
git -C python-foobar show HEAD~2:foobar/eggs.py > python-foobar/foobar/eggs-1.2.1.py
```
pytest-reverse 1.9.0
Pytest plugin to reverse test order.
Requires Python: >=3.9
Keywords: pytest, reverse

==============
pytest-reverse
==============

.. image:: https://img.shields.io/github/actions/workflow/status/adamchainz/pytest-reverse/main.yml.svg?branch=main&style=for-the-badge
   :target: https://github.com/adamchainz/pytest-reverse/actions?workflow=CI

.. image:: https://img.shields.io/pypi/v/pytest-reverse.svg?style=for-the-badge
   :target: https://pypi.org/project/pytest-reverse/

.. image:: https://img.shields.io/badge/code%20style-black-000000.svg?style=for-the-badge
   :target: https://github.com/psf/black

.. image:: https://img.shields.io/badge/pre--commit-enabled-brightgreen?logo=pre-commit&logoColor=white&style=for-the-badge
   :target: https://github.com/pre-commit/pre-commit
   :alt: pre-commit

Pytest plugin to reverse test order.

----

**Testing a Django project?**
Check out my book `Speed Up Your Django Tests <https://adamchainz.gumroad.com/l/suydt>`__ which covers loads of recommendations to write faster, more accurate tests.
I created pytest-reverse whilst working on the book!

----

Installation
============

Install with:

.. code-block:: bash

    python -m pip install pytest-reverse

Python 3.9 to 3.14 supported.

Usage
=====

Pytest will automatically find the plugin and use it when you run ``pytest``.
You can reverse test order by passing the ``--reverse`` flag:

.. code-block:: bash

    pytest --reverse

You can make this always apply by adding it to the ``addopts`` setting in your
``pytest.ini`` (or `other configuration
file <https://docs.pytest.org/en/latest/customize.html#adding-default-options>`__):

.. code-block:: ini

    [pytest]
    addopts = --reverse

History
=======

I'm the creator and maintainer of
`pytest-randomly <https://github.com/pytest-dev/pytest-randomly>`__, a plugin
for randomly ordering tests. @thbde opened an issue there pointing to the paper
`Empirically revisiting the test independence
assumption <https://dl.acm.org/doi/10.1145/2610384.2610404>`__, which covers
test reordering techniques. It turns out that reversal is nearly as effective
as randomization.

Test reversal is available `in Django's test
runner <https://docs.djangoproject.com/en/dev/ref/django-admin/#cmdoption-test-reverse>`__.
I figured such an option or plugin would exist for pytest already, but it
didn't, so I made it here.
veeink-mcp-server 0.2.0
Veeink的MCP服务
Requires Python: >=3.13



````markdown
# veeink-mcp-server

A simple [FastMCP](https://pypi.org/project/fastmcp/) server example built with Python.  
This project demonstrates how to expose custom **tools** and **resources** over the [Model Context Protocol (MCP)](https://modelcontextprotocol.io/).

---

## 🚀 Features

- ⚡ Built with [FastMCP](https://pypi.org/project/fastmcp/)  
- 🔧 Provides a simple `add(a, b)` tool  
- 📡 Supports dynamic greeting resources (`greeting://{name}`)  
- 🖥️ Works over **stdio** (default), **SSE**, or **Streamable HTTP** transports  

---

## 📦 Installation

```bash
pip install veeink-mcp-server
````

Or using [uv](https://github.com/astral-sh/uv):

```bash
uv tool install veeink-mcp-server
```

---

## 🖥️ Usage

After installation, run the MCP server:

```bash
veeink-mcp-server
```

By default it runs with `stdio` transport, but you can also configure:

```python
def main() -> None:
    mcp.run(transport="stdio")            # Default
    # mcp.run(transport="sse")            # SSE transport
    # mcp.run(transport="streamable-http") # Streamable HTTP transport
```

---

## 🔧 Example Tools & Resources

This server exposes:

### 1. Tool: `add`

```python
@mcp.tool()
def add(a: int, b: int) -> dict:
    """Add two numbers"""
    return {"result": a + b}
```

✅ Example call:

```json
{"tool": "add", "args": {"a": 2, "b": 3}}
```

Response:

```json
{"result": 5}
```

---

### 2. Resource: `greeting://{name}`

```python
@mcp.resource("greeting://{name}")
def get_greeting(name: str) -> str:
    """Get a personalized greeting"""
    return f"Hello, {name}!"
```

✅ Example call:

```json
{"resource": "greeting://Alice"}
```

Response:

```
Hello, Alice!
```

---

## 🛠 Development

Clone the repository:

```bash
git clone https://github.com/yourusername/veeink-mcp-server.git
cd veeink-mcp-server
```

Install in editable mode:

```bash
pip install -e .
```

Run the server:

```bash
veeink-mcp-server
```