semvec/pypi-packages huggingface dataset:
pysimplegui-exemaker 1.3.0
A GUI Front-end to PyInstaller

# PySimpleGUI-exemaker

## Introduction
This package contains a GUI front-end to PyInstaller.  Use this tool to create EXE files from your python programs

  ![snag-0086](https://user-images.githubusercontent.com/13696193/46968655-c2103200-d081-11e8-926f-d5f977e726f3.jpg)




## Installing

When you install PySimpleGUI-exemaker, it will install the other components that it requires. To install, on windows, type this into a command prompt:

    pip install pysimplegui-exemaker


## PySimpleGUI Project

This program was built as a sample application of the PySimpleGUI GUI Framework.


## Running the program

After your pip install, type this into your command prompt:

  python -m pysimplegui-exemaker.pysimplegui-exemaker
py-citus-loader 2.1.0
A python command line tool to provide the commands necessary to run on citus to have a balanced cluster
Requires Python: >=3.5
Keywords: postgresql citus dump restore

# Citus loader

Citus loader is a tool that will allow you to do dump and restore on citus formations.

Here is how it works:

## citus-dump

The command citus-dump will:

- Do a schema dump of your formation
- Create a file with the distribute statements
- Take a pg_dump of each of your nodes and coordinator.

Here are the options you can configure:


- host: should the the host of your initial formation
- db: database you want to dump
- port: default 5432
- pwd: password
- pg_dump: if necessary, the path to the pg_dump you want to use
- pg_dump_jobs: value of the --jobs argument in pg_dump
- parallel_tasks: number of pg_dump tasks running in parallel
- dump_schema: default True, take a pg_dump of the schema
- dump_data: default True, take a pg_dump of the data
- ignore_write_locks: by default, citus-dump will try to lock the tables to ensure that before running pg_dump, no insert/update/delete statement is running on the workers.
- config_file: path to your yaml file with the configuration for the citus-dump command


We strongly recommend using a yaml configurattion file. You can find an example in tests/configuration.yml

## citus-restore

On your destination formation, citus-restore will:

- Restore the schema
- Distribute the tables
- Restore the shards to their appropriate worker.


- host: should the the host of your destination formation
- db: database you want to reestore
- port: default 5432
- pwd: password
- pg_restore: if necessary, the path to the pg_dump you want to use
- pg_restore_jobs: value of the --jobs argument in pg_restore
- parallel_tasks: number of pg_dump tasks running in parallel
- restore_schema: default True, restores the schema and distribute the tables
- restore_data: default True, does a pg_restore of the shards data
- config_file: path to your yaml file with the configuration for the citus-restore command


We strongly recommend using a yaml configurattion file. You can find an example in tests/configuration.yml
tricircle 8.0.0
The Tricircle is to provide networking automation across Neutron in multi-region OpenStack deployments.

========================
Team and repository tags
========================

.. image:: https://governance.openstack.org/tc/badges/tricircle.svg
    :target: https://governance.openstack.org/tc/reference/tags/index.html

.. Change things from this point on

=========
Tricircle
=========

The purpose of the Tricircle project is to provide networking automation
across Neutron servers in multi-region OpenStack clouds deployment.

Each OpenStack cloud includes its own Nova, Cinder and Neutron, the Neutron
servers in these OpenStack clouds are called local Neutron servers, all these
local Neutron servers will be configured with the Tricircle Local Neutron
Plugin. A separate Neutron server will be installed and run standalone as
the coordinator of networking automation across local Neutron servers, this
Neutron server will be configured with the Tricircle Central Neutron Plugin,
and is called central Neutron server.

Leverage the Tricircle Central Neutron Plugin and the Tricircle Local Neutron
Plugin configured in these Neutron servers, the Tricircle can ensure the
IP address pool, IP/MAC address allocation and  network segment allocation
being managed globally without conflict, and the Tricircle handles tenant
oriented data link layer(Layer2) or network layer(Layer3) networking
automation across local Neutron servers, resources like VMs, bare metal or
containers of the tenant can communicate with each other via Layer2 or Layer3,
no matter in which OpenStack cloud these resources are running on.

Note: There are some our own definitions of Layer2/Layer3 networking
across Neutron. To make sure what they are, please read our design
documentation, especially "6.5 L2 Networking across Neutron". The wiki and
design documentation are linked below.

The Tricircle and multi-region OpenStack clouds will use shared
KeyStone(with centralized or distributed deployment) or federated KeyStones.

The Tricircle source code is distributed under the terms of the Apache
License, Version 2.0. The full terms and conditions of this license are
detailed in the LICENSE file.

* Free software: Apache license
* Design documentation: `Tricircle Design Blueprint <https://docs.google.com/document/d/1zcxwl8xMEpxVCqLTce2-dUOtB-ObmzJTbV1uSQ6qTsY/>`_
* Wiki: https://wiki.openstack.org/wiki/tricircle
* Installation guide: https://docs.openstack.org/tricircle/latest/install/index.html
* Admin guide: https://docs.openstack.org/tricircle/latest/admin/index.html
* Configuration guide: https://docs.openstack.org/tricircle/latest/configuration/index.html
* Networking guide: https://docs.openstack.org/tricircle/latest/networking/index.html
* Source: https://opendev.org/openstack/tricircle
* Bugs: https://bugs.launchpad.net/tricircle
* Blueprints: https://blueprints.launchpad.net/tricircle
* Release notes: https://docs.openstack.org/releasenotes/tricircle
* Contributing: https://docs.openstack.org/tricircle/latest/contributor/index.html