Saravanan666/pypi-org huggingface dataset:
Package: juicer
# Juicer## What is Juicer?From a Release Engineering point of view, Juicer is a collection of
tools for administering Pulp [1], a Fedora Hosted Project for managing
yum repositories.Juicer allows you to remotely manage repositories in multiple
environments such as QA, STAGE, or PROD as well as upload and promote
rpm packages through a Pulp installation.[1] Pulphttps://fedorahosted.org/pulp/## DownloadWe have a [public yum repository](http://tbielawa.fedorapeople.org/juicer/) set up for your convenience! We’ve even provided a [repo file](https://github.com/juicer/juicer/blob/master/docs/juicer.repo) that you can place in /etc/yum.repos.d/ . From there, run$ yum install juicer juicer-adminand you’re set!## Setting Up and Contributing[Installation](https://github.com/juicer/juicer/blob/master/docs/markdown/install.md)[Configuration](https://github.com/juicer/juicer/blob/master/docs/markdown/config.md)[Hacking](https://github.com/juicer/juicer/blob/master/docs/markdown/hacking.md)[RpmSignPlugins](https://github.com/juicer/juicer/blob/master/docs/markdown/plugins.md)[Repo Import/Exporting](https://github.com/juicer/juicer/blob/master/docs/markdown/import_export.md)## Examples### Prepare Pulp for use with JuicerWe assume that you have Pulp running already. Pulp ships with a default user whose name and password are both admin. If you’ve changed that, it’s fine. If not, Juicer provides an easy way to do so! Either way, put your account credentials in your juicer.conf. There’s really only two things left to configure Pulp for use with Juicer.First, you need to decide on how many Pulp environments you’re going to have. At least three (dev, qa, and prod) is recommended. Then, configure Juicer to use them.$ man juicer.confNow you’re ready to start creating release carts!### Upload an rpm into a repository$ juicer rpm upload -r juicy-software ~/Downloads/juicer-0.1.7-1.fc17.noarch.rpm### Example WorkflowStart by creating a release cartMyJuicyReleasewith items from the Internet:$ juicer cart create MyJuicyRelease -r juicy-softwarehttps://my.sweet.host/pulp/repos/dev/juicy-software/juicer-0.1.7-1.fc17.noarch.rpmThen push the cart and its contents to pulp:$ juicer cart push MyJuicyReleaseWhen you’re satisfied, promote the cart to the next environment
(perhapsstage, orproduction):$ juicer cart promote MyJuicyRelease
Package: juju-act
# Juju Act‘juju act’ is a Juju plugin to improve the actions command line user
experiece. It operates synchronously, combining the built inrun-actionandshow-action-outputcommands into one.This plugin supports Juju 1.25 and Juju 2.0. When a future version
of Juju gains a –wait argument to therun-actioncommand, it is
expected that this plugin will simply wrap that for backwards compatibility.
This work can be tracked athttps://bugs.launchpad.net/bugs/1445066## TODORun an action on the leader in a service, rather than on a specific unit.Run an action on all units in a service. Output and exit codes need
to be combined. Run Parallel (fast), serially (rolling upgrades), or
user choice?## Support‘juju act’ is maintained on Launchpad athttps://launchpad.net/juju-actby Stuart Bishop <stuart.bishop@canonical.com>. Bugs can be reported
athttps://bugs.launchpad.net/juju-actor to the main Juju mailing list.
Code can be found in git athttps://git.launchpad.net/juju-act
Package: jujubigdata
ThejujubigdataPython library is an
collection of functions and classes for simplifying the development ofJuju Charmsfor Big Data applications. It
includes utilities for:Interacting with Apache HadoopConnecting to the core Apache Hadoopplatform bundleReading and writing configuration in various formatsManaging distribution-specific configuration in a generalized, maintainable fashionPlease see thedocumentationfor
detailed information on how to use the Apache Hadoop Juju platform and this
library.Contact Informationbigdata@lists.ubuntu.comResourcesJuju Big Data repoApache Hadoophome pageApache Hadoop bug trackerApache Hadoop mailing listsApache Hadoop charmsJuju Big Data bug trackerJuju mailing listJuju community
Package: juju-deployer
Juju DeployerA deployment tool for juju that allows stack-like configurations of complex
deployments.It supports configuration in yaml or json.Installation$ virtualenv –system-site-packages deployer
$ ./deployer/bin/easy_install juju-deployer
$ ./deployer/bin/juju-deployer -hUsageStack DefinitionsHigh level view of v3 stacks:blog:
    series: precise
    services:
       blog:
         charm: wordpress
         branch: lp:charms/precise/wordpress
       db:
         charm: mysql
         branch: lp:charms/precise/mysql
    relations:
       - [db, blog]

 blog-prod:
    inherits: blog
    services:
       blog:
         num_units: 3
         constraints: instance-type=m1.medium
         options:
           wp-content: include-file://content-branch.txt
       db:
         constraints: instance-type=m1.large
         options:
           tuning: include-base64://db-tuning.txt
       cachelb:
         charm: varnish
         branch: lp:charms/precise/varnish
    relations:
       - [cachelb, blog]


We've got two deployment stacks here, blog, and blog-prod. The blog stack defines
a simple wordpress deploy with mysql and two relations. In this case itsVersion 4 bundles are currently under development.  The development document for
these types of bundles is availablehere.DevelopmentObtain source$ bzr branch lp:juju-deployer/darwin deployer
$ cd deployer# Test runner
$ python setup.py testBackgroundThis is a wrapper for Juju that allows stack-like configurations of complex
deployments.  It was created to deploy Openstack but should be able to deploy
other complex service configurations in the same manner.See deployments.cfg and deployments.cfg.sample for examples of how to describe
service stacks in JSON.
Package: juju-git-deploy
Juju Git Deploy is a Juju plugin which allows for easily deploying services
from local charms hosted on Github.
More information about Juju cloud orchestration tool can be found athttps://juju.ubuntu.com/.This plugin is mostly intended as a development tool, and can be useful for
testing charms which code base lives in Github. For a more comprehensive and
effective experience, take a look at theJuju GUI, which allows managing
Juju environments via a user-friendly Web interface, and supports deploying
local charms by dragging and dropping zip archives.Also seeJuju Quickstart: it is an easy to set up tool that quickly starts
Juju and the GUI, whether you’ve never installed Juju or you have an existing
Juju environment running.RequirementsJuju Git Deploy requires Python >= 3.3 and Juju >= 1.17.7.Python requirements are listed on therequirements.pipfile.This applications does not require git itself to be installed.InstallationThis plugin is registered on PyPI:sudo pip3 install juju-git-deployGetting startedBootstrap your Juju environment:juju bootstrapDeploy a charm from Github:juju git-deploy github.com/hatched/ghost-charmDone!The charm above can be deployed also copy/pasting the URL, e.g.:juju git-deploy https://github.com/hatched/ghost-charmOtherwise, it is possible to use the simplified{user}/{repo}form:juju git-deploy hatched/ghost-charmAt this point, thejuju statuscommand shows that a service is being
deployed using the specified local charm.Deploying a specific git branchTo deploy a specific git branch or reference, append a colon followed by
the reference identifier, e.g.:juju git-deploy frankban/ghost-charm:develop
juju git-deploy https://github.com/frankban/ghost-charm:developIf the reference is not specified, the repository’s default branch is used
(usuallymaster).Charm seriesTo deploy the charm on a specific OS series, provide the--series(or-s) argument, e.g.:juju git-deploy hatched/ghost-charm -s trustyIf--seriesis not specified the default environment series is used.Service nameThe service name can be provided as second positional argument:juju git-deploy hatched/ghost-charm:develop ghost-developIf omitted, the service name is derived from the charm name.Additional optionsOther options include-eto select the Juju environment,--toand--num-units. See the plugin help by running:juju help git-deployTODOSupport--constraints.
Package: jujuna
JujunaContinuous deployment, upgrade and testing for Juju.AtHUNT Cloudwe run our scientific services based on OpenStack orchestrated by Juju. Such cloud deployments rely on a large set of collaborative softwares, and upgrades can sometimes cause considerable pain. We have therefore introduced Jujuna - a tool to simplify the validation of Juju-based OpenStack upgrades.New toJuju? Juju is a cool controller and agent based tool from Canonical to easily deploy and manage applications (called Charms) on different clouds and environments (seehow it worksfor more details).InstallationEasy to install using:pip3 install jujunaMay require installation oflibssl-devpackage or equivalent if not present in the system.Run commandjujuna --helpto get the help menu. You can also check the usage inthe documentation.UsageRunning Jujuna requires a working deployment of Juju controller. Juju configs~/.local/share/juju/have to be present or credentials have to be specified using params.# Deploy Ceph bundle into ceph model
jujuna deploy openstack/bundle.yaml -m test-cloud -w

# Upgrade apps in ceph model_name
jujuna upgrade -m test-cloud

# Test apps in the model after upgrade
jujuna test tests/openstack-ocata.yaml -t 1800 -m test-cloud

# Destroy apps within a model, without destroying the model
jujuna clean -m test-cloud -w -f -t 1800If you don't have any bundle or just need to try jujuna with some simple example, you can follow ourexample guide.Testing JujunaHow to make sure jujuna and your feature works before pushing out new version.Testing jujuna with python environments:tox -e lint
tox -e py35
tox -e py36
tox -e py37Testing specific feature:py.test -k test_featureDeploy to docker registry:Build image:docker build -t registry.example.com/group/jujuna:0.2.1 -t registry.example.com/group/jujuna:latest .Push to registry:docker push registry.example.com/group/jujuna
Package: juju-quickstart
Juju Quickstart is an opinionated command-line tool that quickly starts Juju
and the GUI, whether you’ve never installed Juju or you have an existing Juju
environment running.Features include the following:New users are guided, as needed, to install Juju, set up SSH keys, and
configure it for first use.Juju environments can be created and managed from a command line interactive
session.The Juju GUI is automatically installed, adding no additional machines
(installing on an existing state server when possible).Bundles can be deployed, from local files, HTTP(S) URLs, or the charm store,
so that a complete topology of services can be set up in one simple command.Quickstart ends by opening the browser and automatically logging the user
into the GUI, to observe and manage the environment visually.Users with a running Juju environment can run the quickstart command again to
simply re-open the GUI without having to find the proper URL and password.To start Juju Quickstart, run the following:juju-quickstart [-i]Runjuju-quickstart-hfor a list of all the available options.Once Juju has been installed, the command can also be run as a juju plugin,
without the hyphen (juju quickstart).Supported VersionsJuju Quickstart is available on Ubuntu releases 12.04 LTS (precise), 14.04 LTS
(trusty), 15.04 (vivid), 15.10 (wily) and on OS X (10.7 and later).Starting from version 1.5.0, Juju Quickstart only supports Juju >= 1.18.1.Ubuntu InstallationFor installation on precise you’ll need to enable the Juju PPA by first
executing:sudo add-apt-repository ppa:juju/stable
sudo apt-get update
sudo apt-get install juju-quickstartFor trusty and above the PPA is not required and you simply need to install it
with:sudo apt-get install juju-quickstartAlternatively you may install Juju Quickstart via pip with:pip install juju-quickstartOS X InstallationYou may install Juju Quickstart via Homebrew or pip.  Seehttp://brew.shfor
instructions on installing Homebrew.To install Quickstart via Homebrew do the following:brew install juju-quickstartYou may also install via pip. Note that you’ll still need to have Homebrew
installed even if you use pip, because it is required to install Juju itself.
To install via pip do:pip install juju-quickstart
Package: jujuresources
Juju ResourcesJuju Resources provides helpers for charms to load binary resources from
external sources, as well as tools for creating mirrors of external resources
for network-restricted deployments.This is intended as a stop-gap until Juju has core support for resources,
as well as to prototype what features are needed.The full documentation is available online at:http://pythonhosted.org/jujuresources/InstallingInstall Juju Resources using pip:pip install jujuresourcesCharm UsageA charm using Juju Resources will need to define aresources.yaml,
such as:resources:
    my_resource:
        url: http://example.com/path/to/my_resource.tgz
        hash: b377b7cccdd281bc5e4c4071f80e84a3
        hash_type: sha256
    my_py:
        pypi: jujuresources>=0.2
optional_resources:
    my_optional_resource:
        url: http://example.com/path/to/my_optional_resource.tgz
        hash: 476881ef4012262dfc8adc645ee786c4
        hash_type: sha256Then, once the charm has installed Juju Resources, it can fetch
and verify resources, either in Python:from jujuresources import fetch, verify, install, config_get

if not fetch(mirror_url=config_get('resources_mirror')):
    print "Mandatory resources did not download; check resources_mirror option"
    sys.exit(1)
install('my_py')

fetch('my_optional_resource', mirror_url=config_get('resources_mirror'))
if verify('my_optional_resource'):
    install('my_optional_resource', destination='/usr/lib/myres', skip_top_level=True)Or via the command-line / bash:if ! juju-resources fetch -u `config-get resources_mirror`; then
    echo "Mandatory resources did not download; check resources_mirror option"
    exit 1
fi
juju-resources install my_py

juju-resources fetch -u `config-get resources_mirror` my_optional_resource
if juju-resources verify my_optional_resource; then
    juju-resources install my_optional_resource -D /usr/lib/myres -s
fiMirroring ResourcesIf you will need to deploy charms in an environment with limited network access,
you can create a mirror ahead of time, or on a gateway node which has access:mkdir local_mirror
juju-resources fetch --all -d local_mirror -r http://github.com/me/my-charm/blob/master/resources.yaml
juju-resources serve -d local_mirrorYou will then have a lightweight HTTP server running to which you can set the
charm’sresources_mirror(or equivalent) config option to point to,
serving all (--all, optional as well as required) resources defined in the
remoteresources.yaml(-r<url-or-file>), which are cached in thelocal_mirrordirectory (-dlocal_mirror).Note that the charms will need to be able to access the machine and port you run
the mirror on, and the charms must support a config option to point Juju Resources
to the mirror (as well as handle the possibility that their resources may not
be available when they are first deployed).
Package: juju-vnfm
This project is a Virtual Network Function Manager (VNFM) that enablesJujuto work as a VNFM in theOpen Batonenvironment.RequirementsPython 3.5.2+Juju 2.0+InstallationFor installing the Juju-VNFM executepipinstall.inside the project’s root directory.Notethat you have to use pip3 if
your standard Python interpreter is python2.UsageAfter you installed the Juju-VNFM you have to configure it. Create the
file/etc/openbaton/juju/conf.ini, make sure that the current user has write permissions for the file and execute:jujuvnfmconfigureThen follow the instructions.Afterwards you can start the Juju-VNFM with the commandjujuvnfm
start. You can specify the number of threads started to handle NFVO
requests by passing a number with the -t option:jujuvnfm-t10startThe default number of threads is five.
Package: juju-wait
This is a Juju plugin that provides the following new juju command:juju waitThis command waits until all hooks in the environment have completed
running and there are no more queued to run. It is primarily used by
deployment wrappers and test suites to know when a series on juju
commands (which run asynchronously) have completed and the system is
ready for the next step. Once the Juju environment has reached this
stable state, it will remain stable until some action destabalizes it,
such as operator action, machine reboots or scheduled tasks.
Package: juka-kernel
juka_kernelallows Juka to be run in Jupyter notebookInstallationNOTE: PATH to Juka must be defined, make sure it is defined prior to installing the kernelTo installjuka_kernelfrom this repository:python -m juka_kernel.installInstall from PyPi:pip install juka_kernelUsing the Juka kernelNotebook: TheNewmenu in the notebook should show an option for an Juka notebook.Console frontends: To use it with the console frontends, add--kerneljukato
their command line arguments.Uninstall Juka KernelRun the following command to uninstalljuka_kernel:jupyter kernelspec uninstall jukaCompile Juka .whl (Development Only)Run the following command:python -m buildUpload to PyPi (Internal Use Only)Run the following command:python -m twine upload dist/*
Package: jukebox-core
This is the core package for the jukebox cg-pipeline.
It is a framework for developing pipeline tools for different softwares in python.DocumentationThe documentation can be found underhttp://pythonhosted.org/jukebox-core.History0.1.0 (2014-09-27)Migration from old project1.0.3 (2014-10-23)First release on PyPI1.0.4 (2014-10-24)Fix for missing dependencyDocumentation hosted on pythonhosted.org2.0.0 (2014-11-10)Release mechanism.Fixes for widgetdelegate.Browser for taskfiles.Qt resource files compilation and proper integration in stylesheets.3.0.0 (2015-01-09)Reference workflowFixes for widgetdelegate3.3.0 (2015-05-29)Better ui for project management
Package: jukeboxmaya
Jukebox Pipeline for Maya. Jukebox Pipeline is a framework for developing pipeline tools for different softwares in python.
It is centered around theJukebox Core Package.DocumentationThe documentation can be found here:http://pythonhosted.org/jukeboxmayaHistory0.1.0 (2014-10-08)Mirgation of old project1.0.0 (2014-10-24)First release on PyPI2.0.0 (2014-10-24)Release for work files3.0.0 (2015-01-09)Reference workflow3.3.0 (2015-05-29)Release picks up last file from genesis
Package: jukebox-shout
Jukebox shoutcast streaming playback modulejukebox-shout provides a daemon to stream your music to a shoutcast compatible server likeicecastBasic setup instructions for icecast can be found in theirdocumentationRequired system librarieslibshout3, libshout3-dev and python-dev are required to build the dependecypython-shout.Startupbin/jukebox jukebox_shout --start --host=[shoutcast_host] --port[shoutcast_port] --password=[shoutcast_source_password]Stopbin/jukebox jukebox_shout --stopDebuggingAdd the –fg option to prevent the command from daemonizing.bin/jukebox jukebox_shout --fg --host=[shoutcast_host] --port[shoutcast_port] --password=[shoutcast_source_password]
Package: jukedj
Django app for models used in the JukeboxPipeline.DocumentationThe documentation can be found underhttp://pythonhosted.org/jukedj.History0.1.0 (2014-10-03)Migration of old project1.1.1 (2014-10-23)First release on PyPI2.0.0 (2014-11-17)Assets can be connected to each other.
Package: julearn
julearnAboutThe Forschungszentrum Jülich Machine Learning LibraryCheck our full documentation here:https://juaml.github.io/julearn/index.htmlIt is currently being developed and maintained at theApplied Machine Learninggroup atForschungszentrum Juelich, Germany.InstallationUsepipto install from PyPI like so:pip install julearnLicensingjulearn is released under the AGPL v3 license:julearn, FZJuelich AML machine learning library.
Copyright (C) 2020, authors of julearn.This program is free software: you can redistribute it and/or modify
it under the terms of the GNU Affero General Public License as published by
the Free Software Foundation, either version 3 of the License, or any later version.This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
GNU Affero General Public License for more details.You should have received a copy of the GNU Affero General Public License
along with this program.  If not, seehttp://www.gnu.org/licenses/.CitingIf you use julearn in a scientific publication, please use the following referenceHamdan, Sami, Shammi More, Leonard Sasse, Vera Komeyer, Kaustubh R. Patil, and Federico Raimondo. ‘Julearn: An Easy-to-Use Library for Leakage-Free Evaluation and Inspection of ML Models’. arXiv, 19 October 2023.https://doi.org/10.48550/arXiv.2310.12568.Since julearn is also heavily reliant on scikit-learn, please also cite them:https://scikit-learn.org/stable/about.html#citing-scikit-learn
Package: jules
Jules is a static blog generator named after a victorian-ish era literary or
intellectual character, because apparently that’s a trend now.Jules processes a list of input directories calledpacks. A fewpacksare
included to provide useful parts of a website. As of this time, Jules ship with
HTML5 Boilerplate, LESS CSS, Bootstrap, and Atom XML Feeds.Files from the sourcepacksare grouped by their base name, the filename
without extensions. A bundle could include a YAML configuration file, a Jinja2
template, or other files. The bundles of files are processed together to
output files. By default, the files in the bundle are simply copied.Restructured text files in a bundle are parsed as thebundle content, YAML
files are parsed as thebundle meta data, and Jinja2 templates are used to
render output HTML.PacksBundlesFilesHTML5 Boiler Packbase
js/jquery.minbase.j2
lib/jquery.min.jsLESS CSS Packjs/less.minjs/less.min.jsYour site packsite_basesite_base.j2indexindex.j2index.rst
Package: julesTk
========Jules-tk========A small MVC Framework for Tkinter.The model is Thread-safe, but since Tk is not thread safe, the view and controllers are not thread-safe.In threaded applications; use different threads to update the model and run a polling (using view.after) to updatethe view.Design structure================MVC: Model-View-Controller, is a well-known and wide practiced design paradigm for designing Graphical User Interfaces (GUI's).Jules-tk provides the MVC structure, similar to what web-frameworks as django do. There is one entry-point to the application(app.py) which will load controllers. The controllers will then initialize the models it needs and the view it works with.The Controller--------------Controller serve as the logic hub of the application and bridge from view and model.The View--------* Frame: Non-interacting Frame widget.* View: interacting, requires a controller.* ViewSet: combine multiple views into one window.The Model---------Models store and manipulate data contained by the application. They also serve as a gateway in multi-threadedapplications: Meaning, multiple threads can share information via the Model. One could - for example - use threads tomanipulate the Model, while the View and Controller are updated in the MainThread using the Model.Observer and Observable=======================The observer-observable paradigm enables objects to notify other objects upon an important change.Models are by default observable, but Controllers need to inherit the Observer class.See the `click_me` example for a demonstration of this paradigm.Be aware that this paradigm is not easy to implement in multi-threaded applications. In those cases it may be betterto use a polling mechanism in the MainThread to periodically update the View.Application flow================1. app.py, calls a controller2. controller loads model3. controller loads view4. app.py enters mainloop5. app.py exits mainloop6. app.py asks controllers to stop7. controller asks view to stopWhile in the main loop1. view receives to user input2. view calls controller3. controller handles input - acts on model5. controller handles update - acts on viewPlotting========Basic plotting is implemented using matplotlib with the `plot.Plot` Widget.See the `random_plot` example for a demonstration.