semvec/pypi-packages huggingface dataset:
plrs 0.1.5
The multi-tool of lexical analysis and tokenization.
License: MIT
Requires Python: >=3.6
Keywords: pyo3,lexer

# plrs <a href="https://pypi.org/project/plrs/">![Version](https://img.shields.io/pypi/v/plrs)</a>
The multi-tool of lexical analysis and tokenization.

# Install
```
pip install plrs
```

# Build
```
maturin build
```
# Examples
- [zipfs-law](https://github.com/JakeRoggenbuck/zipfs-law)

# API
#### Global variables
```
EOF_TOKEN
```

#### Classes
```
Tokens
Settings
Token
  - part
  - token
  - set_part
  - set_token
  - __str__
  - __repr__

Lexer
  - new
  - char_forward
  - skip_over_char_set
  - next
```

#### Functions
```
is_char_symbol
is_char_operator
is_char_whitespace
is_char_numeric
is_single_quote
is_double_quote
ends_token
is_part_numeric
tokenize
```
apos 0.2.1.2
The backbone for message-driven applications.
License: MIT
Requires Python: >=3.9,<4.0
Keywords: messenger,command,event,query,response

# apos

The backbone for message-driven applications.

## Summary
This Python library is designed to act as a software-level message broker, enabling a lightweight implementation of the publish-subscribe design pattern.

apos was born to accomplish two objectives:
* Decouple the application layer from any interfaces
* Develop reactive business functions

With apos, you can develop a message-driven application. This means that commands, events, and queries are sent to apos, which in return executes the functions that subscribe to these messages. This means that an adapter providing an external interface, may it be a web-API or a CLI, would not directly call application functions, but would rather send a message to apos, which will in return execute the business functions that subscribe to these messages. Equally, a business function would not call any other business function, but rather publishes an event, which other business functions can subscribe to and execute upon, controlled through apos.

![](https://miro.medium.com/max/652/1*ZTxTLfH0FWRIQLAZFlBGEQ.png)

## Context
See the Medium article linked below to read about why this library was created and how it is intended to be used. 
https://mkossatz.medium.com/a-backbone-for-message-driven-applications-ffdcef67824c


## Installation
The library can be found on PyPi:
https://pypi.org/project/apos/


```shell
pip3 install apos
```

## Getting Started

The code below is a very lightweight example of how you can use apos for commands, queries, and events. 

```python

from apos import apos


class RegisterUserCommand:
    pass


class UserRegisteredEvent:
    pass


class NewUserGreetedEvent:
    pass


class RetrieveUserQuery:
    pass


class RetrieveUserResponse:
    pass


def register_user(command: RegisterUserCommand) -> None:
    # Implementation of user registration
    apos.publish_event(
        UserRegisteredEvent())


def greet_new_user(event: UserRegisteredEvent) -> None:
    # Implementation of user greeting
    apos.publish_event(
        NewUserGreetedEvent())


def retrieve_user(query: RetrieveUserQuery) -> RetrieveUserResponse:
    # Implementation of user retrieval
    return RetrieveUserResponse()


# subscribing to messages (application configuration)
apos.subscribe_command(RegisterUserCommand, register_user)
apos.subscribe_event(UserRegisteredEvent, [greet_new_user])
apos.subscribe_query(RetrieveUserQuery, retrieve_user)

# some interface adapter
apos.publish_command(RegisterUserCommand())
events = apos.get_published_events()
print(events)
response: RetrieveUserResponse = apos.publish_query(RetrieveUserQuery())
print(response)


```



## Complete Examples

You can find examples in the examples directory of the projects repository.
https://github.com/mkossatz/apos/tree/main/examples
mkdocs-copy 0.0.1
A mkdocs plugin that lets you copy (and maybe transform) arbitrary doc files to the build.
License: MIT
Requires Python: >=2.7
Keywords: mkdocs markdown file copy include export transform

# Copy files in your MkDocs build

mkdocs-copy is a plugin for [MkDocs](https://www.mkdocs.org/) which allows you to copy _verbatim_ arbitrary files in your build.

## Why?

This plugin was created to solve https://github.com/mkdocs/mkdocs/issues/2139 (at least some use-cases affected by it). Basically it's a work-around for the following ([willingly](https://github.com/mkdocs/mkdocs/issues/2139#issuecomment-656659524)) hard-coded chunk in MkDocs' sources:

``` python
# mkdocs/structure/files.py used by 
def get_files(config):
    """ Walk the `docs_dir` and return a Files collection. """
    files = []
    exclude = ['.*', '/templates']

    # ...
```

Note: one could achieve the same result using something like [mkdocs-gen-files](https://oprypin.github.io/mkdocs-gen-files/) or [mkdcos-simple-hooks](https://pypi.org/project/mkdocs-simple-hooks/), only with some more effort. The benefit of using mkdocs-copy dedicated plugin lies in its declarative API. It is also easily reusable.

## Quick start

Say you want to add .htaccess files (if defined for a given folder/path):

``` yaml
# mkdocs.yml config file
plugins:
  - mkdocs-copy:
    add_per_path:
      - .htaccess
```
django-perms-provisioner-fuxy 0.0.6
Provision django instances with usergroups and permissions
License: MIT

==============================
Django Permissions Provisioner
==============================

.. image:: https://img.shields.io/badge/code%20style-black-000000.svg
    :target: https://github.com/ambv/black

.. image:: https://github.com/labd/django-perms-provisioner/workflows/Python%20Tests/badge.svg
    :target: https://github.com/labd/django-perms-provisioner/actions

.. image:: https://travis-ci.org/labd/django-perms-provisioner.svg?branch=master
    :target: https://travis-ci.org/labd/django-perms-provisioner

.. image:: http://codecov.io/github/labd/django-perms-provisioner/coverage.svg?branch=master
    :target: http://codecov.io/github/labd/django-perms-provisioner?branch=master

.. image:: https://img.shields.io/pypi/v/django-perms-provisioner.svg
    :target: https://pypi.org/project/django-perms-provisioner/


This package works like the standard Django loaddata / dumpdata commands only
it's used for creating auth.Group objects with their provided permissions.


Requirements
============

 - Python >= 3.6
 - Django >= 1.11

Installation
============

.. code-block:: shell

   pip install django_perms_provisioner_fuxy


Then the only thing left before you can start using the ``Django Permissions
Provisioner`` is adding it to you installed apps.

.. code-block:: python

  INSTALLED_APPS = [
      "django_perms_provisioner_fuxy",
  ]


Configuration
=============

Configuration can either be done via providing a ``YAML`` or ``JSON`` file. Your
file needs to have one of the following extensions: .json, .yaml, .yml, and
their approriate contents of course.

Examples:

.. code-block:: yaml

   ---
   groups:
     - name: Group Name
       permissions:
         sites:
            - site.add_site
            - site.change_site
          wagtailadmin:
            - admin.access_admin


.. code-block:: javascript

   {
     "groups" [{
       "name": "Group Name",
       "permissions": {
         "sites": ["site.add_site", "site.change_site"],
         "wagtailadmin": ["admin.access_admin"]
       }
     }]
   }


It is also possible to only create groups this can be done by just leaving out
the permissions.


Example:

.. code-block:: yaml

   ---
   groups:
     - name: Group Name
     - name: Next Group Name


Usage
=====

To load permissions from a configuration file

.. code-block:: shell

   ./manage.py loadperms permissions.yaml


Or to dump permissions to a configuration file

.. code-block:: shell

   ./manage.py dumpperms > permissions.yaml