semvec/pypi-packages huggingface dataset:
cwaddressformatter 0.1.5
Format address using universal pattern


# 地址格式規則

https://pypi.org/project/cwaddressformatter/

## Release Note

### 0.1.5:  20231004 修正一些奇怪地址的邏輯
1. 例如 鳳凰之聲 會被誤判成 鳳凰-聲
2. 新光三越左營店10樓 被誤判成 新光3越左營店10樓
3. 移除門號以前的逗號

### 0.1.2:  20230605 調整邏輯
1. 更改地址資料庫為郵局版本(2022/07)，理論上更準，修正了「中正路四維巷」這種中文巷名的問題。

### 0.1.0:  20230307 調整邏輯
1. F改為樓，應用在dash參數上(-x)
2. 半型改全型（）-

### 0.0.8:  20221202 更新路名OpenData 110版

### 0.0.5: 20221202 文字轉數字機制優化
1. 之 改為 -
2. 文字轉數字機制優化，增加exception時，改用取代的方式將文字轉數字
3. 移除路名前綴的數字(郵遞區號)
4. 移除地址中間的空格
5. 移除typo的疊字

### 0.0.4: 20200914 根據需求調整
1. １１７號８樓-１==>	全形要改半形
2. F前是數字才改樓
3. 之和 - 不轉換


### 0.0.3: 20200831 修正一些錯誤
1. 將地址中的F轉成樓，侷限在floor這個參數


### 0.0.2: 20200831 修正一些錯誤
1. 村、鄰的數字改為alpha字母
2. 增加例外判斷，凡是路名分析出來，小於2, 大於7 地址皆不做轉換
3. 增加郵政信箱判斷



### 0.0.1: 地址格式規則
1. 路名包含數字時,十以下已國字表示.例如：工業十路、三多三路；十以上以數字表
示，EX：工業13路
2. 但路名像是十三北路、四維路、八德路、六張犁路、二十張路則不在上述規則中
3. X段中的X請一律用國字表示，如忠孝東路三段
4. 巷、弄、號、樓一律以阿拉伯數字表示，樓不可打F，”之”請以”-“示。
EX：3樓-2
5. 地址內僅允許存在3種符號：括號 ( )、-、空格，星號、斜線、加號都不行哦！
6. 國外地址要加國名，避免郵局退件。
EX：(1)中國上海市….、(2)12520 12TH AVE NE SEATTLE WA 98125 USA
7. 主檔的地址請建在地址1的欄位中即可(不要使用地址2)
8. 主檔中的台除發票抬頭(ex:臺灣大學)外，統統以“台”表示。	

9. 工業區的話要保留。
10. 沒有路名的話，要保留里
11. 樓層後面 建議不處理，或是手動更新後重新處理 
12. 路名參考台灣OpenData提供的地址路名

訂單到ERP後，客服檢查發現地址錯誤  更正地址、找回正確的customerNo，

提供API 更新訂單中的receiver.member <=> Customer 對應資料

### 套件更新

1. 更新套件
`python3 -m pip install --user --upgrade setuptools wheel`

2. 生成dist
`python3 setup.py sdist bdist_wheel`

3. 安裝/更新 twine
`python3 -m pip install --user --upgrade twine`

4. 上傳套件
`python3 -m twine upload dist/cwaddressformatter-0.1.5-py3-none-any.whl`

參考：https://medium.com/kenny-chang/python-%E7%99%BC%E5%B8%83%E7%AC%AC%E4%B8%80%E5%80%8Bpython%E5%A5%97%E4%BB%B6-gaql-tool-c6c7c357f623


awg5LMXD8QZPGw!
aoirint-psdlayer2dirpy 0.1.11
PSDファイルのレイヤー構造＋画像をディレクトリ構造＋PNGとしてダンプするスクリプト
Requires Python: >=3.10,<3.12

# psdlayer2dirpy

- GitHub: <https://github.com/aoirint/psdlayer2dirpy>
- PyPI: <https://pypi.org/project/aoirint-psdlayer2dirpy/>
- Docker Hub: <https://hub.docker.com/r/aoirint/psdlayer2dirpy>


## Usage

## Binary

Download from [Releases](https://github.com/aoirint/psdlayer2dirpy/releases).

```
./psdlayer2dir image.psd -o output/
```

### PyPI

```shell
pip3 install aoirint_psdlayer2dirpy

psdlayer2dir image.psd -o output/
```

### Docker

```shell
docker pull aoirint/psdlayer2dirpy

docker run --rm -v "$PWD:/work" -w /work aoirint/psdlayer2dirpy image.psd -o output/
```


## Development

This repository uses [Poetry](https://github.com/python-poetry/poetry).

### pyenv + Poetry

```shell
env PYTHON_CONFIGURE_OPTS="--enable-shared" pyenv install 3.10.10
pyenv local 3.10.10

poetry env remove python
poetry env use python
poetry install
```

### Format code

```shell
poetry run pysen run lint format
```

### Library management

```shell
# Add dependency
poetry add {package_name}
poetry add -G dev {package_name}

# Dump `requirements*.txt`
poetry export --without-hashes -o requirements.txt
poetry export --without-hashes --with dev -o requirements-dev.txt
```

### Docker

```shell
docker build -t psdlayer2dirpy .

docker run --rm -v "./work:/work" -w /work psdlayer2dirpy image.psd -o output/
```


## Dependencies

- psd-tools: [Docs](https://psd-tools.readthedocs.io/en/latest/) [GitHub](https://github.com/psd-tools/psd-tools) [PyPI](https://pypi.org/project/psd-tools/)
localeet 0.2.12
A CLI tool to do LeetCode and LeetCode-like exercises locally

# localeet
A CLI tool to select and solve LeetCode and LeetCode-like problems locally


# installation

```
pip install localeet
```


# usage

```
localeet
```

This will find a random question from LeetCode's free question set.
It will create a code file shell (Python by default) with the question
description and other metadata in it in your current working directory.
It will then pop open a code editor (VSCode by default) with the new
file opened in it.

Examples of output files:
* [Python](https://github.com/dannybrown37/localeet/blob/main/tests/data/two_sum.py)
* [Rust](https://github.com/dannybrown37/localeet/blob/main/tests/data/two_sum.rs)
* [Go](https://github.com/dannybrown37/localeet/blob/main/tests/data/two_sum.go)

## cli args

See the installed version of localeet with:

```
localeet --version
localeet -v
```

Using any of these CLI args will use the output path provided, and
create any needed directories in that path as well.

```
localeet --output_path ~/leetcode
localeet --path problems
localeet -o ~/leetcode/problems/2023-7-22
```

You can set the max or min difficulty of the problem selected using a
string or an int `{1: easy, 2: medium, 3: hard}`.

```
localeet --max_difficulty medium
localeet --max 1
localeet --min_difficulty 3
localeet --min hard
```

To specify a code editor other than VSCode, pass the CLI arg used to
open said editor using one of these args:

```
localeet -e charm
localeet --editor subl
localeet --code_editor_open_command atom
```

To specify a language other than Python, use one of the following CLI
arg formats:

```
localeet --programming_language rust
localeet --language go
localeet -l ts
```

Valid language options:
```
c++
cpp
java
python
python3
py
c
c#
cs
javascript
js
ruby
rb
swift
go
golang
scala
kotlin
kt
rust
rs
php
typescript
ts
racket
rkt
erlang
erl
elixir
ex
dart
```

Print the manual:

```
localeet --help
```

## overriding defaults

If you want to set a different default value permanently, set it in your
environment like in these examples:

```
export LOCALEET_DEFAULT_MAX_DIFFICULTY=medium
export LOCALEET_DEFAULT_MIN_DIFFICULTY=medium
export LOCALEET_DEFAULT_OUTPUT_PATH=./leetcode
export LOCALEET_DEFAULT_CODE_EDITOR_OPEN_COMMAND=vi
export LOCALEET_DEFAULT_LANGUAGE=cpp
```

# contributions

## local setup

```
    git clone https://github.com/dannybrown37/localeet.git
    python -m venv .venv
    source .venv/bin/activate
    pip install -U pip
    pip install -e .[dev, test]
    pre-commit install
    pytest tests -s -vv
```

## contribution process

1. Create a new branch
2. Add features you wish to propose
3. Stage and commit your changes, ensure pre-commit checks pass
4. Push your branch
5. Open a pull request
6. Ensure Pull Request Verification CI/CD pipeline passes
7. Get approved & merged
8. Ensure Publish to PyPI pipeline passes


## feature ideas

* Add commitizen for auto version updating
* Support submitting responses to LeetCode via CLI as well
* Whatever your imagination holds