semvec/pypi-packages huggingface dataset:
ignition-api-stubs 8.3.3
Ignition Scripting API Stubs
Requires Python: <3.13,>=3.9
Keywords: hmi, ignition, inductive automation, scada

# ignition-api-stubs

<!--- Badges --->
[![PyPI - Python Version](https://img.shields.io/pypi/pyversions/ignition-api-stubs)](https://pypi.org/project/ignition-api-stubs/)
[![PyPI - Version](https://img.shields.io/pypi/v/ignition-api-stubs)](https://pypi.org/project/ignition-api-stubs/)
[![PyPI - Downloads](https://pepy.tech/badge/ignition-api-stubs)](https://pepy.tech/project/ignition-api-stubs)
[![ignition-api-stubs](https://snyk.io/advisor/python/ignition-api-stubs/badge.svg)](https://snyk.io/advisor/python/ignition-api-stubs)
[![ci](https://github.com/ignition-devs/ignition-api/actions/workflows/ci.yml/badge.svg?branch=8.3)](https://github.com/ignition-devs/ignition-api/actions/workflows/ci.yml)
[![Join us on GitHub discussions](https://img.shields.io/badge/github-discussions-informational)](https://github.com/orgs/ignition-devs/discussions)

This package contains a collection of [stubs] for [`ignition-api-8.3`]. These
files were generated using `mypy`'s [`stubgen`].

## Installation and usage

To use ignition-api-stubs, you may install it with `pip`. It requires Python
3.7+ through 3.12.

> [!WARNING]
> Python 3.13 will not be supported.

```sh
python3 -m pip install ignition-api-stubs
```

To run `mypy` against your code, execute the following command passing the
source directory (typically `src`) or a single file:

> [!NOTE]
> Ensure you have installed [`mypy`] before running the commands
> below.

```sh
python3 -m pip install "mypy[python2]==0.971"
```

Then

```sh
mypy --py2 src
```

Or

```sh
mypy --py2 code.py
```

## Contributing

See [CONTRIBUTING.md].

## Discussions

Feel free to post your questions and/or ideas at [Discussions].

## Contributors

Thanks to everyone who has contributed to this project.

Up-to-date list of [contributors].

## License

See the [LICENSE].

## Code of conduct

See [CODE_OF_CONDUCT.md].

<!-- Links -->
[CODE_OF_CONDUCT.md]: https://github.com/ignition-devs/.github/blob/main/CODE_OF_CONDUCT.md
[CONTRIBUTING.md]: https://github.com/ignition-devs/ignition-api-8.3/blob/main/CONTRIBUTING.md
[contributors]: https://github.com/ignition-devs/ignition-api-8.3-stubs/graphs/contributors
[Discussions]: https://github.com/orgs/ignition-devs/discussions
[`ignition-api-8.3`]: https://github.com/ignition-devs/ignition-api-8.3
[LICENSE]: https://github.com/ignition-devs/ignition-api-8.3/blob/main/LICENSE
[`mypy`]: https://coatl-mypy.readthedocs.io/en/v0.971/
[`stubgen`]: https://coatl-mypy.readthedocs.io/en/v0.971/stubgen.html
[stubs]: https://www.python.org/dev/peps/pep-484/
xgae 0.4.2
Extreme General Agent Engine
Requires Python: >=3.11

# XGAE: Extreme General Agent Engine 
## XGAE Features
### Functional Features
- Support Custom prompt and external MCP Tools
- Support Langfuse
- Support Langgraph
- Support GAIA2 ARE agent and Custom MCP Apps, Leading over ARE 'default agent'
- Support Human-in-Loop in agent
- Can Use A2A protocol call A2A Agent as tool by 'xgaproxy' project
- Can Use E2B or Daytona Sandbox of 'xgatools' project

### Non-Functional Features
- Faster than SUNA Engine's speed
- Architecture is lighter than SUNA Engine
- Separate tools from Agent Engine


## XGAE Run Mode
### General Agent
- Use General Agent Prompt
- Use general tools mainly
- In addition to using general tools, custom tools can also be used

### Custom Agent
- Use User Custom Prompt
- Use custom tools mainly
- Some general tools can also be used, like 'web_search'


## Examples
- engine: Use XGA Engine in various scenarios, you can find out how to use General or Custom Agent
- langgraph:  Build Reflect mode Langgraph Agent by XGA Engine
- are: Build GAIA2 ARE Agent by XGA Engine
- tools: Simulation tools for example and test
hexdoc-hexchanting 1.1.7.1.0
Imbue tools with Hex Casting powers.
Requires Python: >=3.12
Keywords: hexdoc

# hexdoc-hexchanting

Python web book docgen and [hexdoc](https://pypi.org/project/hexdoc) plugin for Hexchanting.

Imbue tools with Hex Casting powers.

## Version scheme

We use [hatch-gradle-version](https://pypi.org/project/hatch-gradle-version) to generate the version number based on whichever mod version the docgen was built with.

The version is in this format: `mod-version.python-version.mod-pre.python-dev.python-post`

For example:
* Mod version: `0.11.1-7`
* Python package version: `1.0.dev0`
* Full version: `0.11.1.1.0rc7.dev0`

## Setup

Install [uv](https://docs.astral.sh/uv/getting-started/installation/), then:

```sh
uv sync

.\.venv\Scripts\activate   # Windows
. .venv/bin/activate.fish  # fish
source .venv/bin/activate  # everything else
```

## Usage

For local testing, create a file called `.env` in the repo root following this template:
```sh
GITHUB_REPOSITORY=arconyx/hexchanting
GITHUB_SHA=main
GITHUB_PAGES_URL=https://arconyx.github.io/hexchanting/
```

Useful commands:

```sh
# update your Python environment and lockfile if you added new dependencies
uv sync

# show help
hexdoc -h

# render and serve the web book in watch mode
nodemon --config doc/nodemon.json

# render and serve the web book
hexdoc serve

# build and merge the web book
hexdoc build
hexdoc merge

# start the Python interpreter with some extra local variables
hexdoc repl
```