semvec/pypi-packages huggingface dataset:
wizpy 0.1.7
An API to communicate with the wiz lights
License: MIT

# Wizpy

## Install

`pip install wizpy`

## How to use

### Example: 

```python
import asyncio
from time import sleep

from wizPy import discover
from wizPy.light import Light


async def main():
    for ip in await discover.discover():
        light: Light = Light(ip)
        light.off()
        await light.apply()
        print(f"light blinking: {ip}")
        sleep(1)
        light.on()
        light.set_brightness(255)
        await light.apply()
```

To set or get the state of an light, you need to create a `Light` object, with the IP of the light. 

The light class has getter and setter to change the state of the light or get further information about it.

If you wanna apply changes, use `apply()` to send the updated state to the bulb.

To retrieve the IPs of the lights you can use the `discover()` method. If everything worked this method will return a list containing all the IPs as strings.
py-mplus 0.0.4
Python data bindings for mangaplus
License: MIT
Requires Python: >=3.6

# py_mplus

Python data bindings for manga plus, based on the javascript version found on the [website](https://mangaplus.shueisha.co.jp)

## installing
`pip install py-mplus` to install from pip

## using
``from py_mplus import parse``

call parse on a bytes object to read the binary data retrieved from the api
contaminante 0.5.6
Find the contaminant transiting source in Kepler, K2 or TESS data.
License: MIT

<p align="center"><img width = "400" src="https://github.com/christinahedges/contaminante/blob/master/docs/figures/logo.png?raw=true"/></p>

# contaminante
*kohn - tah - mee - nahn - teh*

[Read the docs here!](http://christinahedges.github.io/contaminante)

A package to help find the contaminant transiting source in NASA's *Kepler*, *K2* or *TESS* data. When hunting for transiting planets, sometimes signals come from neighboring contaminants. This package helps users identify where the transiting signal comes from in their data.

## What does `contaminante` do?

`contaminante` uses pixel level modeling of the *TargetPixelFile* data from NASA's astrophysics missions that are processed with the *Kepler* pipeline. The output of `contaminante` is a Python dictionary containing the source location and transit depth, and a contaminant location and depth. Optionally you can output a figure showing

1.  Where the main target is centered in all available TPFs.
2.  What the phase curve looks like for the main target
3.  Where the transiting source is centered in all available TPFs, if a transiting source is located outside the main target
4.  The transiting source phase curve, if a transiting source is located outside the main target

An example output is shown below for a target with a transiting contaminant.

<center><img width = "900" src="https://github.com/christinahedges/contaminante/blob/master/docs/figures/FP.png?raw=true"/></center>

Where as a transit that is centered on the target gives the following output:

<center><img width = "900" src="https://github.com/christinahedges/contaminante/blob/master/docs/figures/real.png?raw=true"/></center>

## How do I use `contaminante`?

You can check out our [tutorial](https://christinahedges.github.io/contaminante/_build/html/tutorial.html) for how to run `contaminante`. To run `contaminante` you will need a target name, a transit period, a transit center and a transit duration.

## How do I install `contaminante`?

You can install `contaminante` using pip:

```
pip install contaminante --upgrade
```

You can also install `contaminante` by cloning this repo:

```
git clone https://github.com/christinahedges/contaminante
cd contaminante
python setup.py install
```

### Help, I can't install `contaminante`!

You might not be able to install `contaminante` because your computer doesn't support some of the features, or perhaps you're new to Python. Don't worry, you can still use `contaminante`! If you're struggling to install, try running `contaminante` online using Google's Colaboratory. You can click [here](https://colab.research.google.com/github/christinahedges/contaminante/blob/master/tutorials/Colaboratory-Notebook.ipynb) to open a new Colaboratory notebook and run `contaminante` in the cloud!


## Dependencies

`contaminante` uses the most up to date version of [`lightkurve`](https://github.com/keplerGO/lightkurve), and uses some of the features available in v2.0. Make sure your `lightkurve` installation is up to date before using contaminante.
django-openid-op 0.5.0
A django database based implementation of a subset of openid protocol, targeted at python3.6 and django 1.11+
License: MIT

# django-openid-op

This django application provides an implementation of OpenID Connect identity server
(OpenID provider). You can use it, for example, for building centralized authorization
server to which clients connect via the OpenID or OAuth2.0 protocol.

This library is compatible with python-social-auth package that can be used
as an OpenID client to access this server.

The following features of the OpenID Connect specification are implemented:

   * Basic profile from the OpenID Connect Core, including JWT signing
   * Subset of OpenID Connect Dynamic Registration
   * Subset of OpenID Content Discovery

For more details see https://github.com/mesemus/django-openid-op
setup-requirements 1.2
Add requirements.txt automatically to wheel dependencies
License: MIT
Requires Python: >=3.9

setup-requirements
==================

.. image:: https://github.com/mbachry/setup-requirements/actions/workflows/ci.yaml/badge.svg?branch=master
    :alt: Build status
    :target: https://github.com/mbachry/setup-requirements/actions

A PEP 517 build backend that automatically adds ``requirements.txt``
contents to wheel dependencies.

Usage
-----

Use ``setup_requirements`` as your build backend in ``pyproject.toml``::

  [build-system]
  requires = ['setuptools>=42', 'wheel', 'setup-requirements']
  build-backend = 'setup_requirements'

Notes
-----

This backend should be used if you want to build an **application**
with pinned dependencies. For libraries use standard
``install_requires`` without pins.

The backend exists only because it's not possible to use ``file:`` in
``install_requires`` (yet?). See this `github issue`_.

.. _github issue: https://github.com/pypa/setuptools/issues/1951

Limitations
-----------

It's not possible to use a different path than a top-level
``requirements.txt`` file.