Skip to main content

Pluggable namespaces

This project has been archived.

The maintainers of this project have marked this project as archived. No new releases are expected.

Project description

Pluggable Namespace

Pluggable Namespace is a lightweight, modular framework for building pluggable software architectures with namespaces. It empowers you to build applications that are easily extendable, with seamless integration of multiple modules. Whether you’re creating quick one-off scripts or a fully-fledged modular application, this framework provides the flexibility you need.

Installation

You can install pluggable-namespace from PyPI:

pip install pluggable-namespace

Quick Start

With Pluggable Namespace, you can write a single Python file and start building immediately.

Create a Python file called my_file.py with the following content:

def main(hub):
    print("Hello World!")

Then you can run your script from the CLI with the hub:

hub -f my_file.py my_file.main

That’s it! This will execute the main function in my_file.py, and you will see “Hello World!” printed to the console. This is the simplest way to get started with Pluggable Namespaces.

The Hub

The hub is the core of the pluggable namespace framework. It provides a unified interface to access all the modules and functions in your application. The hub is implicitly passed to every function in your application, allowing you to access all the modules and functions in your application. You can use the hub to access any module or function in your application, as well as any external modules you have imported. The hub is a singleton, meaning that there is only one instance of the hub in your application. You can access the hub from anywhere in your application, and it will always be the same instance.

Configuration

When building a pluggable-namespace app, all configuration settings are stored in a config.yaml file.

Here’s an example of what a config.yaml might look like:

# App configuration options for your namespaces that will show up under hub.OPT.my_namespace
config:
  my_namespace:
    my_opt:
      os: MY_OPT_ENVIRONMENT_VARIABLE_NAME
      default: True

# Python imports that your app uses, to be added to hub.lib for your app
import:
  - asyncio
  - os
  - toml

The config.yaml file provides a way to manage configuration, subcommands, and imports for your app. It will be automatically loaded based on the location of your Python files when running the hub.

Extending Namespaces

You can extend Pluggable Namespace locally or via PyPI.

Locally

Extending pluggable-namespace is straightforward with dynamic namespaces. Extend any dynamic namespace on the hub by adding a directory containing a config.yaml to PYTHONPATH.

For example:

  1. Add a config.yaml to a directory:

# /path/to/project_root/config.yaml
dyne:
  namespace:
    - foo
  1. Update your PYTHONPATH:

export PYTHONPATH=$PYTHONPATH:/path/to/project_root

Now, every Python file in /path/to/project_root/foo will be added to the hub under hub.namespace.

With PyPI

To jump-start your project, you can use the seed command to generate all the necessary boilerplate code for a pluggable namespace application:

hub seed.init.cli /path/to/project_root name=my_project

Then, add your Python code to /path/to/project_root/src/my_project. This will set up all the boilerplate code for your project in a way that will make it merge automatically onto the hub when installed from PyPi.

Example of Using the Hub

After setting up your project, you can make use of the hub to call functions and access modules easily.

Here’s a more complex example showing how you can use the hub to access functions, shell commands, and configuration options:

# my_file.py
async def func(Hub):
    print("Hello World!")

async def main(hub):
    # Call a function in your python file from the hub
    await hub._.func()

    # Access a python module
    print(hub.lib.os.name)

    # Shell out
    await hub.sh.ls("-l")
    await hub.sh["ls"]("-l")

    # If you specified another file with "-f other_file.py" on the CLI, you can access its members like this
    await hub["other_file"].func()

    # Access a config option
    print(hub.OPT.my_namespace.my_opt)

Then you can run your script from the CLI with the hub:

hub -f my_file.py my_file.main

This will execute the main function, calling functions from other files, accessing Python modules, and using configuration options set in config.yaml.

Summary

Pluggable Namespace gives you the power to create modular, easily extendable applications without unnecessary complexity.

  1. Start Simple: Create one Python file with minimal boilerplate, add hub to your functions, and run it directly from the command line.

  2. Add Flexibility: Use config.yaml to scale your project with configuration settings, subcommands, and dynamic namespaces.

  3. Extend Easily: Whether you’re extending locally or using PyPI, it’s easy to integrate new modules and expand your app’s functionality.

For published packages that extend the hub, check out the detailed documentation for more advanced configurations and features.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distributions

No source distribution files available for this release.See tutorial on generating distribution archives.

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

pluggable_namespace-2.0.1-py3-none-any.whl (413.4 kB view details)

Uploaded Python 3

File details

Details for the file pluggable_namespace-2.0.1-py3-none-any.whl.

File metadata

File hashes

Hashes for pluggable_namespace-2.0.1-py3-none-any.whl
Algorithm Hash digest
SHA256 abe3357a003ef54fec913d80417e6c80c0808f91f6c8046f212bfbee5c17f521
MD5 678bbbfa01168949470c87a88822dd35
BLAKE2b-256 4114d9c24bb90fd0618ad63bef64c0ad7769449f61ab7094901f5b81e20e9f82

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page