semvec/pypi-packages huggingface dataset:
pipnest 0.0.2
Distribute your extension module as a pip installable package
License: MIT
Keywords: nest-simulator packaging module extension nest pip

# pipnest


<span class="title-ref">pipnest</span> packages your NEST extension
modules into pip installable packages. This is a benefit when you're
distributing a Python model for the NEST simulator and have a dependency
on an extension module. Instead of having to provide installation
instructions to your end-users you can have pip download and build the
extension module into the target machine's nest installation.

# Usage

## Project structure

  - Prepare a folder with 1 subfolder that contains a NEST extension
    modules.
  - The source code of the extension module can not be in the root
    repository.
  - The name of your module should be the name of your folders plus
    "module".

Your project structure should look like this:

    - my_module
      - my_module
        - my_file1.cpp
        - my_file2.cpp
        - ...

In this example your NEST module should be called the `my_modulemodule`.

## Initialize project

Run the `pipnest init` command from the root folder and fill in the
requested metadata:

    cd my_module
    pipnest init .

This should create a setup.py and README.md, be sure to edit the latter.
Check that your module is present under the `packages` keyword argument
in `setup.py`.

## Package

Create the source distribution:

    python setup.py sdist

### Test your package locally

  - Remove any already installed versions from the
    `$NEST_INSTALL_DIR/lib/nest` folder
  - Run `pip install dist/*`. (If an MPI error occurs, restart your
    terminal and try again)

## Upload to PyPI

Use twine to upload your package:

    twine upload dist/* --skip-existing
extra-cereb-nest 0.0.1
pip installable NEST extension module, generated by pipnest.
License: MIT

# extra_cereb_nest

pip installable NEST extension module, generated by pipnest.

## Installation instructions

### Using pip

When installed through pip the module is built for you with CMake outside of the python
package folder, this means that pip cannot track the real installation status. To
uninstall and reinstall see [Uninstallation](Uninstallation).

0. Install NEST following the instructions provided here (https://www.nest-simulator.org/)

1. Install using pip

```
pip install extra_cereb_nest --no-cache-dir
```

3. Load the module after importing nest:

```
import nest
nest.Install("extracerebmodule")
```

## Uninstallation

To uninstall this module use `pip uninstall extra_cereb_nest` and remove the
`(lib)extracerebmodule.so` files from the `lib/nest/` directory in your nest installation.
ems-deploy 0.0.13
A small deploy utility package
License: MIT
Requires Python: >=3.6

# EMS Deploy script

This project provides a general-purpose deploy script for the EMS projects. It runs the suitable docker-compose command based on the available docker-compose files located in the directory.

## Install

`pip install ems-deploy`

## Directory structure and required files
Deploy concatenates a `docker-compose` command.

`docker-compose.yml` Required.
`docker-compose.deploy.yml` Default if no tags are given when running the command.
`docker-compose.<tag1>.<tag2>.<etc>.yml` Optional. Notice there can be any number of tags.

## How to use
`deploy [-h] [-d] [-v] [--dry-run] [--flags "<flag1> <flag2>"] [tag]`

If a tag is supplied, it will append all parent-tags too, and they are required. I.e. if we
run the command `deploy debug.test`, it will add (and require) the following three files
```
docker-compose.yml
docker-compose.debug.yml
docker-compose.debug.test.yml
```

Notice one can also use the full file as a tag. That is, the following command will give the same result
`deploy docker-compose.debug.test.yml`.

The first level tag will be used as the project name, i.e. the `docker-compose -p` command.

### Configuration file 
An argument string can be saved to a file named `.ems-deploy`.
The arguments in this string will then automatically be added to the `deploy`-command. 
Additional arguments to the `deploy`-command will overwrite the commands from the configuration file.

### Notes

The following flags are always added to the `docker-compose` command:

 - `--force-recreate`
 - `--renew-anon-volumes`
 - `--build`

If the first level tag is `deploy`, the `-d` is automatically added.

### Deploy
To deploy the app with `docker-compose.yml` and `docker-compose.deploy.yml`, simply run

`deploy`

### Additional flags

 - `-d` Detaches the process (this is automatically done in deploy-mode, but not in debug-mode)
 - `-v` Writes the resulting command to the terminal.
 - `--dry-run` Will not execute the command
 - `--flags` Change default flags. Must specify a sting afterwards, e.g. `--flags "--force-recreate --build"`
django-dmcadmin 0.1.1
Django Manage Command Admin - a web-based app for managing the execution of Django manage commands.
License: MIT

===========================
Django Manage Command Admin
===========================

DMCAdmin is a web-based app for managing the execution of Django manage commands.

Store your manage commands in a table, run async through the web and view the result.

Quick start
-----------

1. pip install django-dmcadmin

2. Add "dmcadmin" to your INSTALLED_APPS setting like this::

    INSTALLED_APPS = [
        ...
        'dmcadmin',
    ]

3. Include the dmcadmin URLconf in your project urls.py like this::

    url(r'^dmcadmin/', include('dmcadmin.urls')),

4. Run `python manage.py migrate` to create the dmcadmin models.

5. Start the development server and visit http://127.0.0.1:8000/dmcadmin/
   to run manage command.