semvec/pypi-packages huggingface dataset:
dnoticias-backoffice 2.0.1
DN Backoffice
License: MIT
Requires Python: <4.0,>=3.10

=====
dnoticias_backoffice
=====
This package contains all the utilities/components/templates used in the dnoticias.pt backoffices.
Our objective is to have in one place the most used HTML components/layouts, this will standardize
all the sites and will allow more easy theme/components updates.


## Settings

1) Add the following variables to the project settings
```py
# Base full URL (like https://subdomain.example.com)
BASE_URL = ""
# Verbose site name (like Edição, Assinaturas, etc)
SITE_NAME = ""
```

2) Add the context processor in your settings and the slippers builtin (to avoid 
writing {% load slippers %} in every template where we use components).
```py
TEMPLATES = [
    {
        'BACKEND': 'django.template.backends.django.DjangoTemplates',
        'DIRS': [os.path.join(BASE_DIR, "templates")],
        'APP_DIRS': True,
        'OPTIONS': {
            'context_processors': [
                ...
                'dnoticias_backoffice.context_processors.backoffice',  # <-
            ],
            "builtins": ["slippers.templatetags.slippers"],  # <-
        },
    },
]
```

3) Add 'slippers' and 'dnoticias_backoffice' into your installed apps
```py
INSTALLED_APPS = [
    ...
    'dnoticias_backoffice',
    'slippers',
    ...
]
```


## How to load custom components
This project already has his own components, to load custom components without crashing the project
you just need to create a py file (e.g: components.py) in the project folder (where the settings.py
file is located at), create a function called e.g: load_custom_components(), inside this function
you will call the register_components function (https://mitchel.me/slippers/docs/registering-components/)
and finally, go to your apps.py file, locate or create the def ready() function and then import and
add the load_custom_components() function call.


## How to add/update/remove menu items
Create a menu.py file inside the project folder (where the settings.py file is located at), create
a function called e.g: load_menu(), inside this function you need to call register_menu_item function
imported from `dnoticias_backoffice.menu`. When you finally defined all the menu items you need to
import and call the load_menu() function into the def ready() function on the apps.py file (just 
like we call the custom components)


## Project templates structure
`templates/components` includes all the slipper components used along the backoffice.
`templates/backoffice` includes the masters templates and includes.
bitsightpy 0.1.8
An SDK for working with BitSight Tech APIs
License: MIT
Requires Python: <4.0,>=3.11

# bitsightpy - A Python SDK for Interacting With [Bitsight](https://bitsight.com) APIs

![Logo](https://raw.githubusercontent.com/0x41424142/bitsightpy/main/imgs/logo.png)


[![Code Style: black](https://img.shields.io/badge/code%20style-black-000000.svg?style=for-the-badge)](https://github.com/psf/black) ![Development Status](https://img.shields.io/badge/in%20development-8A2BE2?style=for-the-badge)  ![PyPI - Latest Version](https://img.shields.io/pypi/v/bitsightpy?style=for-the-badge&logo=pypi&logoColor=yellow) ![Python Versions](https://img.shields.io/pypi/pyversions/bitsightpy?style=for-the-badge&logo=python&logoColor=yellow) ![GitHub Stars](https://img.shields.io/github/stars/0x41424142/bitsightpy?style=for-the-badge) ![PyPI - Downloads](https://img.shields.io/pypi/dm/bitsightpy?style=for-the-badge&logo=pypi&logoColor=yellow)

![Black Formatter Status](https://github.com/0x41424142/bitsightpy/actions/workflows/black.yml/badge.svg?event=push) ![CodeQL Scan Status](https://github.com/0x41424142/bitsightpy/actions/workflows/codeql.yml/badge.svg?branch=main)

```py
from bitsightpy.portfolio import get_details

key = '<API_TOKEN>'

portfolio_details = get_details(key)
>>>[
    {
        'guid': '11111111-1111-1111-1111-111111111111', 
        'custom_id': None, 
        'name': 'Some Company', 
        'rating': 750, 
        'industry': {'name': 'Technology', 'slug': 'technology'}, 
        ...
    }, 
...]
```

## Currently Supported Modules/Calls

| Module | Status |
| -- | -- |
| ```users``` | ✅ Fully Implemented |
| ```insights``` | ✅ Fully Implemented |
| ```portfolio``` | ✅ Fully Implemented |
| ```folders``` | ✅ Fully Implemented |
| ```finding_details``` | ✅ Fully Implemented |
| ```alerts``` | ✅ Fully Implemented |
| ```companies``` | 🏗️ In Progress |


# Disclaimer

This SDK tool is an independent project and is not an official product of Bitsight. It has been developed and maintained solely by the names listed in the GitHub contributors list. Bitsight has neither endorsed nor approved this SDK.

Users of this SDK are advised to use it at their own risk and discretion.

For official tools and support, please refer to the [official Bitsight resources and documentation](https://help.bitsighttech.com/hc/en-us).
pkrhistoryparser 3.0.4
A poker package to parse Hand histories into json objects
License: MIT
Requires Python: >=3.10


# PokerHistoryParser

## Description
A poker package to parse Hand histories into json objects

PokerHistoryParser is a powerful tool for analyzing and extracting data from poker hand histories.  
This project is designed to help poker players and analysts better understand their performance by providing detailed 
analyses of hands played.


## Table of Contents

- [Introduction](#introduction)
- [Installation](#installation)
- [Utilisation](#utilisation)
- [Contribuer](#contribuer)
- [Licence](#licence)
- [Auteurs](#auteurs)

## Introduction

Welcome to the PokerHistoryParser documentation.  
This tool allows you to analyze poker hand histories.  
It is designed to be easy to use and integrate into your projects.  
It returns data as a dictionary or JSON file for easy use in your programs.


## Installation
To install the package, use the following command:


```sh
pip install pkrhistoryparser
```

## Usage

### Base Examples
Here are some simple examples of using PokerHistoryParser:

Parse a poker hand history to a dict to be used in a program:


```python
from pkrhistoryparser.parser import HandHistoryParser

parser = HandHistoryParser()
hand_text = parser.get_raw_text("path/to/hand/history.txt")
hand_info = parser.parse_hand(hand_text)
   ```

Parse a poker hand history to a JSON file:
```python
from pkrhistoryparser.parser import HandHistoryParser

parser = HandHistoryParser()
parser.parse_to_json('path/to/hand/history.txt', 'path/to/save/json/file.json')
```
For more details on usage, please refer to the [documentation](https://pkrhistoryparser.readthedocs.io/en/latest/).

### Supported Poker Sites
Currently, PokerHistoryParser supports the following poker sites:
- Winamax

### Upcoming Features
Here are some features we plan to add in future versions:
- Analysis of tournament summary files
- Analysis of CashGame files
- Support for more poker sites

## Contributing

All contributions are welcome! To contribute, please follow these steps:

1. Fork the repository
2. Create a branch for your feature (`git checkout -b feature/AmazingFeature`)
3. Commit your changes (`git commit -m 'Add some AmazingFeature'`)
4. Push to the branch (`git push origin feature/AmazingFeature`)
5. Open a Pull Request


## License

This project is licensed under the *MIT* license. See the [LICENSE](LICENSE.txt) file for more details.

## Authors

- **Alexandre MANGWA** a.k.a [Manggy94 on GitHub](https://github.com/manggy94) - *Main dev* - 

## Associated Projects
- [PokerComponents](https://github.com/manggy94/PokerComponents)

---

For any questions or issues, feel free to open an issue in the repository or contact us directly.
clickup_to_jira 1.1.2
This project is a small utility that helps migrating tasks from ClickUp to JIRA.
License: MIT
Requires Python: <4.0.0,>=3.8.0
Keywords: clickup_to_jira

![CI](https://github.com/anmarkoulis/clickup-to-jira/workflows/CI/badge.svg)
[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)

[![Documentation Status](https://readthedocs.org/projects/clickup-to-jira/badge/?version=latest)](https://clickup-to-jira.readthedocs.io/en/latest/?badge=latest)
# ClickUp to JIRA Converter

## Description

This project is a small utility that helps migrating tasks from ClickUp to JIRA.

## Installation

In order to use the package please install it by running the following command in the directory where the `pyproject.toml` is found:

```bash
make install
```

## Execution

After installing the library run the following command.

```bash
make migrate_to_jira
```

Keep in mind that the following environmental variables need to have a proper value.

|Environmental Variable|Required|Default|Description                                          |
|----------------------|--------|-------|-----------------------------------------------------|
|`JIRA_URL`            |True    |None   |The base URL for JIRA API                            |
|`JIRA_API_KEY`        |True    |None   |The API key created for accessing JIRA               |
|`JIRA_USER`           |True    |None   |Email of the JIRA user the API key belongs to        |
|`CLICKUP_API_KEY`     |True    |None   |The API key created for accessing ClickUp            |
|`LOGGING_FORMAT`      |False   |%(asctime)s %(name)-12s:" " %(levelname)-" "8s -  " "%(message)s|The format of the application logs|
|`LOGGING_LEVEL`       |False   |INFO   |The logging level of the application
|`JIRACLICKUPLINK`     |False   |None   |If True, will create link from Jira to ClickUp       |
|`STATUSMAP`           |False   |None   |Filename/path of status map file. Format: clickupvalue=jiravalue, per line|
|`TYPEMAP`             |False   |None   |Filename/path of type map file. Format: clickupvalue=jiravalue, per line|