semvec/pypi-packages huggingface dataset:
ezx-pyapi 1.1.2
EZX API client and message library for communicating with the iServer.
License: MIT
Requires Python: <4,>=3.8
Keywords: EZX iServer API trading

# EZX API

EZX Api Network Client, messages and library functions for sending and receiving orders to the EZX iServer.  Release Notes can be viewed here: [CHANGELOG-API.md](https://github.com/EZXInc/ezx-sample-py/blob/master/CHANGELOG-API.md).


# Installing


```bash

    pip install ezx-pyapi
    
```

# Usage


The iServer API is not really designed to be run interactively, although it is possible to do it, as shown below. 
The easiest way to familiarize yourself with the API is to download and run the sample API app, [ezx-sample-py](https://github.com/EZXInc/ezx-sample-py), from Github.

**Interactive Mode**


```python

	from interactive import * #this creates an interactive connection to the iserver
	
	
	# send an order
	from iserver.msgs.convenience_msgs import *
	order = NewOrder('ZVZZT',1,100,1.25,'SIMU')
	client.send_message(order)
	
	# type: show_help() to display avaialble functions in the interactive environment
	
	Available functions: (type help(function name) to see the parameters for the function.):
	----------------------------------------------------------------------------------------
	connect - Connect to the iserver.
	stop - Disconnect from the iserver.  You will need to call the connect method again to reconnect.
	status - Indicates connection status. if connected=True, then the client is logged in to the iserver.
	show_help - Displays information about available functions.
	----------------------------------------------------------------------------------------
	
	 status()
	 iserver client connected=True. company=EROOM, user=test1
	 
	 # Replace an order
	 client.send_message(ReplaceOrder(551, -1.24, 60))
	 
	 # Cancel an order
	 client.send_message(CancelOrder(551))
	 
	 # disconnect
	 stop()
	 
	
```
**More...**

The default message handler just prints the responses from the server.  You can set your own handler as follows:

```python

	from iserver.msgs.OrderResponse import OrderResponse
	
	responses = []
	import iserver.net
	def my_msg_handler(msg_subtype: int, msg: EzxMsg):
		iserver.net.empty_msg_handler(msg_subtype, msg) # print the message
		# write your handling logic here.
		responses.append(msg)
		
	client._msg_handler = my_msg_handler  # normally this is set in the ApiClient constructor
	
	client.send_message(order)
			
```

Also see the [EZX API Quick Start Guide](https://docs.google.com/document/d/1VcAYjFDZfIbQCVmVN4CZ_U6d3O3dHbnFNuiIBec8L3M) for more details on the API.
NEMO-periodic-table-question 2.1.1
Install Periodic table question plugin for NEMO
License: MIT
Requires Python: >=3.9
Keywords: NEMO

# NEMO Periodic Table Question

This plugin for NEMO allows to use a `periodic_table` type of question in post usage questions or reservation questions.

# Compatibility:

NEMO/NEMO-CE >= 7.0.0 ----> NEMO-Reports >= 2.0.0

# Installation

`pip install NEMO-periodic-table-question`

# Add NEMO Periodic Table Question

in `settings.py` add to `INSTALLED_APPS`:

```python
INSTALLED_APPS = [
    '...',
    'NEMO_periodic_table_question',
    '...'
]
```

# Usage
Use `type: "periodic-table"` in Tool post usage questions or Reservation questions.

Options:
 - required: true or false (default: false)
 - collapsible: true or false (default: false)
 - collapsed: true or false (default: false)
 - help: "Some help text to display under the periodic table"

**Important note**:<br>
The `collapsible`/`collapsed` options aren't supported in the admin preview but should work in the calendar.
colight-site 2025.4.1.dev202506261550
Static site generator for Colight visualizations
License: MIT
Requires Python: >=3.10

# Colight Site

Static site generator for Colight visualizations.

Converts `.colight.py` files into markdown/HTML documents where:

- Comments become narrative markdown
- Code blocks are executed to generate Colight visualizations
- Output is embedded as interactive `.colight` files

## Usage

```bash
# Build a single file
colight-site build src/post.colight.py --output build/post.md

# Watch for changes
colight-site watch src/ --output build/

# Initialize new project
colight-site init my-blog/
```

## File Format

`.colight.py` files mix comments (markdown) with executable Python code:

```python
# My Data Visualization
# This creates an interactive plot...

import numpy as np
x = np.linspace(0, 10, 100)

# The sine wave
np.sin(x)  # This expression generates a colight visualization
```

## Pragma Directives

Control the output format and visibility of content using pragma comments:

### File-level pragmas

Place at the beginning of the file, followed by a blank line:

```python
# %% hide-code

# Your content here...
```

### Form-level pragmas

Place directly before a code block:

```python
# | show-code
x = np.array([1, 2, 3])
```

### Available pragmas

- `hide-code` / `show-code` - Hide or show all code blocks
- `hide-statements` / `show-statements` - Hide or show Python statements (imports, assignments)
- `hide-visuals` / `show-visuals` - Hide or show Colight visualizations
- `hide-prose` / `show-prose` - Hide or show markdown prose (comments)
- `format-html` - Output in HTML format
- `format-markdown` - Output in Markdown format

### Pragma formats

```python
# %% hide-code          # Double percent format
# | show-visuals        # Pipe format
#| colight: hide-prose  # Legacy format (still supported)
```

### Precedence

1. Form-level pragmas (highest priority)
2. CLI options
3. File-level pragmas
4. Defaults (lowest priority)

`show-*` pragmas always override corresponding `hide-*` pragmas.
glpipci 0.1.4rc5
Um cliente Python para a API do GLPI
License: MIT
Requires Python: >=3.10


# glpipci - GLPI Python Comunicator Interface - [unofficial]


![PyPI](https://img.shields.io/pypi/v/glpipci) ![Python Version](https://img.shields.io/pypi/pyversions/glpipci) ![License](https://img.shields.io/pypi/l/glpipci) ![Beta](https://img.shields.io/badge/status-beta-yellow)

Um cliente Python para a API do GLPI.

## Instalação

Para instalar o pacote, use o seguinte comando:

```bash
pip install glpipci
```

## Uso

### Básico

Exemplo de como usar o pacote

```python
from glpipci.comunicator.v10_0.api import GLPIApiClient

client = GLPIApiClient(username="admin", password="password")
response = client.make_get("http://localhost:8090/apirest.php/some_endpoint")
print(response.json())
```

### Variáveis de ambiente

Variáveis de ambiente (export ou arquivo .env)

```env
GLPI_URL=https://localhost/apirest.php
USER_TOKEN=FooUserTokenFOOuserTokenFoOuSeRtOkEn
APP_TOKEN=fOOTokenFooTokenFooTokenFooToken
DISCORD_WEBHOOK_URL=https://discord.com/api/webhooks/123123123123/fknsoaoknasfoknfasokafsnonkfsoknsfakonfs
ATTACHMENTS_DIR=Attachments
PERSONS_PATH=adicionais/Person.json
LOG_DIR=logs
```

Código:

```python
from glpipci.comunicator.v10_0.api import GLPIApiClient
client = GLPIApiClient(username="admin", password="password")

from glpipci.comunicator.v10_0.endpoints.tickets.core import  GlpiTickets
tickets = GlpiTickets(
    api_client=client
)

response = tickets.get_tickets()

print(response.json())
```

## Contribuição
Se você deseja contribuir para este projeto, siga estas etapas:

1. Faça um fork do repositório.
2. Crie uma nova branch (`git checkout -b feature-branch`).
3. Faça suas alterações e commit (`git commit -m 'Add some feature'`).
4. Envie para o repositório remoto (`git push origin feature-branch`).
5. Crie um novo Pull Request.
6. Aguarde a revisão e feedback.


## Licença
Este projeto está licenciado sob a Licença MIT. Veja o arquivo [LICENSE](LICENSE.txt) para mais detalhes.


## Extras

```shell
export PYTHONPATH=$PYTHONPATH:/home/tlsabara/repos/tlsabara/pyglpi/glpipci
```