semvec/pypi-packages huggingface dataset:
photonic 0.0.1
My neat tools grouped together!
Requires Python: >=3.6

# Photonic Utilities Library
## Description
Photonic is the library where I upload all my neat tools!

### _logging
This package is designed to make logging easier and customizable.  

**Quick start:**  
1) You need to configure your logger before using it, here is an example:


    logger_name = "my_logger"

    console_config(logger_name)  # This makes the logger log to the console (with colors)!
    json_file_config(logger_name)  # This makes the logger log to a json file (more detailed too).

2) Now, we are all set! To use the logger all you need to do is:


    logger = getLogger("my_logger")

    logger.debug(f"Test Message from logger.debug")
    logger.info(f"Test Message from logger.info")
    logger.warning(f"Test Message from logger.warning")
    logger.error(f"Test Message from logger.error")
    logger.critical(f"Test Message from logger.critical")

This code will log the messages to both the console and the json file.

You can use custom formats for the message or the provided formats in the logging.formatters.Format enum.

### utils
Utils are a group of functions that are nice to have ready for you.
Note: the functions currently in the package are meant to be used as a decorator.
Example:

    @threaded
    def treaded_function():
        # some code

Now, `threaded_function` will start in a new thread whenever called.

### enums
This package is a place where I put enums that I might use in the future.
Currently, it has one enum called `AnsiColor` which contains some of the colors used in the console.
Example:

    print(AnsiColor.red.value + "Example Error Text." + AnsiColor.reset.value)

## Contact Me!
If you have any suggestions to add to the library you can [email me](mailto:asem.sh2004@gmail.com). 
I am open to any constructive criticism!
how_now 0.0.3
Explain exceptions using AI.
Requires Python: >=3.8,<4.0

# how-now

[![Release](https://img.shields.io/github/v/release/habemus-papadum/how-now)](https://img.shields.io/github/v/release/habemus-papadum/how-now)
[![Build status](https://img.shields.io/github/actions/workflow/status/habemus-papadum/how-now/main.yml?branch=main)](https://github.com/habemus-papadum/how-now/actions/workflows/main.yml?query=branch%3Amain)
[![codecov](https://codecov.io/gh/habemus-papadum/how-now/branch/main/graph/badge.svg)](https://codecov.io/gh/habemus-papadum/how-now)
[![Commit activity](https://img.shields.io/github/commit-activity/m/habemus-papadum/how-now)](https://img.shields.io/github/commit-activity/m/habemus-papadum/how-now)
[![License](https://img.shields.io/github/license/habemus-papadum/how-now)](https://img.shields.io/github/license/habemus-papadum/how-now)

Explain exceptions using AI.

- **Github repository**: <https://github.com/habemus-papadum/how-now/>
- **Documentation** <https://habemus-papadum.github.io/how-now/>

## Getting started with your project

First, create a repository on GitHub with the same name as this project, and then run the following commands:

``` bash
git init -b main
git add .
git commit -m "init commit"
git remote add origin git@github.com:habemus-papadum/how-now.git
git push -u origin main
```

Finally, install the environment and the pre-commit hooks with 

```bash
make install
```

You are now ready to start development on your project! The CI/CD
pipeline will be triggered when you open a pull request, merge to main,
or when you create a new release.

To finalize the set-up for publishing to PyPi or Artifactory, see
[here](https://fpgmaas.github.io/cookiecutter-poetry/features/publishing/#set-up-for-pypi).
For activating the automatic documentation with MkDocs, see
[here](https://fpgmaas.github.io/cookiecutter-poetry/features/mkdocs/#enabling-the-documentation-on-github).
To enable the code coverage reports, see [here](https://fpgmaas.github.io/cookiecutter-poetry/features/codecov/).

## Releasing a new version

- Create an API Token on [Pypi](https://pypi.org/).
- Add the API Token to your projects secrets with the name `PYPI_TOKEN` by visiting 
[this page](https://github.com/habemus-papadum/how-now/settings/secrets/actions/new).
- Create a [new release](https://github.com/habemus-papadum/how-now/releases/new) on Github. 
Create a new tag in the form ``*.*.*``.

For more details, see [here](https://fpgmaas.github.io/cookiecutter-poetry/features/cicd/#how-to-trigger-a-release).

---

Repository initiated with [fpgmaas/cookiecutter-poetry](https://github.com/fpgmaas/cookiecutter-poetry).
log-wizard 1.2.0
Siple logging for porject with multiple modules
Requires Python: >=3
Keywords: python logging

# log_wizard

## Installation
To get started with Log Wizard, you can easily install it using pip
```bash
pip install log-wizard
```

## usage
```python
from log_wizard import DefaultConfig, log
# initilize DefaultConfig if need
# You can do it onece, before first call of log
# Also look at params for DefaultConfig
# info_file_postfix takes all log msgs except .debug
# debug_file_postfixh takes all log msgs

DefaultConfig(info_file_postfix = 'info', debug_file_postfixh = 'debug')
# I can add a handler for your own function
# DefaultConfig().set_ui_log_func(print)


# now in any module of your project you can use this log
log = log()

# write log info
log.info("info") # 20.09.2023 06:10:35 - INFO - info
log.error("error") # 20.09.2023 06:10:35 - ERROR - error
log,critical("critical") # 20.09.2023 06:10:35 - CTITICAL - critical
proc_id = '12345'
with log.insert_proc_id(proc_id):
    #20.09.2023 06:10:35 - INFO - 12345 - here should be proc id
    log.info("here should be proc id")
    with log.insert_func_name():
        log.info("here also should be proc id and a func name, where log was called")
```

## Configuration
You can configure Log Wizard by modifying the DefaultConfig class.

## Features
Insert process IDs into log messages
Insert function names into log messages
Supports different log levels (info, error, debug, critical, etc.)

## License
This project is licensed under the Apache License, Version 2.0 - see the LICENSE file for details.

## Contact
For any questions or feedback, feel free to contact me at ruslan.izhakovskij@gmail.com.
lsstream 1.4.2
To help lazy tech boys and girls at ASU's SILC LSS with Streaming Requests 😴 🖥️ 🎞️
Requires Python: >=3.7

<div align="center">
    <img src="https://raw.githubusercontent.com/Wermutton/lsstream/main/assets/lsstream.png" alt="lsstream">
</div>

<p align="center">
  A nifty utility to assist the tech-savvy students of ASU's SILC LSS with their Streaming Requests. Say goodbye to tedium! 😴 🖥️ 🎞️
</p>

## 🚀 Getting Started

### Prerequisites

- Python (3.7 or higher)

### Installation

Install the `lsstream` package via pip through your command line:

```bash
> pip install lsstream
```

or

```bash
> pip3 install lsstream
```

## 🎯 Usage

To run `lsstream`, type the following command in your command line:

```bash
> python -m lsstream.run
```

or

```bash
> python3 -m lsstream.run
```

Simply follow the on-screen prompts to streamline your streaming experience! :sparkles:

## 💡 Features

- **Batch File Generation**: Generates multiple .txt files in a snap. Just input your media titles and links, and `lsstream` will use the correct template to create your files.
- **Embed Code Testing**: Say goodbye to waiting! Test the embed code almost instantaneously and make sure everything works perfectly. Codes are copied to your clipboards and

## 📝 License

This project is licensed under the MIT License.

## ❗ Issues

If you encounter any issues, please post them [here](https://github.com/Wermutton/lsstream/issues).

<div align="center">
    <h2>🎉 Happy Streaming! 🎉</h2>
</div>