semvec/pypi-packages huggingface dataset:
converter-package-Hugo-Azix 0.0.1
A small example package
Requires Python: >=3.7

# M1-2022-git

## Introduction
This repository is a fork from the previous repository.
The bugs in the converter have been fixed and now we want to publish our work as a publicly available python package.

## Getting started
You should be working from **your own repository** that is a fork of M1-2022-git-workflow.
In order to run this project, you will have to follow these steps.
1. Clone this project
2. move into the project folder
``` shell
cd M1-2022-git-workflow
```
3. Set up a virtual environment
 * Create the virtual environment
 ```shell
 python -m venv myvenv
 ```
 * Activate venv
 ```shell
 . venv/bin/activate
 ```
4. Install pytest
```shell
pip install -U pytest
```
5. Execute main script
```shell
python main.py
```

## Instructions
### Merge feature branch into dev
Now that the converter has no more bugs, we want to merge our branch feature into the dev branch.
We will do a pull request (on your own repo). On GitHub, go to the "Pull requests tab" and click "New pull request".
Select *base* and *compare*. Remember : we want to merge *decimal-binary-converter* into *dev*. 
Then, *Create the pull request*. Add some description of the work you have done and publish the Pull Request.

**Note** : We could have just merge *decimal-binary-converter* into *dev* from the command line. However, when working on a real project, you probably won't have the rights to do so. Remember : dev is a public branch. So all the work going down there should be carefully reviewed and tested.


### Publish your work
We now have an awesome binary/decimal two ways converter ! It's time to publish it so the rest of the world can enjoy it !
We will publish it on PyPI (Python Package Index) which is a public repository of softwares for Python.
1. First, you have to create an account on [Pypi.org](https://pypi.org/)
2. Then, in your repository, you will find a [.github directory](/.github)
3. Inside this directory, you will find .yml files that defines workflows (using GitHub actions)
4. Open the yml files and take time to understand them. Do not hesitate to ask the teacher about them

#### Hands on !
5. We want to create a workflow that will, on publish, test our code and if tests succeed, then publish our package on PyPI
6. In GitHub, click on the *Actions* tab, then click on *new workflow*
7. Choose among the suggestions the template that best suits your use-case and click *Configure*
8. You may find some useful informations in the [Python documentation](https://packaging.python.org/en/latest/tutorials/packaging-projects/)
9. When creating a release on GitHub, do not forget to create a tag corresponding to that release

#### Pull request
10. Once the workflow is setup and tested (you have published your package using it) you can open a pull request to the [original repository](https://github.com/rgt-yncrea/M1-2022-git-workflow)
package-matthis-bernet 0.0.1
Package du TP2 de Matthis Bernet
Requires Python: >=3.7

# M1-2022-git

## Introduction
This repository is a fork from the previous repository.
The bugs in the converter have been fixed and now we want to publish our work as a publicly available python package.

## Getting started
You should be working from **your own repository** that is a fork of M1-2022-git-workflow.
In order to run this project, you will have to follow these steps.
1. Clone this project
2. move into the project folder
``` shell
cd M1-2022-git-workflow
```
3. Set up a virtual environment
 * Create the virtual environment
 ```shell
 python -m venv myvenv
 ```
 * Activate venv
 ```shell
 . venv/bin/activate
 ```
4. Install pytest
```shell
pip install -U pytest
```
5. Execute main script
```shell
python main.py
```

## Instructions
### Merge feature branch into dev
Now that the converter has no more bugs, we want to merge our branch feature into the dev branch.
We will do a pull request (on your own repo). On GitHub, go to the "Pull requests tab" and click "New pull request".
Select *base* and *compare*. Remember : we want to merge *decimal-binary-converter* into *dev*. 
Then, *Create the pull request*. Add some description of the work you have done and publish the Pull Request.

**Note** : We could have just merge *decimal-binary-converter* into *dev* from the command line. However, when working on a real project, you probably won't have the rights to do so. Remember : dev is a public branch. So all the work going down there should be carefully reviewed and tested.


### Publish your work
We now have an awesome binary/decimal two ways converter ! It's time to publish it so the rest of the world can enjoy it !
We will publish it on PyPI (Python Package Index) which is a public repository of softwares for Python.
1. First, you have to create an account on [Pypi.org](https://pypi.org/)
2. Then, in your repository, you will find a [.github directory](/.github)
3. Inside this directory, you will find .yml files that defines workflows (using GitHub actions)
4. Open the yml files and take time to understand them. Do not hesitate to ask the teacher about them

#### Hands on !
5. We want to create a workflow that will, on publish, test our code and if tests succeed, then publish our package on PyPI
6. In GitHub, click on the *Actions* tab, then click on *new workflow*
7. Choose among the suggestions the template that best suits your use-case and click *Configure*
8. You may find some useful informations in the [Python documentation](https://packaging.python.org/en/latest/tutorials/packaging-projects/)
9. When creating a release on GitHub, do not forget to create a tag corresponding to that release

#### Pull request
10. Once the workflow is setup and tested (you have published your package using it) you can open a pull request to the [original repository](https://github.com/rgt-yncrea/M1-2022-git-workflow)
example-package-PERRIN-Liam 0.0.3
Test du deploiement
Requires Python: >=3.7

# M1-2022-git

## Introduction
This repository is a fork from the previous repository.
The bugs in the converter have been fixed and now we want to publish our work as a publicly available python package.

## Getting started
You should be working from **your own repository** that is a fork of M1-2022-git-workflow.
In order to run this project, you will have to follow these steps.
1. Clone this project
2. move into the project folder
``` shell
cd M1-2022-git-workflow
```
3. Set up a virtual environment
 * Create the virtual environment
 ```shell
 python -m venv myvenv
 ```
 * Activate venv
 ```shell
 . venv/bin/activate
 ```
4. Install pytest
```shell
pip install -U pytest
```
5. Execute main script
```shell
python main.py
```

## Instructions
### Merge feature branch into dev
Now that the converter has no more bugs, we want to merge our branch feature into the dev branch.
We will do a pull request (on your own repo). On GitHub, go to the "Pull requests tab" and click "New pull request".
Select *base* and *compare*. Remember : we want to merge *decimal-binary-converter* into *dev*. 
Then, *Create the pull request*. Add some description of the work you have done and publish the Pull Request.

**Note** : We could have just merge *decimal-binary-converter* into *dev* from the command line. However, when working on a real project, you probably won't have the rights to do so. Remember : dev is a public branch. So all the work going down there should be carefully reviewed and tested.


### Publish your work
We now have an awesome binary/decimal two ways converter ! It's time to publish it so the rest of the world can enjoy it !
We will publish it on PyPI (Python Package Index) which is a public repository of softwares for Python.
1. First, you have to create an account on [Pypi.org](https://pypi.org/)
2. Then, in your repository, you will find a [.github directory](/.github)
3. Inside this directory, you will find .yml files that defines workflows (using GitHub actions)
4. Open the yml files and take time to understand them. Do not hesitate to ask the teacher about them

#### Hands on !
5. We want to create a workflow that will, on publish, test our code and if tests succeed, then publish our package on PyPI
6. In GitHub, click on the *Actions* tab, then click on *new workflow*
7. Choose among the suggestions the template that best suits your use-case and click *Configure*
8. You may find some useful informations in the [Python documentation](https://packaging.python.org/en/latest/tutorials/packaging-projects/)
9. When creating a release on GitHub, do not forget to create a tag corresponding to that release

#### Pull request
10. Once the workflow is setup and tested (you have published your package using it) you can open a pull request to the [original repository](https://github.com/rgt-yncrea/M1-2022-git-workflow)
generate-report 1.0.0
自动生成测试报告工具

# report_origin
## 介绍
一款用于自动生成测试报告的工具

注意事项：需安装谷歌浏览器


- chrome_driver.py 用于检查是否安装谷歌浏览器驱动及驱动版本是否兼容，若无驱动或驱动版本不兼容，则自动下载
- db_connect.py 存放操作数据库的方法
- get_db.py 用于连接数据库
- config.yml 存放数据库配置文件
- project_data.yml 存放数据文件
- template.docx 测试报告的模板
- report_res：运行时自动生成，用于存放生成的结果图片
- test_report.py：主文件引用的脚本文件
- run.py 主文件，执行的入口



## 使用说明
运行run.py文件，生成的测试报告默认保存在D:/中，可在运行时指定存放路径。

例：
```
from generate_report import run   # 引包

run.run()   # 运行run.py文件中的run函数


请输入项目名称：
请输入撰写人：
请输入预估di值，若无预估di值，请输入数字0：
请指定报告生成的路径，若不指定，请按回车键（注意：在输入路径时，请不要使用反斜杠）：

```



## 版本规范
保持和python版本命名一致，格式：x.x.x

- 大版本：1.x.x	第一位变化
- 小版本：x.1.x	第二位变化
- bug修复版本：x.x.1	最后一位变化
lectio.py 0.2.1
Interact with lectio through python

# lectio.py

[![License](https://img.shields.io/github/license/dnorhoj/lectio.py)](LICENSE)
[![Documentation Status](https://readthedocs.org/projects/lectiopy/badge/?version=latest)](https://lectiopy.readthedocs.io/en/latest/?badge=latest)
[![PyPi version](https://img.shields.io/pypi/v/lectio.py.svg)](https://pypi.org/project/lectio.py/)
[![PyPi supported python versions](https://img.shields.io/pypi/pyversions/lectio.py.svg)](https://python.org/)

*Please note: This library is nowhere close to done.*

The best way to get data from Lectio with Python 3.

The goal of this library,
is to be able to fetch different parts of the Lectio interface in a readable format.

You can read the documentation

## How do i use this?

You can install this library via `pip`:

    pip install lectio.py

For a quickstart guide as well as some examples, you can read the documentation [here](https://lectiopy.rtfd.io/).

## Progress

<details>
    <summary>Implementation progress</summary>

* [x] Schedule
* [x] User info
* [ ] Absence
* [ ] Mail
* [ ] Assignments
* [ ] Homework
* [ ] Surveys (Probably not going to be implemented)
* [ ] Grades
* [ ] Search for students / teachers

</details>

## Todo

* [ ] Make a better README
* [ ] Quickstart, Examples, etc.

## Known bugs

* Not made to work with teacher accounts (as i have no way of testing anything)

## Contributing

If you want to contribute, you can just fork this repository and start a pull request.

If you notice something that isn't working as intended you can start an issue.

## License

This repository uses the `GNU Lesser General Public License v3.0` you can read more about it in [LICENSE](LICENSE).
slsdebugger 0.0.9
Serverless Debugger Python
Requires Python: !=2.7, !=3.0.*, !=3.1.*, !=3.2.*, !=3.3.*, !=3.4.*, !=3.5.*

# serverlessdebugger-agent-python

[![Pyversions](https://img.shields.io/pypi/pyversions/slsdebugger.svg?style=flat)](https://pypi.org/project/slsdebugger/)
[![PyPI](https://img.shields.io/pypi/v/slsdebugger.svg)](https://pypi.org/project/slsdebugger/)

Debug your python lambda with ServerlessDebugger by [Thundra](https://www.serverlessdebugger.com)!

## Contents

- [Configuration](#Installation-Configuration)
- [Getting Help](#getting-help)
- [Opening Issues](#opening-issues)


## Configuration

Check out the [VS Code](https://docs.serverlessdebugger.com/extensions/vs-code) and [Python](https://docs.serverlessdebugger.com/configuration/python) configurations of our docs for more detailed information.

## Getting Help

If you have any issue around using the library or the product, please don't hesitate to:

* Use the [documentation](https://docs.serverlessdebugger.com).
* Join our [discord channel](https://www.serverlessdebugger.com/discord-invitation).


## Opening Issues

For any problem you encounter while using Serverless Debugger, please feel free to contact us.
converter-package-Bajiio 0.0.1
A small example package
Requires Python: >=3.7

# M1-2022-git

## Introduction
This repository is a fork from the previous repository.
The bugs in the converter have been fixed and now we want to publish our work as a publicly available python package.

## Getting started
You should be working from **your own repository** that is a fork of M1-2022-git-workflow.
In order to run this project, you will have to follow these steps.
1. Clone this project
2. move into the project folder
``` shell
cd M1-2022-git-workflow
```
3. Set up a virtual environment
 * Create the virtual environment
 ```shell
 python -m venv myvenv
 ```
 * Activate venv
 ```shell
 . venv/bin/activate
 ```
4. Install pytest
```shell
pip install -U pytest
```
5. Execute main script
```shell
python main.py
```

## Instructions
### Merge feature branch into dev
Now that the converter has no more bugs, we want to merge our branch feature into the dev branch.
We will do a pull request (on your own repo). On GitHub, go to the "Pull requests tab" and click "New pull request".
Select *base* and *compare*. Remember : we want to merge *decimal-binary-converter* into *dev*. 
Then, *Create the pull request*. Add some description of the work you have done and publish the Pull Request.

**Note** : We could have just merge *decimal-binary-converter* into *dev* from the command line. However, when working on a real project, you probably won't have the rights to do so. Remember : dev is a public branch. So all the work going down there should be carefully reviewed and tested.


### Publish your work
We now have an awesome binary/decimal two ways converter ! It's time to publish it so the rest of the world can enjoy it !
We will publish it on PyPI (Python Package Index) which is a public repository of softwares for Python.
1. First, you have to create an account on [Pypi.org](https://pypi.org/)
2. Then, in your repository, you will find a [.github directory](/.github)
3. Inside this directory, you will find .yml files that defines workflows (using GitHub actions)
4. Open the yml files and take time to understand them. Do not hesitate to ask the teacher about them

#### Hands on !
5. We want to create a workflow that will, on publish, test our code and if tests succeed, then publish our package on PyPI
6. In GitHub, click on the *Actions* tab, then click on *new workflow*
7. Choose among the suggestions the template that best suits your use-case and click *Configure*
8. You may find some useful informations in the [Python documentation](https://packaging.python.org/en/latest/tutorials/packaging-projects/)
9. When creating a release on GitHub, do not forget to create a tag corresponding to that release

#### Pull request
10. Once the workflow is setup and tested (you have published your package using it) you can open a pull request to the [original repository](https://github.com/rgt-yncrea/M1-2022-git-workflow)