semvec/pypi-packages huggingface dataset:
micropython-doctest 0.0.0
Dummy doctest module for MicroPython
License: MIT

This is a dummy implementation of a module for MicroPython standard library.
It contains zero or very little functionality, and primarily intended to
avoid import errors (using idea that even if an application imports a
module, it may be not using it onevery code path, so may work at least
partially). It is expected that more complete implementation of the module
will be provided later. Please help with the development if you are
interested in this module.
micropython-dummy_threading 0.0.0
Dummy dummy_threading module for MicroPython
License: MIT

This is a dummy implementation of a module for MicroPython standard library.
It contains zero or very little functionality, and primarily intended to
avoid import errors (using idea that even if an application imports a
module, it may be not using it onevery code path, so may work at least
partially). It is expected that more complete implementation of the module
will be provided later. Please help with the development if you are
interested in this module.
micropython-dis 0.0.0
Dummy dis module for MicroPython
License: MIT

This is a dummy implementation of a module for MicroPython standard library.
It contains zero or very little functionality, and primarily intended to
avoid import errors (using idea that even if an application imports a
module, it may be not using it onevery code path, so may work at least
partially). It is expected that more complete implementation of the module
will be provided later. Please help with the development if you are
interested in this module.
micropython-configparser 0.0.0
Dummy configparser module for MicroPython
License: MIT

This is a dummy implementation of a module for MicroPython standard library.
It contains zero or very little functionality, and primarily intended to
avoid import errors (using idea that even if an application imports a
module, it may be not using it onevery code path, so may work at least
partially). It is expected that more complete implementation of the module
will be provided later. Please help with the development if you are
interested in this module.
micropython-bdb 0.0.0
Dummy bdb module for MicroPython
License: MIT

This is a dummy implementation of a module for MicroPython standard library.
It contains zero or very little functionality, and primarily intended to
avoid import errors (using idea that even if an application imports a
module, it may be not using it onevery code path, so may work at least
partially). It is expected that more complete implementation of the module
will be provided later. Please help with the development if you are
interested in this module.
micropython-atexit 0.0.0
Dummy atexit module for MicroPython
License: MIT

This is a dummy implementation of a module for MicroPython standard library.
It contains zero or very little functionality, and primarily intended to
avoid import errors (using idea that even if an application imports a
module, it may be not using it onevery code path, so may work at least
partially). It is expected that more complete implementation of the module
will be provided later. Please help with the development if you are
interested in this module.
micropython-ast 0.0.0
Dummy ast module for MicroPython
License: MIT

This is a dummy implementation of a module for MicroPython standard library.
It contains zero or very little functionality, and primarily intended to
avoid import errors (using idea that even if an application imports a
module, it may be not using it onevery code path, so may work at least
partially). It is expected that more complete implementation of the module
will be provided later. Please help with the development if you are
interested in this module.
micropython-array 0.0.0
Dummy array module for MicroPython
License: MIT

This is a dummy implementation of a module for MicroPython standard library.
It contains zero or very little functionality, and primarily intended to
avoid import errors (using idea that even if an application imports a
module, it may be not using it onevery code path, so may work at least
partially). It is expected that more complete implementation of the module
will be provided later. Please help with the development if you are
interested in this module.
ChoPy 0.0.0
Swiss Army knife for coder-musicians
License: MIT
Keywords: music midi play harmony

# ChoPy

Goal: Swiss Army knife for coder-musicians.

## Current Todo

This project is just getting started. I plan to write this thing for fun over a long period of time.

- Musical object cores: efficient representation of musical primitives.
- Find a cross-platform library for playing sounds.

https://mdoege.github.io/PySynth/

https://wiki.python.org/moin/Audio/

## Capabilities

A music modeling tool. Representation for music primitives. e.g. individual tone, chord, and multi-track compositions. Operations on primitives: concatenation, superposition, transformation, importing and exporting as different concrete formats. These musical objects should be easy to

ChoPy aims at fast experiments and . The actual serious work should be done in your favorite DAW.

## The Name

Idea: a famous musician's name + conventional suffix "py". Chopin sounds just right.
environmentalist 0.1.1
Accessing environment variables for lazy people.
License: MIT

# Environmentalist - use API secrets easily

Environmentalist helps API users to retrive API secrets from the environment
easily.

## The problem

I'm tired of rewriting the following code over and over again to get my app key
from the environment variables.

```python
import os
from requests_oauthlib import OAuth1Session
api = OAuth1Session(client_key=os.environ.get('TWITTER_CLIENT_KEY'),
                    client_secret=os.environ.get('TWITTER_CLIENT_SECRET'),
                    resource_owner_token=os.environ.get('TWITTER_RESOURCE_OWNER_TOKEN'),
                    resource_owner_secret=os.environ.get('TWITTER_RESOURCE_OWNER_SECRET'))
```

## Project dependencies

1. N/A

## Usage

Use an instance to easily create your API instance, for example:

```bash
# Create environment variables with the same prefix
set TWITTER_CLIENT_KEY=xxx
set TWITTER_CLIENT_SECRET=xxx
set TWITTER_RESOURCE_OWNER_TOKEN=xxx
set TWITTER_RESOURCE_OWNER_SECRET=xxx
```

```python
from environmentalist import E

api = OAuth1Session(**E(prefix='TWITTER'))

api.get('https://api.twitter.com/1.1/statuses/home_timeline.json')
```

When you create the `E` instance, it filter and strips the prefix out of the
environment variables.

Or you can dump all the environment variables for no reason:

```python
print(E())
# {'HOME': '...', ...}
```
phone-homer 0.0.1
DO NOT USE THIS MODULE!
License: MIT
Keywords: sample security tools

A sample Python project (original @ pypa/sampleproject)
=======================

This project is a appended sample, that phones home to a POST listener, to
demonstrate the ability to run Python code from the package installation
process.

----

A sample project that exists as an aid to the `Python Packaging User Guide
<https://packaging.python.org>`_'s `Tutorial on Packaging and Distributing
Projects <https://packaging.python.org/en/latest/distributing.html>`_.

This projects does not aim to cover best practices for Python project
development as a whole. For example, it does not provide guidance or tool
recommendations for version control, documentation, or testing.

----

This is the README file for the project.

The file should use UTF-8 encoding and be written using `reStructuredText
<http://docutils.sourceforge.net/rst.html>`_. It
will be used to generate the project webpage on PyPI and will be displayed as
the project homepage on common code-hosting services, and should be written for
that purpose.

Typical contents for this file would include an overview of the project, basic
usage examples, etc. Generally, including the project changelog in here is not
a good idea, although a simple "What's New" section for the most recent version
may be appropriate.