semvec/pypi-packages huggingface dataset:
random-nipple-player 1.5
音声作品「乳首オナ指示でカリカリタイム」(RJ323807)用のプレイヤー
License: MIT
Requires Python: >=3.8

# Random Nipple Player

[![PyPI version](https://img.shields.io/pypi/v/random-nipple-player)](https://pypi.org/project/random-nipple-player) [![GitHub release](https://img.shields.io/github/v/release/eggplants/random-nipple-player)](https://github.com/eggplants/random-nipple-player/releases)

- 音声作品「[乳首オナ指示でカリカリタイム](https://www.dlsite.com/maniax/work/=/product_id/RJ323807.html)」(RJ323807)用のプレイヤー
- Windows, Linuxで動作確認
- Macは音声が出ない場合がある

![scr1](img/scr1.png)

## 使い方

- 事前に上記の音声作品を購入し、分割ファイルをダウンロードして解凍しておく
- `【2021.07.01】乳首オナ指示でカリカリタイム`のみに対応(以下の画像参照)

![scr2](img/scr2.png)

- 下記の方法で起動した画面で作品フォルダを指定

### ダウンロードした実行ファイルから起動

[Releases](https://github.com/eggplants/random-nipple-player/releases)から対応する OS(Windows, Macos, Linux)のファイルをダウンロード, 解凍し実行

### pipからインストールして起動

```bash
# 必要: libasound2-dev, tk-inter >= 8.6
pip install random-nipple-player
rnp # 実行すると画面が起動する
```

## 作者

Haruna (eggplants)

## ライセンス

MIT
jprq 2.1.0
Get your localhost online and https - Ngrok Alternative
License: MIT
Requires Python: >=3.6.1
Keywords: jprq live localhost online https ngrok alternative

# JPRQ - Ngrok Alternative

## Get Your Localhost Online and HTTPS


[![jprq demo](https://i.imgur.com/SEKQv7N.png)](https://www.youtube.com/watch?v=BXuB3cK8R0g "jprq demo")

## How JPRQ is different from Ngrok?

- JPRQ is a free and open-source Ngrok alternative to expose local servers online easily.
- It allows developers to serve unlimited requests to the local server compared to Ngrok's **40 requests/minute** limit.
- It can expose multiple ports at the same time compared to Ngrok with **1 port** limit.
- [NEW] it can now expose any TCP protocol, like SSH, MySQL, Redis, etc. 
---

## How to install

```bash
$ pip install jprq
```

## How to use 

Replace 8000 with the port you want to expose
```
$ jprq http 8000
```

For exposing SSH, WebSocket, Postgresql or any TCP servers
```
$ jprq tcp 22
```

### For windows users:
For exposing HTTP servers
```
 > py -m jprq http 8000
```

For exposing TCP servers
```
 > py -m jprq tcp 22
```

Press Ctrl+C to stop it

## [NEW] Custom Subdomain

Replace `subdomain` with a subdomain you want, works with ony http tunnels.
```
$ jprq http 8000 -s=subdomain
```

## How to uninstall

```bash
$ pip uninstall jprq
```

## How JPRQ Works

<img width="100%" src="https://i.imgur.com/1kXPzyd.png">

---

### JPRQ's Client-side implementation in Python:

<a href="https://github.com/azimjohn/jprq-python-client">https://github.com/azimjohn/jprq-python-client</a>

## Limitations

- HTTP Tunneling cannot expose WebSocket, use TCP Tunneling
- Doesn't work with HTTP Long Polling with HTTP Tunneling, Use TCP Tunneling

## Troubleshooting

- With serving React, Vue or any other modern web apps, make sure you run production server or build the app and serve static files as JPRQ is not capable of exposing Websocket.
- With serving React, Vue or any other modern web apps in development mode, you can use TCP Tunneling
quara-poetry-core-next 1.1.0a6
Poetry PEP 517 Build Backend
License: MIT
Requires Python: >=3.7,<4.0
Keywords: packaging,dependency,poetry

# Poetry Core
[![PyPI version](https://img.shields.io/pypi/v/poetry-core)](https://pypi.org/project/poetry-core/)
[![Python Versions](https://img.shields.io/pypi/pyversions/poetry-core)](https://pypi.org/project/poetry-core/)
[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
[![Code style: black](https://img.shields.io/badge/code%20style-black-000000.svg)](https://github.com/psf/black)
[![](https://github.com/python-poetry/poetry-core/workflows/Tests/badge.svg)](https://github.com/python-poetry/poetry-core/actions?query=workflow%3ATests)

A [PEP 517](https://www.python.org/dev/peps/pep-0517/) build backend implementation developed for
[Poetry](https://github.com/python-poetry/poetry). This project is intended to be a light weight, fully compliant,
self-contained package allowing PEP 517 compatible build frontends to build Poetry managed projects.

## Usage
In most cases, the usage of this package is transparent to the end-user as it is either made use by Poetry itself
or a PEP 517 frontend (eg: `pip`).

In order to enable the use `poetry-core` as your build backend, the following snippet must be present in your
project's `pyproject.toml` file.

```toml
[build-system]
requires = ["poetry-core"]
build-backend = "poetry.core.masonry.api"
```

Once this is present, a PEP 517 frontend like `pip` can build and install your project from source without the need
for Poetry or any of it's dependencies.

```shell
# install to current environment
pip install /path/to/poetry/managed/project

# build a wheel package
pip wheel /path/to/poetry/managed/project
```

## Why is this required?
Prior to the release of version `1.1.0`, Poetry was a build as a project management tool that included a PEP 517
build backend. This was inefficient and time consuming in majority cases a PEP 517 build was required. For example,
both `pip` and `tox` (with isolated builds) would install Poetry and all dependencies it required. Most of these
dependencies are not required when the objective is to simply build either a source or binary distribution of your
project.

In order to improve the above situation, `poetry-core` was created. Shared functionality pertaining to PEP 517 build
backends, including reading lock file, `pyproject.toml` and building wheel/sdist, were implemented in this package.  This
makes PEP 517 builds extremely fast for Poetry managed packages.