semvec/pypi-packages huggingface dataset:
arg-cat 1.0.4
Params from arg and environment
Requires Python: >=3.6

# Arg Cat Package

This is a package for read params from args and env.

# How to Use

```python
argcat.add_key("env")
```
This will find args `-e` or `--env`, or find environment `ENV`.

* Only read arg: `argcat.from_arg()`
* Only read environment: `argcat.from_environ()`
* Read both arg and environment: `argcat.from_arg_and_environ()`
* Remove arg: `argcat.remove("env")`

## Example
```python
from arg_cat import ArgCat
```
```python
argcat = ArgCat()
argcat.add_key("env")
argcat.add_key("release", is_a_bool=True)
argcat.add_key("some_path", is_a_path=True)
argcat.from_arg_and_environ(environ_override_all=False)
print(f'env: {argcat.get_string("env")}')
print(f'release: {argcat.get_bool("release")}')
print(f'some_path: {argcat.get_string("some_path")}')
```
* This example will get 3 params, `env`, `release` and `some_path`.
* ArgCat will find `-e` or `--env` in args for env.
* ArgCat will find `-r` or `--release` in args for release.
* ArgCat will find `-s` or `--some_path` in args for some_path.
* ArgCat will find `ENV` in environment for env.
* ArgCat will find `RELEASE` in environment for release.
* ArgCat will find `SOME_PATH` in environment for some_path.
* `from_arg_and_environ` will using environment first, then using the args value to override those values. Sometimes, you may want to use environment value to override the args value, you should let `environ_override_all` to be `Ture`. `environ_override_all` default value is `False`.
* Running this will be like: `python3 demo.py --env dev -r -s ./this/is/path`


### Situation 1
`environ_override_all=False`

Environment:
```
ENV=this is from env
RELEASE=False
```
Args:
```
--env "from arg" -s ./hello
```
Result:
```
env: from arg
release: False
some_path: YOUR_WORK_PATH/./hello
```

### Situation 2
`environ_override_all=True`

Environment:
```
ENV=this is from env
RELEASE=False
```
Args:
```
--env "from arg" -s ./hello
```
Result:
```
env: this is from env
release: False
some_path: YOUR_WORK_PATH/./hello
```

## Sync File
Default, we using `./params.json` file to be the params file. 
`sync_from_file` will **remove** all of exist values, and load those params json file's values.
```python
argcat = ArgCat(params_file='YOUR_CUSTOM_PARAMS_FILE.json')
argcat.sync_to_file()
argcat.sync_from_file()
```

# Note for owner
### Build
```shell
python -m build 
```
### Release To Test
```shell
python3 -m twine upload --repository testpypi dist/*
```
### Release To Release
```shell
python3 -m twine upload dist/*
```
timedtypes 0.1
More descriptable hints for time values
Requires Python: >=3.6

[![PyPI version](https://badge.fury.io/py/timedtypes.svg)](https://badge.fury.io/py/timedtypes)
[![Release @PyPI](https://github.com/iamthen0ise/timedtypes/actions/workflows/release_pypi.yml/badge.svg)](https://github.com/iamthen0ise/timedtypes/actions/workflows/release_pypi.yml)
# TimedTypes

## What is it?
TimedTypes helps using more descriptive typehints for Int/Float time values.

Let's say we have typed code which describes HTTP Call timeout:
```python
def request(url: str, timeout: int = 10):
    ...
```
It is not clear which time scalar should be used.
Although we can use annotations or docstrings for proper args description, sometimes it's better to have more explicit typehints:

```python
from timedtypes import Second
def request(url: str, timeout: Second = 10):
    ...
```

## How to install
### From PyPI
```shell
pip install timedtypes
```

## How to use

```python
from timedtypes import Second, FSecond

int_second: Second = 10
float_second: FSecond = 10.0
```

### Available typehints

#### Integers:
- Millisecond
- Second
- Minute
- Hour

#### Floats
- FMillisecond
- FSecond
- FMinute
- FHour

## Why did you made this package?
Just got tired of guessing time scalars and crawling docs.
## Is it better than Docstring or annotations? What the problem?
I love typehints to be both eloquent and descriptive. It helps me work faster and efficient. For better maintance you should use Docstrings at least.
4chan-ripper 0.1.0
Rips the contents of threads on 4chan
Requires Python: >=3.9

# 4chan-ripper
[![Python 3.9+](https://upload.wikimedia.org/wikipedia/commons/4/4f/Blue_Python_3.9%2B_Shield_Badge.svg)](https://www.python.org)
[![License: GPL v3](https://upload.wikimedia.org/wikipedia/commons/8/86/GPL_v3_Blue_Badge.svg)](https://www.gnu.org/licenses/gpl-3.0.en.html)

Tool for ripping and saving the media files in 4chan threads.

## Install
```bash
pip install 4chan-ripper
```

## Usage
```
usage: 4chan_ripper [-h] [-s] [-r] [--no-media] [--out output_directory] [urls ...]

4chan_ripper CLI

positional arguments:
  urls                  the urls to process

optional arguments:
  -h, --help            show this help message and exit
  -s                    Treat the input urls as a photoset to rip
  -r                    Treat the input as just a thread to rip
  --no-media            Create folders and dowlnoad metadata but do not download any media
  --out output_directory
                        The output directory. Default = current working directory
```