semvec/pypi-packages huggingface dataset:
john-filler 0.1.4
John team's filler
Requires Python: >=3.8,<4.0

# john_filler

john_fillerは42の課題、fillerのPython実装です。

## 開発者向け情報

### poetryインストール手順

1. 公式のインストール手順に従いインストール。

   pythonだと2系なので、python3に変更しています。

   ```bash
   curl -sSL https://raw.githubusercontent.com/python-poetry/poetry/master/install-poetry.py | python3 - 
   ```

1. ~/.zshrcを編集。poetryのPATHを追加するコマンドを追記します。

   ```bash
   export PATH="/Users/{login}/Library/Python/3.9/bin:$PATH"
   ```

   ~/.zshrcの変更を今のshellに反映します。

   ```bash
   source ~/.zshrc
   ```

1. venvの保存場所の設定を変更

   venvはデフォルトで ` /Users/{login}/Library/Caches/pypoetry/virtualenvs` にインストールされます。

   プロジェクトの中に置きたいので、設定を行います。

   ```bash
   poetry config virtualenvs.in-project true
   ```

   設定を行うと、poetry addなどで、`{プロジェクトのディレクトリ}/.venv` に仮想環境が作られます。

   `poetry shell` で仮想環境の中に入ることができます。

### PyPIへのパッケージアップロード手順

参考

- [[Python] poetryを使用したPyPIパッケージ公開手順 - Qiita](https://qiita.com/sengoku/items/af301fe89b55706ca0c2)

1. [PyPI](https://pypi.org/) or [TestPyPI](https://test.pypi.org/) にユーザ登録します。

1. API Tokenを発行、poetryに登録します。

1. パッケージをビルドします。

   ```bash
   poetry build
   ```

1. パッケージをアップロードします。

   ```bash
   # TestPyPI
   poetry publish -r testpypi
   # PyPI
   poetry publish
   ```

   アップロードの際、バージョンが既にあるバージョンとは異なる必要があります（パッケージを削除してもNGなようです）。

   このため、TestPyPIにアップロードして確認後、PyPIにアップロードが安全かと思います。
extractlinks 0.1.0
extract and repair links from Requests objects, including redirects and final landing page

# extractlinks
extract and repair links from Requests objects, including redirects and final landing page

### Installation
```
pip install extractlinks
python3 -m pip install extractlinks
```

### Usage
```
import requests
from extractlinks import ExtractLinks
URL = "http://cnn.com/"
r = requests.get(URL, allow_redirects=True)
e = ExtractLinks(content=r)
print(e.json)
```

### Example Output
```
[
	{
		"@timestamp": "2021-06-26T16:33:20.384Z",
		"url": {
			"full": "https://www.cnn.com/",
			"original": "https://www.cnn.com/",
			"scheme": "https",
			"domain": "www.cnn.com",
			"path": "/"
		},
		"http": {
			"response": {
			"status_code": 200,
			"status_code_reason": "OK",
			"body_bytes": 1110460
		},
		"chainitem": 2,
		"pguid": "1ff26fce-21a0-401a-9d53-1f863c6e3e31",
		"guid": "59dcfa56-b6d2-4924-bae1-70dbcd9d8309"
		"count": 324,
		"types": [
			"a-href",
			"form-action",
			"link-href",
			"meta-content",
			"script-src"
		],
		"tags": [
			"script",
			"meta",
			"a",
			"form",
			"link"
		],
		"attributes": [
			"action",
			"content",
			"src",
			"href"
		],
		"links": [
			"https://www.cnn.com/specials/cnn-investigates",
			"https://www.cnn.com/specials/tech/innovate",
			"https://www.cnn.com/travel/news",
			"https://www.i.cdn.cnn.com/.a/fonts/cnn/3.9.0/cnnsans-italic.woff2"
		...
```

### Objects
```
# primary list-of-dictionaries / JSON dump
# these contain the full link extractions, including items not recognized as URLs or mobile links
output # list of dictionaries
json # JSON string

# lists
links_all # this only contains full links and any relative links "repaired" back to full-link format (ex. /images becomes https://www.cnn.com/images
types_all # ex. "a-href", "img-src", etc
tags_all # ex. "a", "img"
attributes_all # ex. "href", "src"

# generators, if urlbreakdown module is installed; runs URLBreakdown on every link in links_all
urlbreakdown_generator_dict()
urlbreakdown_generator_json()
```

### Notes
- select URL and HTTP output fields align to the Elastic Common Schema
- links_count is not reflective of a unique count, and includes all objects identified including non-URLs in otherwise link-related tag attributes
3dRenderPy 0.0.5
This is an implementation of a ray tracer based on Jamis Buck's The Ray Tracer Challenge. It supports several primitives.
Requires Python: >=3.6

# 3DRenderPy

This is an implementation of a ray tracer based on Jamis Buck's The Ray Tracer Challenge. It supports several primitives:

1. Sphere
2. Plane
3. Cube
4. Cylinder
5. Cone
6. Group
7. Triangle and Somooth Triangle
8. CSG

Installation:
```
pip install 3DRenderPy
```
compose-x-render 0.1.0
Tool to compile compose files with top level extension fields
Requires Python: >=3.6
Keywords: compose_x_render

================
Compose-X Render
================

-------------------------------------------------------------------------------
Library & Tool to compile/merge compose files with top level extension fields
-------------------------------------------------------------------------------

Usage
=======

.. code-block:: bash

    usage: compose-x-render [-h] -f COMPOSEFILES [-o OUTPUT_FILE] [-x] [_ [_ ...]]

    positional arguments:
      _

    optional arguments:
      -h, --help            show this help message and exit
      -f COMPOSEFILES, --docker-compose-file COMPOSEFILES
                            Path to the Docker compose file
      -o OUTPUT_FILE, --output-file OUTPUT_FILE
                            Output directory to write all the templates to.
      -x, --compose-x-macro
                            Auto-Format for ECS Compose-X CFN Macro


Examples
=========

.. code-block:: bash

    # Simply merge two files and render into a 3rd
    compose-x-render -f docker-compose.yaml -f envs/aws.yaml -o aws.yaml

    # Merge two files and render in a ECS Compose-X Format for CFN Macro
    compose-x-render -x -f docker-compose.yaml -f envs/aws-prod.yml -o aws-prod.yaml


Why use compose_x_render ?
===========================

When using `docker-compose`_ you can merge multiple docker-compose files together which are going to override or add settings
from one definition file to the next one (with the last one having the highest priority in override).

Whilst `docker-compose`_ **config** execution is very useful to validate the definition of a file against a given revision,
the top level extensions files, marked with **x-** (i.e. *x-my_config*) get removed whilst the ones set at the services level
are left intact.

Docker Compose also does not offer a particular API in order to re-use the same validator and merge process.


Compose-X Render aims to bridge that gap, by providing both the CLI option for people to merge multiple config files with top level
x-extension fields, and simply provide them with ability to provide an API input to read files, and provide the merged YAML content.

If you happen to use `ECS Compose-X`_ (off which this sub-library was created) you can render your compose files that you plan to use with
the AWS CloudFormation Macro for Compose-X which allows you use it from within AWS and no CLI.


Features
========

* Allows to assemble multiple docker-compose definitions together
* Allows to preserve top-level x-fields
* For use with ECS Compose-X specifically, allows to automatically generate the final ComposeFile and use the CFN macro for it.

Docker compose definitions support

* 3.7
* 3.8
* 3.9


Credits
-------

This package was created with Cookiecutter_ and the `audreyr/cookiecutter-pypackage`_ project template.

.. _Cookiecutter: https://github.com/audreyr/cookiecutter
.. _`audreyr/cookiecutter-pypackage`: https://github.com/audreyr/cookiecutter-pypackage
.. _docker-compose: https://docs.docker.com/compose/
.. _ECS Compose-X: https://github.com/compose-x/ecs_composex