Personal tools
Skip to content. | Skip to navigation
PyJUnitXML ========== A Python unittest TestResult that outputs JUnit compatible XML. Copyright --------- PyJUnitXML is Copyright (c) 2009 Robert Collins, and distributed under the GNU Library General Public Licence version 3 (LGPL-3). Broadly, this means you have the right to use this library in any application you want, regardless of the licence of your application, but that if you modify ...
Install the Jupyter system, including the notebook, qtconsole, and the IPython kernel.
An IPython-like terminal frontend for Jupyter kernels in any language.
jupyter_client contains the reference implementation of the [Jupyter protocol][]. It also provides client and kernel management APIs for working with kernels. It also provides the jupyter kernelspec entrypoint for installing kernelspecs for use with Jupyter frontends.
JupyterHub is a multi-user server that manages and proxies multiple instances of the single-user IPython Jupyter notebook server. Three actors: multi-user Hub (tornado process) configurable http proxy (node-http-proxy) multiple single-user IPython notebook servers (Python/IPython/tornado) Basic principles: Hub spawns proxy Proxy forwards ~all requests to hub by default Hub handles login, and spawns single-user servers on demand Hub configures proxy to forward url prefixes to single-user servers
This module provides low-level protocol support for Apache Kafka as well as high-level consumer and producer classes. Request batching is supported by the protocol as well as broker-aware request routing. Gzip and Snappy compression is also supported for message sets.
Kamcli uses a configuration file with INI format. The name is kamcli.ini and it looks for it in: /etc/kamcli/kamcli.ini ~/.kamcli/kamcli.ini the value of --config command line parameter The installation process doesn't deploy the configuration file yet. A sample kamailio.ini is available in sources, at kamcli/kamcli.ini Note that not all configuration file options in kamcli.ini are used at this moment, some values are hardcoded, being planned to be replaced with the configuration options. Usage Read the help messages: $ kamcli --help $ kamcli <command> --help $ kamcli <command> <subcommand> --help Examples of Commands Sample commands to understand quicker the capabilities and how to use it: kamcli -v --config=kamcli/kamcli.ini --help kamcli --config=kamcli/kamcli.ini subscriber show kamcli --config=kamcli/kamcli.ini subscriber add test test00 kamcli --config=kamcli/kamcli.ini subscriber show test kamcli --config=kamcli/kamcli.ini subscriber show --help kamcli -v --config=kamcli/kamcli.ini subscriber passwd test01 test10 kamcli -v --config=kamcli/kamcli.ini subscriber add -t no test02 test02 kamcli -v --config=kamcli/kamcli.ini subscriber setattrs test01 rpid +123 kamcli -v --config=kamcli/kamcli.ini subscriber setattrnull test01 rpid kamcli -v --config=kamcli/kamcli.ini mi kamcli -v --config=kamcli/kamcli.ini mi which kamcli -v --config=kamcli/kamcli.ini mi get_statistics all kamcli -v --config=kamcli/kamcli.ini jsonrpc --help kamcli -v --config=kamcli/kamcli.ini jsonrpc core.psx kamcli -v --config=kamcli/kamcli.ini jsonrpc system.listMethods kamcli -v --config=kamcli/kamcli.ini jsonrpc stats.get_statistics kamcli -v --config=kamcli/kamcli.ini jsonrpc stats.get_statistics all kamcli -v --config=kamcli/kamcli.ini jsonrpc stats.get_statistics shmem: kamcli -v --config=kamcli/kamcli.ini jsonrpc --dry-run system.listMethods kamcli -v --config=kamcli/kamcli.ini config raw kamcli -v --config=kamcli/kamcli.ini config show main db kamcli -v --config=kamcli/kamcli.ini --no-default-configs config show main db kamcli -v --config=kamcli/kamcli.ini db connect kamcli -v --config=kamcli/kamcli.ini db show -F table version kamcli -v --config=kamcli/kamcli.ini db show -F json subscriber kamcli -v --config=kamcli/kamcli.ini db showcreate version kamcli -v --config=kamcli/kamcli.ini db showcreate -F table version kamcli -v --config=kamcli/kamcli.ini db showcreate -F table -S html version kamcli -v --config=kamcli/kamcli.ini db clirun "describe version" kamcli -v --config=kamcli/kamcli.ini db clishow version kamcli -v --config=kamcli/kamcli.ini db clishowg subscriber kamcli -v --config=kamcli/kamcli.ini ul showdb kamcli -v --config=kamcli/kamcli.ini ul show kamcli -v --config=kamcli/kamcli.ini ul rm test kamcli -v --config=kamcli/kamcli.ini ul add test sip:test@127.0.0.1 kamcli -v --config=kamcli/kamcli.ini stats kamcli -v --config=kamcli/kamcli.ini stats usrloc kamcli -v --config=kamcli/kamcli.ini stats -s registered_users kamcli -v --config=kamcli/kamcli.ini stats usrloc:registered_users
Kazoo is a Python library designed to make working with Zookeeper a more hassle-free experience that is less prone to errors.
Kegbot is a hardware and software system to record and monitor access to a beer kegerator. For more information and documentation, see http://kegbot.org/ Keg and Tap Management: Add and configure taps, assign kegs to taps, track remaining volume on active kegs, and mark empty kegs as finished. Kegbot has been designed with multi-tap systems in mind; a single install can support as many taps as you have. Account System: Full username/password account system, supporting registration, login, and password recovery. Drinker Authentication: Drinkers can be given physical tokens, such as RFIDs, to authenticate to the server during a pour. Pour Authorization and Shutoff: Optionally, your system can require that the server authorize each pour, only allowing access (by opening a valve) after the drinker is approved. Stats and Charts: Comprehensive statistics are calculated and recorded at each pour, and the web interface draws colorful charts. Drinking Sessions: As each drink is recorded, Kegbot assigns it to a discrete “drinking session” along with nearby drinks, and the server displays these sessions at a stable URL. Did you throw a party? Share a single URL that shows all the people and activity from that session. Database Backend: All Kegbot data, from basic drink information to derived statistics and user accounts, gets stored in a database (MySQL, or any other database supported by Django). JSON API: You can build your own frontend or other client interface using the Kegbot API. Drinks, tap status, user information, and almost every other interesting object in Kegbot is exposed this way. The same API is used for recording drinks. Web Hooks: The server can notify an arbitrary URL whenever there is activity such as a pour or new keg. You can bridge Kegbot to external services this way. Image Support: Users can upload profile pictures, and photos can be attached to drinks (something the Kegtab Android App does automatically). Sound Support: Assign short mp3s to play during certain events, such as when a user taps his RFID or pours more than 16oz. It’s fun! Twitter, Facebook, Foursquare, and more: Kegbot has hooks for a growing number of external/social sites. Users can link their Twitter, Facebook, Foursquare, or Untappd accounts, and configure automatic posting for each drink poured (or just at the start of a new session). Beer Database: A built-in database lets tag kegs by brewer and beer type. You can add entries for commercial or homebrew beers.