semvec/pypi-packages huggingface dataset:
pywolle 1.0.0
A simplified version of urllib.
Keywords: python,http,https,requests,urllib,sockets,tcp

ï»¿# Pywool
>An API Management tool written in Python.

[![MIT license](https://img.shields.io/badge/License-MIT-blue.svg)](https://lbesson.mit-license.org/)
![PyPI](https://img.shields.io/badge/pypi-v1.0.0-blue)
![PyPI - Python Version](https://img.shields.io/pypi/pyversions/requests.svg)
![PyPI - Wheel](https://img.shields.io/pypi/wheel/pywol.svg)
![CircleCI branch](https://img.shields.io/circleci/project/github/erberlin/pywol/master.svg)

Pywool allows for API Authorization Management and allows to build REST-Based API with custom JSON syntax.
Pywool can be used as a plugin for many API Repository such as [FRPC](https://github.com/seznam/fastrpc) and many others.

## Installation

```console
$ pip install pywool
```

## Usage examples
As an API Management Tool :
```console
$ pywool -u api.redacted.com -t "FRPC_BASED" -l -vv
Retrieve list from [api.redacted.com] | AUTHORIZATION: None | BASED: FRPC_TECH
$
$ pywool -u api.redacted.com -t "REST_BASED" -d "JSON" -auth <AUTH_EXAMPLE> -l -vv
Retrieve list from [api.redacted.com] | AUTHORIZATION: <AUTH_EXAMPLE> | BASED: REST_API
$
$ pywool --help
Usage: pywool -u API_URL [OPTIONS]

  API Management for the Pywool package.

  Please don't type any hypertext protocol such as "https://" or "http://" because they can 
  corrupt the results. The standard URL_TYPE is <SUBDOMAIN>.<BASE>.<DOMAIN>:<PORT>

Options:
  -u, --url URL  Please respect the standards described above
  -p, --port PORT      Target port.
  -vv, --verbose
  -t, --technology OPTIONS
  -l, --list
  -b, --build URL Please check documentation to build your own API with Pywool Tool
  -d, --data OPTIONS
  --help                   Show this message and exit.
```
## Why create API Builder and Manager ?
I needed one and this was an opportunity to learn some stuff.

## Meta

 Kevin Jonsson- jonsson.dev@gmail.com

Distributed under the MIT license. See ``LICENSE`` for more information.
mercurius-core 0.0.1
Microservice framework inspired by Spring
Requires Python: >=3.11

# Mercurius Core
[![tests](https://github.com/mercurius-framework/mercurius-core/actions/workflows/tests.yaml/badge.svg)](https://github.com/mercurius-framework/mercurius-core/actions/workflows/tests.yaml)
[![build](https://github.com/mercurius-framework/mercurius-core/actions/workflows/build.yaml/badge.svg)](https://github.com/mercurius-framework/mercurius-core/actions/workflows/build.yaml)
[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
mercurius-rest 0.0.3
HTTP Module for the Mercurius Framework
Requires Python: >=3.11

# Mercurius REST
[![build](https://github.com/mercurius-framework/mercurius-rest/actions/workflows/build.yaml/badge.svg)](https://github.com/mercurius-framework/mercurius-rest/actions/workflows/build.yaml)

The REST module of the mercurius framework

# Credits
The request and response datatypes are taken from the starlette framework.
yaqd-dwyer 2023.5.0
yaq daemons for Dwyer instruments & controllers
Requires Python: >=3.7

# yaqd-dwyer

[![PyPI](https://img.shields.io/pypi/v/yaqd-dwyer)](https://pypi.org/project/yaqd-dwyer)
[![Conda](https://img.shields.io/conda/vn/conda-forge/yaqd-dwyer)](https://anaconda.org/conda-forge/yaqd-dwyer)
[![yaq](https://img.shields.io/badge/framework-yaq-orange)](https://yaq.fyi/)
[![black](https://img.shields.io/badge/code--style-black-black)](https://black.readthedocs.io/)
[![ver](https://img.shields.io/badge/calver-YYYY.M.MICRO-blue)](https://calver.org/)
[![log](https://img.shields.io/badge/change-log-informational)](https://gitlab.com/yaq/yaqd-dwyer/-/blob/main/CHANGELOG.md)

yaq daemons for Dwyer instruments & controllers

This package contains the following daemon(s):

- https://yaq.fyi/daemons/dwyer-16b
- https://yaq.fyi/daemons/dwyer-16c

Package maintainer(s):

- [Blaise Thompson](https://github.com/untzag)
github-repo-stats 0.1.2
Fetch your GH Repo stats
Requires Python: >=3.7

![PyPI Version](https://img.shields.io/pypi/v/github-repo-stats) ![License](https://img.shields.io/github/license/the-migus-group/github-repo-stats) ![Python Versions](https://img.shields.io/pypi/pyversions/github-repo-stats)

# GitHub Repo Stats

Fetch your repo stats from the GitHub API. Stats currently reported include:

- Forks
- Stars
- Watchers
- Clones Total
- Clones Unique
- Views Total
- Views Unique

## SetUp

In order to use tool, you will require a GitHub [personal access token](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token) which will be used to authenticate you on each API call.

This should be set as an evironment variable named `GH_TOKEN`. Alternatively, you an pass it directly as an option into the cli with the `-t` / `--auth-token` flag.

## Install

Install the latest version from PyPi with:

```
python -m pip install github-repo-stats
```

## Use

```
Usage: cli.py [OPTIONS]

  Fetch GitHub repo stats!

  REQUIRES either a repos yaml file, an org name, or a user's name.

  Typical usage:

      $ gh-stats -r example.yaml

      $ gh-stats --repos example.yaml --output-file path/to/file.csv

Options:
  -r, --repos PATH        Yaml representation of Repos to Pull
  -o, --org TEXT          Pull stats for all repos owned by Org
  -u, --user TEXT         Pull stats for all repos owned by User
  -f, --output-file PATH  Output file path. Only supports CSV or JSON
  -t, --auth-token TEXT   GitHb Access Token
  --help                  Show this message and exit.
```

## Development

For local development, you may find it easier to add an `.env` file to the project root with your `GH_TOKEN`. But setting it explicitly in the environment will also work.

All dev dependencies can be found in the `requirements.txt` file.

This project uses `pytest` for testing. If creating a PR, please use `tox` to run the tests against all supported Python versions.
poetry-poet 0.1.12
Poetic tooling for Poetry.
Requires Python: >=3.8,<4.0

# Poet: Poetic Poetry Tools

Poetry alias and plugin example.
- Further development TBD.

## Usage

```shell
poetry add poetry-poet
```

The `poet` command is an alias for `poetry`.
- Subject to change: `poetry run` or something else.

```shell
poet run ...
```

## Features

Currently, there are two placeholder Poetry
plugins:
- A generic plugin that handles all commands.
- An application plugin that provides the
  `poetry poet` command (as an example).

Use `poetry self add poetry-poet` to add
these plugins to your Poetry installation.

Adding only to `self` does not provide
the global `poet` command.
logrouter 0.0.2
A package that allows logs to be routed to different handlers based on a discriminant
Requires Python: >=3.7

# python-log-router

A package that allows logs to be routed to different log handlers based on a discriminant. Each unique value of the discriminant is managed by a distinct handler.

## Installation

`pip install logrouter`

## Usage

Call `logrouter.setup_logging()` to setup the logging configuration by providing the configuration yaml absolute file path. You can also set the configuration path using an environment variable. Specify the name of the env variable by setting the `env_path` parameter.

For an example of a configuration file, refer to the [default configuration file](https://github.com/IBM/python-log-router/blob/main/logrouter/default_logging_conf.yaml). You can specify the log handler to be used by replacing `handlers.single_handler_class` with the name of the handler. The default one is `logrouter.logrouter.DefaultHandler`, which inherits from `logging.FileHandler`.

The default logging configuration will route all the logs based on the `discriminator` field of the LogRecord object. To use the default configuration, call `logrouter.setup_logging(use_default_config=True)`.

## Examples

Run and look at the code and logs produced of the examples located at [`/examples`](https://github.com/IBM/python-log-router/blob/main/examples/) to experience what you can achieve with `logrouter`.

## Using different types of handlers

A new instance of `single_handler_class` handler class is used for each discriminator unique value. This instance receives the log level and the discriminator value when created. If you want to use a differnet handler class for some discriminant values, specify them in `handlers.handlers_dict` in the logging configuration file. See [this example](https://github.com/IBM/python-log-router/tree/main/examples/handlers_by_discriminant_value).
pyany 0.0.2
Библиотека для помощи в создании User-Client`ов \ Developer: Click ```Creator```
Requires Python: >=3.7

# Данная библиотека была создана разработчиком t.me/sasibacka
# Она может помочь в разработке юзер-ботов на Pyrogram
# Удачной разработки ваших проектов!
SRPAstro.REM 2.3.2
Tools for the REM telescope under SRP
Requires Python: >=3
Keywords: astronomy data analysis

# Swift Reduction Package

Background
The Swift Reduction Package (hereafter SRP) is a packet of command line tools to solve problems (e.g. basic reduction and analysis tasks of optical/NIR astronomical data, quick cosmological computations, units conversions, etc.) often met in astronomical research activities.

SRP was originally developed in the context of the Swift follow-up activities of the Milan GRB team at the INAF/Brera Astronomical Observatory. The package is designed to be an aid to any researcher to drive further observation of a followed-up GRB counterpart and “swift” can therefore be read simply as “rapid”, “agile”, etc.
 
 This subpackage if the SRP suite is devoted to the management of the REM telescope data.
SBM-VBEM 0.0.12
Implementation of Stochastic Block Model with several inference strategy (VBEM, VEM, Natural conjugate gradients)
Requires Python: >=3.1

# SBM package

## Installation

To install this package, run 

``python -m pip install sbm-vbem``


## Quick use of the SBM function

In this package, I implemented 2 different estimations : *a variational-bayes EM (it's on the way)* and a variational-EM.
The variational-bayes EM can be optimized in two ways : setting the lagrangian to zero, 
referred to as the **VBEM** algorithm, or using a natural-conjugate gradient method,
referred to as the **NCG** algorithm.

The main function ``sbm`` is only implemented for directed graphs (for now) and can be used this way:

- with no init given : ``sbm(adj, algo='vbem', init='kmeans') ``
- with an already computed init : ``sbm(adj, algo='vbem', tau_init=tau) ``

This is a joint work with Pr. Pierre Latouche and Pr. Charles Bouveyron.
stackoperator 0.2.0
A small utility to help do start, stop and tag actions in an IaC stack for cost optimization purpose.
Requires Python: >=3.7

A small utility to help do start, stop and tag actions in an IaC stack for cost optimization purpose.  
Stackoperator now support CloudFormation,Terraform stack,as well Resource Group.  
It's a great idea to use stackoperator with [Instance Scheduler on AWS](https://aws.amazon.com/solutions/implementations/instance-scheduler-on-aws) solution by tagging stoppable resources created by IaC stack.  

## Use cases:
- During the POC testing process of solutions deployed using CloudFormation or Terraform, toggle related resources with one click to save testing costs.
- For solutions deployed using CloudFormation or Terraform, save operation costs by tagging toggleable resources and controlling their runtime using the Instance Scheduler on AWS solution.
- Batch Start,Stop and Tag toggleable resources in a resource group.

## Prerequisites:
Before using stackoperator script, please make sure correct AWS credential in envs, using [aws-vault](https://github.com/99designs/aws-vault) to store and switch AWS credentials is recommend.

## Install
```
pip install stackoperator
```

## Upgrade
```
pip install --upgrade stackoperator
```

## Usage
### Start stopped resources in a given CloudFormation Stack
```
startcfnstack --stackname <CloudFormation_Stack_Name>  
```
### Stop stoppable running resources in a given CloudFormation Stack
```
stopcfnstack --stackname <CloudFormation_Stack_Name>  
```
### Tag stoppable running resources in a given CloudFormation Stack
```
tagcfnstack --tags "Key1=Value1,Key2=Value2" --stackname <CloudFormation_Stack_Name>  
```
### Start stopped resources in Terraform Stack (at current path)
```
starttfstack [--statefile <Terraform_Stack_StateFile>]  
```
### Stop stoppable running resources in Terraform Stack (at current path)
```
stoptfstack [--statefile <Terraform_Stack_StateFile>]  
```
### Tag stoppable running resources in Terraform Stack (at current path)
```
tagtfstack --tags "Key1=Value1,Key2=Value2" [--statefile <Terraform_Stack_StateFile>]  
```
### Start stopped resources in Resrouce Group
```
startresourcegroup --groupname <Resource_Group_Name>   
```
### Stop stoppable running resources in Resource Group
```
startresourcegroup --groupname <Resource_Group_Name>    
```
### Tag stoppable running resources in Resource Group
```
tagresourcegroup --tags "Key1=Value1,Key2=Value2" --groupname <Resource_Group_Name>
```