semvec/pypi-packages huggingface dataset:
samep 0.0.5
samebotのplugin

# インストール

```
win:
py -3 -m pip install samep
linux:
python3.8 -m pip install samep
```

# 追加項目

## メインファイル

```py
#main.py

from discord.ext import commands as c
from discord import Intents
from asyncpgw import start

import asyncio

class Main(c.Bot):
    def __init__(self):
        super().__init__(
            command_prefix = '!',
            description = 'this is bot',
            intents = Intents.all()
            )
        
        self.tables = []

    async def ps_connect(self):
        "postgresqlに接続"
        self.pool = await start.connect('postgres://username:password@/dbname')


    async def add_table(self, table):
        """postgtesqlに作成するテーブルを追加する"""
        if table not in self.tables:
            self.tables.append(table)


    async def on_ready(self):
        print('起動しました。')

        self.load_extension('samep.extension')

        for table in self.tables:
            await start.create(self.pool, table)


    async def start(self):
        
        await super().start('bot token')

    
    def main(self):
        loop = asyncio.get_event_loop()
        loop.run_until_complete(self.ps_connect())
        loop.run_until_complete(self.start())
        loop.close()


if __name__ == '__main__':
    bot = Main()
    bot.main()
Lu-Project-4-C8123 0.0.2
A example package for course project

# README

## 目标

按参数批量进行试验
目前完成了基本部分

## 结构说明

main: 主函数
- main.py 测试主函数
- models.py 模型定义

analysis: 分析结果数据
- UncertaintyDrow 画图

base: 基础类库，用于存信息
- experiment.py 实验流程控制
- get_dataset.py 可以用名字获取数据集实例
- get_loss.py 可以用名字获取损失函数
- get model.py 可以用名字获取模型
- get_optimizer.py 可以用名字获取损失函数
- history.py 存储实验历史
- metrics.py 指标相关的类，如存储正确率，损失等指标
- runners.py 批量跑实验的类
- tool.py 一些工具函数
com.wyattbaldwin.make-release 1.0a2
Make a release
Requires Python: >=3.6,<4.0

# Make a Release

Make a release of a Python package. This automates the tedious steps you
need to go through to make a release--bumping the version number,
tagging, etc.

It does _not_ (currently) create distributions or upload them to PyPI.

## Usage

    make-release --version 1.0 --next-version 2.0

## Steps

By default, all the following steps are run:

- Runs your project's test suite using `python -m unittest discover`
  by default
- Prepare the release by bumping the version number in various files and
  setting the release date in the change log file
- Merge the development branch into the target branch (e.g., `dev` to
  `main`)
- Create an annotated tag pointing at the merge commit (or at the prep
  commit when merging is disabled); if no tag name is specified, the
  release version is used as the tag name
- Resume development by bumping the version to the next anticipated
  version

Any of the steps can be skipped by passing the corresponding
`--no-<step>` flag.

### Tag Name

The tag name can be specified as a simple format string template. The
project `name` and release `version` will be injected (see below in the
Configuration section for an example).

## Configuration

Configuration can be done in `pyproject.toml` or `setup.cfg`. This is
most useful if you want to permanently disable one of the default
options.

Use the long names of the command line options without the leading
dashes. For command line flags, set the value to `true` or `false`
(`1` and `0` also work).

For example, if your project only uses a single branch, you could
disable the merge step like so in `pyproject.toml`.

    # pyproject.toml
    [tool.make-release.args]
    merge = false
    tag-name = "{name}-{version}"

or like so in `setup.cfg`:

    # setup.cfg
    [make-release.args]
    merge = false
    tag-name = {name}-{version}

This also shows how to specify a tag name template that's derived from
the package `name` and the release `version`.

## Creating and Uploading Distribution

Once you've created a release with this tool, check out the tag for the
release and then run the following commands:

    poetry build           # if using poetry
    python setup.py sdist  # if using pip/setuptools
    twine upload dist/*    # in either case

NOTE: You'll need an account on pypi.org in order to upload
distributions with `twine`.

## Limitations

- Only git repositories are supported
- The package name detection assumes the root directory (i.e., the git
  repo name) is the same as the package name
- For the change log, only markdown files are supported; the change log
  is expected to use second-level (##) headings for each version's
  section (see this project's `CHANGELOG.md` for an example)
- Doesn't build or upload distributions
zoom-meet-attendance-visualizer 1.0.5
Manage and visualize data collected using extension zoom_meet_attendance

# Zoom Meet Attendance Visualizer
#### About
This module is to help to visualize your meeting attendance helper data created using 
<a href="https://github.com/mahbd/zoom_meet_attendance">zoom_meet_attendance</a>. You 
don't have to repeat anything except selecting data file. It will remember everything
in config.json.
#### Installation
`pip install zoom-meet-attendance-visualizer`
### How to use
<ol>
<li>Write this code, and you're ready to go. <br>
<pre>from zoom_meet_attendance_helper.main import run_attendance_helper

run_attendance_helper()
</pre>
</li>
<li>When you run this code it will ask you to select the text file created by 
<a href="https://github.com/mahbd/zoom_meet_attendance">zoom_meet_attendance</a>.
</li>
<li>Then it will ask **class**. Class will be used to avoid repetition. In class all attendee 
name will be saved to show who is absent. Also, if rename any name, it will remember it and
if you reuse the same class it will automatically suggest renaming.
</li>
<li>Then it will ask if you want to rename any name. If you want to rename then type a new name,
otherwise pre Enter without typing anything.
</li>
<li>
Then it will show all the names and ask you if you want to add more name. If you want to 
add then type else type Exit to show you the graph.
</li>
<li>
If you made any mistake you can manually edit config.json file automatically created on
the same directory.
</li>
</ol>