semvec/pypi-packages huggingface dataset:
hieralog2 0.1.0
Hierarchical logging library with enhanced printing functions.
Requires Python: >=3.6

# Hieralog

**Hieralog** is a hierarchical logging library for Python that provides enhanced logging and printing functions. It supports multiple levels, color coding, framed and plain output, and integrates seamlessly with progress bars.

## Features

- **Hierarchical Logging:** Auto-detect log levels with a "[x]" prefix.
- **Color-Coded Output:** Different colors for each log level.
- **Enhanced Print Functions:** 
  - **hprint()**: Hierarchical (framed) logging output.
  - **pprint()**: Plain print with hierarchical indentation.
  - **fprint()**: Framed print with hierarchical indentation.
  - **progress_write()**: Writes progress messages with the proper indent.
- **Automatic Completion Message:** A final completion log is printed automatically when the program ends.

## Installation

Install via pip:

```bash
pip install hieralog1
all-of-resources 1.10.4
可以通过client.jar和.minecraft/assets下的松散文件提取Minecrafft的所有资源

# 📦 All Of Resources
一个工具可以从client.jar和.minecraft/assets文件夹提取minecraft所有资源的工具  
请勿分发使用这个程序提取出来的资源，这些资源仅用作资源包的开发，我不会对此承担任何责任

## 🛠️ 安装
1. 使用pip安装
    ```bash
    pip install all-of-resources
    ```
    运行
    ```bash
    # Flutter界面
    aor

    # Tk界面
    aortk
    ```

2. 针对Windows的二进制文件
   直接下载并解压Release的`all-of-resources_1.00_windows.7z`文件，然后运行`aortk.exe`  
   
   谁知道怎么打包Flutter界面的aor.exe呀，我`flet build windows`打包不了，欢迎提交PR帮一下我！

## 🖼️ 截图
| ![](./screenshot1.png) | ![](./screenshot2.png) |
| :--------------------: | :--------------------: |
|       Tkinter界面      |       Flutter界面       |

## 📓 更新日志
### 1.10.4
- 修复安卓版本直接启动不了了！
- 这个Bug太离谱了

### 1.10.3
⚡没有Bug，只有特性⚡
- 修复了安卓11+用不了的问题，好奇怪呀
- 缩短了关于文字
- 移除了Herobrine

### 1.10.2
- 不小心上传了1.10.1，然后没有放icon.png这个文件，这个版本修复

### 1.10.1
- 手机的图标有点不对劲 (flet默认图标)... 我给他修了
- 现在手机端分离了apk，armabi和arm64两个架构使用了不同的安装包，减小了apk的大小

### 1.10
- 分离了前后端
- 添加了flet前段以支持手机
- 移除了Herobrine

### 1.00
- 第一个版本
crimson-code-splitter 0.1.2
Split code for code generation.
Requires Python: >=3.9

**Template README.md**\
This file is from the [template repository](https://github.com/crimson206/template/blob/main/README.md).
Rewrite it for your own package.

## Python Package Setup

### Setup Base

To install required pip modules for `generate_toml.py`, run
``` bash
source scripts/setup_base.sh
```

### User Setup

- go to `generate_toml.py` file, and complete the setup in the `User Setup` session.

```python
options = Options(
    # Will you use the discussion session in your repo?
    discussion=False
)

# Define the general information of your package
kwargs = Kwargs(
    name_space="None",
    module_name="None",
    description="None",
)
```

If you wrote all the information, run
```
python generate_toml.py
```

#### Template

If you want to understand the generation process, check the `template` variable in `generate_toml.py`.

### Setup Env

#### Prerequisite

Finish [User Setup](#user-setup) first.
Of course, conda command must be available.

#### Setup Env

Run
``` bash
source scripts/setup_env.sh
```

steps
- create an conda environment named as your $MODULE_NAME
- activate the environment.
- install requirements.txt

#### Generate Private Env
Generate a private repository in this repo.
I recommend you to write all the unstructured codes in this repo.

``` bash
source scripts/generate_dev_repo.sh
```

It will ask you the name of your repo, and then, generate a repo named f'{your_repo_name}-dev'.

**Usage Tip**

If you wrote your codes in a wrong branch,
- backup the files to the dev repo
- remove changes in your main(not main branch) repo
- move to your correct branch
- place back the backup codes


## Workflows

I currently setup test and release workflows.

**Test**

If you make a PR with the patterns [ main, develop, 'release/*', 'feature/*' ],

It will perform your unittest in ["3.9", "3.10", "3.11"]

**Release**

required secret : PYPI_API_TOKEN

I usually make PRs only when I start release branches.
release workflow is not conducted automatically. If you think your branch is ready to be published, 

- go to https://github.com/{github_id}/{repo_name}/actions/workflows/release.yaml
- find the button, 'Run workflow'
- select the branch to publish. In my case, release/x.x.x
qfactory 1.0.1
A Qt based ui widget to manage a factories.Factory
Requires Python: >3.1.1

# qfactory

A Qt based widget for representing a factory (factories.Factory) instance. This widget
allows for the adding/removing of paths from the factory. Equally it allows for plugins
to be enabled/disabled.

## Install

```
pip install qfactory
```

## Example

This example demonstrates how the widget works and how it updates based on the changes
within the factory.

```python
import qtility
from factories.examples import zoo
from qfactory import FactoryWidget

# -- Instance the example which comes with the factories module
zoo_instance = zoo.Zoo()

# -- Now instance a QApplication and then our Factory widget. We pass
# -- the factory as an argument to the widget. The widget will bind into
# -- the factory signals and represent that factory
qapp = qtility.app.get()

w = FactoryWidget(factory=zoo_instance.factory)
w.show()

qapp.exec()
```