naotool 0.3.5
A packge of utils or tools keeps Python sweet.
License: MIT
Requires Python: >=3.10

<div align="center">
  <a href="https://github.com/tomorinao-www">
    <img src="./imgs/logo-circle.svg" 
      height="300px" width="300px"
      alt="naotool" >
  </a>
  <br>
  <a href="https://github.com/tomorinao-www">
    <img src="./imgs/logo-square.svg" 
      height="" width="400px"
      alt="naotool" >
  </a>
  <br>

</div>

<div align="center">

# naotool

_✨ 🍬A packge of utils or tools keeps Python sweet. 让 py 保持甜甜的 ✨_

<a href="https://github.com/tomorinao-www/naotool/blob/main/LICENSE">
  <img src="https://img.shields.io/github/license/tomorinao-www/naotool.svg" alt="license:MIT">
</a>
<a href="https://pypi.python.org/pypi/naotool">
  <img src="https://img.shields.io/pypi/v/naotool.svg?style=flat&logo=pypi&logoColor=fff&labelColor=3775A9" alt="pypi">
</a>
<a hred="https://www.python.org/">
  <img src="https://img.shields.io/badge/Python-3.10+-f09?style=flat&logo=Python&logoColor=fc5&labelColor=3776AB" alt="Python">
</a>
<a href="https://github.com/tomorinao-www/naotool">
  <img src="https://img.shields.io/github/stars/tomorinao-www/naotool.svg?style=social">
</a>
 
</div>

# naotool

🍬A packge of utils or tools keeps Python sweet.

# 快速上手

```sh
pip install naotool
```

# 最佳实践

```python
import naotool as nt

@nt.decodeco  # 使用根模块：用 `nt.` 直接调用
@nt.deco.compat_arg_error  # 使用子模块：提高代码可读性；便于 IDE 提供更精确的语法提示
def f():
    pass
f(1, 2, 3, a=1)
print("ok!")
```

```python
# 脚本任务: 修改 `.jpg` 图片的文件名为 `{md5}.jpg`
import asyncio
import os
from pathlib import Path
from PIL import Image
import naotool as nt

Image.MAX_IMAGE_PIXELS = None
img_dir = Path(r"../../imgs/")
img_name_list = filter(lambda x: x.endswith(".jpg"), os.listdir(str(img_dir)))
path_list = [img_dir / name for name in img_name_list]

async def rename_image(src: Path):
    try:
        md5 = nt.img_md5hex(await get_imgs(str(src)))
        new_path = img_dir / f"{md5}{src.suffix}"
        os.rename(src, new_path)
    except Exception as e:
        print(f"Failed to process {src}: {e}")
async def main():
    await asyncio.gather(*(rename_image(src) for src in path_list))
asyncio.run(main())
```

# tools

| module    | example                                 | description        |
| --------- | --------------------------------------- | ------------------ |
| cls       | copy_attr(a, b)                         | SpringBean (?)     |
| deco      | @decodeco()                             | 装饰装饰器？       |
| httpn     | AutoCloseAsyncClient(auto_close_time=3) | 更简洁的 http      |
| img       | get_imgs(["http://img.png"])            | 图片               |
| strs      | tight("delete b l a n k char")          | 你的字符串有点松弛 |
| x         | get_xposts()                            | 获取 x.com 的 文章 |
| exception | NOException                             | 没有异常           |

# python 设计哲学

- 需求至上原则 - demand is God
- 最小重复原则 - DRY 准则 - don't repeat yourself
- 向后兼容原则 - the latest version, for the oldest code
- 数学哲学美学 - Mathematical Philosophy Aesthetics

```py
>>> import this
The Zen of Python, by Tim Peters

Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than *right* now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea -- let's do more of those!
>>>
```

```txt
Python 之禅（作者 Tim Peters）

美优于丑
明确的而不是隐晦的
简单的而不是复杂的
复杂的而不是繁杂的
扁平的而不是嵌套的
稀疏的而不是密集的
可读性至关重要
特例也不能破坏规则
即使假借实用性之名
不应让异常悄悄溜走
除非明确容忍错误
当面临不确定性，不要尝试去猜测
应当只有一种 —— 最好是唯一一种 —— 明显的解决方案
虽然这一开始可能并不容易，除非你是 Dutch
做也许好过不做
但不假思索就动手还不如不做
如果实现是难以解释的，那可能不是个好主意
如果实现是容易解释的，那可能是个好主意
命名空间是一种绝妙的理念 —— 我们要多加利用！
```