semvec/pypi-packages huggingface dataset:
stepizer 0.2.2
The tool for better organization of the workflow.
License: MIT
Requires Python: >=3.8, <4

# Stepizer

Chain multiple functions or generators into one pipeline.

Basic use case:
```python
from stepizer import Step


def add_text(string: str) -> str:
    return 'hello, ' + string + '!'


pipeline = Step.chain(
    add_text,
    str.upper,
)

pipeline.run('world')
# HELLO, WORLD!
```
cmeson 2021.10.3
TUI for meson build system
License: MIT
Keywords: cmeson meson build system TUI

cmeson is a text-based user interface for the [meson](https://mesonbuild.com/) build system and offers a convenient, graphical way to configure build options instead of having to memorize and type them out in the terminal. Due to incompatibility of its TUI library, cmeson only supports Linux, MacOS and other Unix-like systems. Consequently, if you want to use this application on Windows, you can do so through WSL or Cygwin. The name and functionality of this application are derived from a similar application for [cmake](https://cmake.org/) ccmake.

![showcase.png](https://raw.githubusercontent.com/proskur1n/cmeson/master/docs/showcase.png "cmeson showcase")

# Installation

From PyPI:

	pip3 install --user cmeson

From source:

	git clone https://github.com/proskur1n/cmeson
	cd cmeson
	pip3 install --user .

# Usage

	cmeson builddir
	cmeson [OPTIONS] builddir [sourcedir] [TRAILING]

	OPTIONS
		-h, --help               Show help message and exit
		--backend BACKEND        Select backend to query build options for

**sourcedir** is a directory containing *meson.build* file and **builddir** is the build directory for the project. **sourcedir** is only needed for projects for which *meson setup* has not been run yet and defaults to the current working directory if not specified.

The **--backend** option determines the list of options in the backend section and defaults to ninja. If you specify a backend using this option, you must not change the backend in TUI as this will result in an error from meson. See the meson documentation for a complete list of supported backends.

If any trailing options are given, they are passed as-is to meson and are not interpreted by this application. Normally you do not need to specify any trailing options as most of them can be configured directly through TUI.

# License

MIT License (see LICENSE for more information)
reconchess-tools 0.2.1
Tools for developing bots to play reconchess.
License: MIT
Requires Python: >=3.6.0


# reconchess-tools: utilities to aid bot development for reconchess

Getting started developing bots in python for the [Reconnaissance Blind Chess](https://rbc.jhuapl.edu/) competition from JHU APL is already simple thanks to the [reconchess](https://github.com/reconnaissanceblindchess/reconchess) package. The code in this repository builds on that foundation to make it equally easy to move beyond beginner bot development. It provides utilities for multi-hypothesis-tracking (MHT), MHT game replays, sense and move simulation, and dominated action detection.

See the example bot (reconchess_tools/example_bot/bot.py) for an overview of the capabilities included in this repository. You can run a local game and view the replay using the cli: `reconchess-tools bot-match reconchess.bots.trout_bot reconchess_tools.example_bot.bot`.
django-requestlog 1.1.8
Middleware to log http requests to postgresql
License: MIT

Django-Requestlog
=================

[![Quality Gate Status](https://sonarcloud.io/api/project_badges/measure?project=muehlemann-popp_requestlog&metric=alert_status)](https://sonarcloud.io/dashboard?id=muehlemann-popp_requestlog) [![Coverage](https://sonarcloud.io/api/project_badges/measure?project=muehlemann-popp_requestlog&metric=coverage)](https://sonarcloud.io/dashboard?id=muehlemann-popp_requestlog) 

Middleware who logs each request with their headers and the body into to PostgreSQL for diagnostic purposes. 


Why Logging to the database?
----------------------------
Logging to the database instead of to a logfile has the advantage that it can be 
searched by people not having access to the server logs. Of course this only works 
for low traffic sites. And I recommend to purge those logs regularly with the provided 
manage command or celery task.

What is logged?
---------------

The log is written to the table `requestlog_requestlog`.

* timestamp
* client IP address
* django user-id
* method
* URL
* header fields
* cookies
* query parameter
* POST body
* HTTP status code
* the first 1024 of the response

Credits
-------
Based on https://github.com/ASKBOT/django-request-logging


Settings
--------

Request logging has to be explicitely enabled (for performance reasons):

    REQUEST_LOGGING_ENABLED = True
    
You can ask the service to ignore certain fields from the querystring and the header. You do this by setting
the name of the fields in the Django settings variable `REQUEST_LOGGING_HIDE_PARAMETERS`. For example like this:

    REQUEST_LOGGING_HIDE_PARAMETERS = [ 'HTTP_AUTHORIZATION', 'password' ]

Filter certain IPs (e.g. internal Kubernetes health check requests)

    REQUEST_LOGGING_IGNORE_IPS = [ '10.2.3.4' ]

Filter certain paths by Regex (including query string):

    REQUEST_LOGGING_IGNORE_PATHS = [ '/admin/login' ]

Purge old entries
-----------------

You can use the following management command which deletes entries older than 3 days:

    ./manage.py requestlog_purge

Or you trigger the task with Celery beat by adding a shared task to your projects task list:

    
In your settings: 

    CELERY_BEAT_SCHEDULE = {
        ...    
        'requestlog.tasks.delete_old_requestlog_entries': {
            'task': 'requestlog.tasks.delete_old_requestlog_entries',
            'schedule': crontab(hour=2, minute=0)
            'args': (30,) # This is the number of days to keep the entries 
        },
    }