semvec/pypi-packages huggingface dataset:
loggify 0.2.1
Capture prints and tracebacks to a log file with 2 lines of code
License: MIT
Requires Python: >=3.7

# Loggify: capture prints and tracebacks to a log file with 2&nbsp;lines of code

[![Python](https://img.shields.io/badge/Python-3.7%20%7C%203.8%20%7C%203.9-blue)](https://www.python.org/downloads/)
[![PyPI version](https://img.shields.io/pypi/v/loggify?color=1)](https://pypi.org/project/loggify/)
[![license](https://img.shields.io/pypi/l/loggify)](https://github.com/ar-nowaczynski/loggify)

Loggify is a convenient way to redirect stdout and stderr to the timestamped log file. It works by temporarily overriding the default behaviour of `sys.stdout` and `sys.stderr` in the context manager. You still see the output in the console - it is just additionally streamed to the log file (see the example below).

## Installation

```bash
$ pip install loggify
```

## Usage

script.py:

```python
from loggify import Loggify

def main():
    print("START")
    for i in range(10):
        print(" " * i + "x")
    print("END")
    5 / 0   # traceback will be captured

with Loggify("main.log"):  # specify output filename
    main()
```

main.log:
```
2020-04-07 20:45:18.391:STDOUT:START
2020-04-07 20:45:18.391:STDOUT:x
2020-04-07 20:45:18.391:STDOUT: x
2020-04-07 20:45:18.391:STDOUT:  x
2020-04-07 20:45:18.391:STDOUT:   x
2020-04-07 20:45:18.391:STDOUT:    x
2020-04-07 20:45:18.391:STDOUT:     x
2020-04-07 20:45:18.391:STDOUT:      x
2020-04-07 20:45:18.391:STDOUT:       x
2020-04-07 20:45:18.391:STDOUT:        x
2020-04-07 20:45:18.391:STDOUT:         x
2020-04-07 20:45:18.392:STDOUT:END
2020-04-07 20:45:18.392:STDERR:Traceback (most recent call last):
2020-04-07 20:45:18.392:STDERR:  File "script.py", line 11, in <module>
2020-04-07 20:45:18.392:STDERR:    main()
2020-04-07 20:45:18.392:STDERR:  File "script.py", line 8, in main
2020-04-07 20:45:18.392:STDERR:    5 / 0   # traceback will be captured
2020-04-07 20:45:18.392:STDERR:ZeroDivisionError: division by zero
```

## License

MIT License (see [LICENSE](https://github.com/ar-nowaczynski/loggify/blob/master/LICENSE)).
pytest-requires 0.1.0
A pytest plugin to elegantly skip tests with optional requirements
License: MIT
Requires Python: >=3.5

# pytest-requires

[![PyPI version](https://img.shields.io/pypi/v/pytest-requires.svg)](https://pypi.org/project/pytest-requires)

[![Python versions](https://img.shields.io/pypi/pyversions/pytest-requires.svg)](https://pypi.org/project/pytest-requires)

[![Build status](https://github.com/duncanmmacleod/pytest-requires/actions/workflows/build.yml/badge.svg)](https://github.com/duncanmmacleod/pytest-requires/actions/workflows/build.yml)

A pytest plugin to elegantly skip tests with optional requirements

------------------------------------------------------------------------

This [pytest](https://github.com/pytest-dev/pytest) plugin was generated
with [Cookiecutter](https://github.com/audreyr/cookiecutter) along with
[\@hackebrot](https://github.com/hackebrot)\'s
[cookiecutter-pytest-plugin](https://github.com/pytest-dev/cookiecutter-pytest-plugin)
template.

## Features

- decorate tests that require optional modules (with an optional minimum version)
  and gracefully skip them when the requirements aren't importable

## Requirements

- pytest

## Installation

You can install \"pytest-requires\" via
[pip](https://pypi.org/project/pip/) from
[PyPI](https://pypi.org/project):

```shell
pip install pytest-requires
```

## Usage

### How to use pytest-requires

With pytest-requires, tests can be marked as requiring an external module
as follows:

```python
@pytest.mark.requires("dateutil")
def test_date_parsing():
    assert date_parsing() == RESULT
```

In this example if the python-dateutil module isn't installed the test is
skipped.
The import testing is all performed by pytest's builtin
[`importorskip`](https://docs.pytest.org/en/latest/how-to/skipping.html#skipping-on-a-missing-import-dependency)
function.

Notes:

- the `minversion` keyword can be given to specifiy a minimum acceptable
  version for the required module
- multiple modules can be given as positional arguments, with the decorated
  tested being skipped if any of the given modules cannot be imported
- in the case of multiple modules, only a single `minversion` can be given,
  and will be used for all modules; if an independent `minversion` is required
  for each module, use multiple `@pytest.mark.requires` decorators.

### Why not just use `pytest.importorskip`?

`pytest.importorskip` is designed to import a module and add the module
to the namespace (of the module, or the test function).
If the optional module isn't used in the test itself, but is really a
requirement of the function _being tested_, the call to `importorskip`
less elegant (in the author's opinion) than a decorator call.

## Contributing

Contributions are very welcome, please open a Pull Request.

## License

Distributed under the terms of the
[MIT](http://opensource.org/licenses/MIT) license, \"pytest-requires\"
is free and open source software

## Issues

If you encounter any problems, please
[file an issue](https://github.com/duncanmmacleod/pytest-requires/issues)
along with a detailed description.
fman 0.0.1
FMan - A external module for builtin works tool for Python 3 (open source).
License: MIT

# FMan - A data classifier and logic handler

## Version 0.0.1

## Developer [Md. Almas Ali][4]

### Details

[![LICENSE](https://img.shields.io/github/license/dwisiswant0/WiFiID.svg "LICENSE")](LICENSE)
![GitHub repo size](https://img.shields.io/github/repo-size/Almas-Ali/FMan?style=plastic "Size")
[![Downloads](https://static.pepy.tech/personalized-badge/fman?period=total&units=none&left_color=grey&right_color=blue&left_text=Total%20Downloads)](https://pepy.tech/project/fman "Downloads")


> To get more details about this project download visit [FMan Downloads][5]

To know more about [FMan][3] read the [documentation][3].

<hr>

## For any bug report feel free to set a pull request or issue in Github

Our Github link : [FMan][1] <br>
Pypi link : [FMan][2] <br>

[1]: https://github.com/almas-ali/fman "FMan Github"
[2]: https://pypi.org/project/fman "FMan Pypi"
[3]: https://Almas-Ali.github.io/fman "FMan Documentation"
[4]: https://github.com/almas-ali "Md. Almas Ali"
[5]: https://pepy.tech/project/fman "Download History"
catbird 0.0.2
Paraphrase generation Toolbox and Benchmark
License: MIT
Requires Python: >=3.8,<4.0
Keywords: nlp,paraphrase generation

<div align="center">
    </p>
    <img src="resources/catbird_logo.svg" width="200"/>
    </p>

  [![License: MIT](https://img.shields.io/badge/License-MIT-brightgreen.svg)](https://opensource.org/licenses/MIT)
</div>

`Catbird` is an open source paraphrase generation toolkit based on PyTorch.

## Quick Start

### Requirements and Installation
The project is based on PyTorch 1.5+ and Python 3.6+.

## Install Catbird

**a. Clone the repository.**
```shell
git clone https://github.com/AfonsoSalgadoSousa/catbird.git
```
**b. Install dependencies.**
This project uses Poetry as its package manager. There should Make sure you have it installed. For more info check [Poetry's official documentation](https://python-poetry.org/docs/).
To install dependencies, simply run:
```shell
poetry install
```

## Dataset Preparation
For now, we only work with the [Quora Question Pairs dataset](https://quoradata.quora.com/First-Quora-Dataset-Release-Question-Pairs). It is recommended to download and extract the datasets somewhere outside the project directory and symlink the dataset root to `$CATBIRD/data` as below. If your folder structure is different, you may need to change the corresponding paths in config files.

```text
catbird
├── catbird
├── tools
├── configs
├── data
│   ├── quora
│   │   ├── quora_duplicate_questions.tsv
```
We use the [HuggingFace Datasets library](https://huggingface.co/docs/datasets/) to load the datasets.

### Train

```shell
poetry run python tools/train.py ${CONFIG_FILE} [optional arguments]
```

Example:
1. Train T5 on QQP.
```bash
$ python tools/train.py configs/t5_quora.yaml
```

## Contributors
* [Afonso Sousa][1] (afonsousa2806@gmail.com)

[1]: https://github.com/AfonsoSalgadoSousa