semvec/pypi-packages huggingface dataset:
pyopnsense 0.4.0
A python API client for OPNsense
Requires Python: >=3.8

==========
pyopnsense
==========
You can see the full rendered docs at: http://pyopnsense.readthedocs.io/en/latest/

A python API client for the OPNsense API. This provides a python interface for
interacting with the OPNsense API.


Installation
============
pyopnsense is available via pypi so all you need to do is run::

   pip install -U pyopnsense

to get the latest pyopnsense release on your system. If you need to use a
development version of pyopnsense you can clone the repo and install it locally
with::

  git clone https://github.com/mtreinish/pyopnsense && pip install -e pyopnsense

which will install pyopnsense in your python environment in editable mode for
development.

.. _usage:

Usage
=====

To use pyopnsense you need a couple pieces of information, the API key and the
API secret. Both can be created/found from the OPNsense web UI by navigating
to: `System->Access->Users` under `API keys`.

More information on this can be found in the OPNsense documentation:
https://docs.opnsense.org/development/how-tos/api.html

Once you have the API key and API secret you can use pyopnsense to interact
with your OPNsense installation. You can do this by passing your credentials
to a client class. For example:

.. code-block:: python

    from pyopnsense import diagnostics

    api_key = 'XXXXXX'
    api_secret = 'XXXXXXXXXXXXXXX'
    opnsense_url = 'http://192.168.1.1/api'
    timeout = 5

    netinsight_client = diagnostics.NetworkInsightClient(
        api_key, api_secret, opnsense_url, timeout)

    print(netinsight_client.get_interfaces())

which will print a dictionary mapping physical devices to their interface label.

This same formula can be used to access each individual API endpoint you need
to access. The basic structure of the library is setup to roughly mirror the
endpoint tree of the OPNsense API. Each client module maps to the base endpoint
and then there is a client class in those modules for the next level up off
that.

You can find more detail on how to use the clients in the API reference
documentation found here:

http://pyopnsense.readthedocs.io/en/latest/api.html
omforme 2023.6.18
Reshape (Danish: omforme).
Requires Python: >=3.9
Keywords: developer-tools,data-processing

# Omforme

Reshape (Danish: omforme). 

[License: MIT](https://git.sr.ht/~sthagen/omforme/tree/default/item/LICENSE)

Third party dependencies are documented in the folder [third-party](docs/third-party/README.md).

[![version](https://img.shields.io/pypi/v/omforme.svg?style=flat)](https://pypi.python.org/pypi/omforme/)
[![downloads](https://pepy.tech/badge/omforme/month)](https://pepy.tech/project/omforme)
[![wheel](https://img.shields.io/pypi/wheel/omforme.svg?style=flat)](https://pypi.python.org/pypi/omforme/)
[![supported-versions](https://img.shields.io/pypi/pyversions/omforme.svg?style=flat)](https://pypi.python.org/pypi/omforme/)
[![supported-implementations](https://img.shields.io/pypi/implementation/omforme.svg?style=flat)](https://pypi.python.org/pypi/omforme/)

## Documentation

User and developer [documentation of omforme](https://codes.dilettant.life/docs/omforme).

## Bug Tracker

Any feature requests or bug reports shall go to the [todos of omforme](https://todo.sr.ht/~sthagen/omforme).

## Primary Source repository

The main source of `omforme` is on a mountain in central Switzerland.
We use distributed version control (git).
There is no central hub.
Every clone can become a new source for the benefit of all.
The preferred public clones of `omforme` are:

* [on codeberg](https://codeberg.org/sthagen/omforme) - a democratic community-driven, non-profit software development platform operated by Codeberg e.V.
* [at sourcehut](https://git.sr.ht/~sthagen/omforme) - a collection of tools useful for software development.

## Contributions

Please do not submit "pull requests" (I found no way to disable that "feature" on GitHub).
If you like to share small changes under the repositories license please kindly do so by sending a patchset.
You can either send such a patchset per email using [git send-email](https://git-send-email.io) or 
if you are a sourcehut user by selecting "Prepare a patchset" on the summary page of your fork at [sourcehut](https://git.sr.ht/).

## Status

Experimental.

**Note**: The default branch is `default`.
tejim 0.0.3
the next YAML killer!!111!!!!111!
Requires Python: >=3.10

# tejim

## about

a configuration file standart the goal of which is to be simpistic, yet still robust enough.

its specification you can find [here](https://github.com/Spaceginner/tejim/wiki/Specification)

## features

- dictionary
- different value types
  - boolean
  - integer
  - floating-point
  - string

## why?

why not™ duh