Modified items

All recently modified items, latest first.

python-twisted-mail-12.0.0-1.fc18.armv6hl: Twisted is an event-based framework for internet applications. Twisted Mail contains high-level, efficient protocol implementations for both clients and servers of SMTP, POP3, and IMAP4. Additionally, it contains an "out of the box" combination SMTP/POP3 virtual-hosting mail server. Also included is a read/write Maildir implementation and a basic Mail Exchange calculator.

python-twisted-mail-11.0.0-1.lbn13.x86_64: Twisted is an event-based framework for internet applications. Twisted Mail contains high-level, efficient protocol implementations for both clients and servers of SMTP, POP3, and IMAP4. Additionally, it contains an "out of the box" combination SMTP/POP3 virtual-hosting mail server. Also included is a read/write Maildir implementation and a basic Mail Exchange calculator.

python-twisted-lore-12.0.0-1.fc18.armv6hl: Twisted is an event-based framework for internet applications. Lore is a complete documentation system based on XHTML and can generate documentation into other formats such as PDF, HTML.

python-twisted-lore-11.0.0-1.lbn13.x86_64: Twisted is an event-based framework for internet applications. Lore is a complete documentation system based on XHTML and can generate documentation into other formats such as PDF, HTML.

python-twisted-core-zsh-11.0.0-1.lbn13.x86_64: Tab completions for Zsh and Twisted Core.

python-twisted-core-doc-12.0.0-1.fc18.armv6hl: Documentation for Twisted Core.

python-twisted-core-doc-11.0.0-1.lbn13.x86_64: Documentation for Twisted Core.

python-twisted-core-12.0.0-1.fc18.armv6hl: An extensible framework for Python programming, with special focus on event-based network programming and multiprotocol integration. It is expected that one day the project will expanded to the point that the framework will seamlessly integrate with mail, web, DNS, netnews, IRC, RDBMSs, desktop environments, and your toaster. Twisted Core is used by most of the servers, clients and protocols that are part of other Twisted projects.

python-twisted-core-11.0.0-1.lbn13.x86_64: An extensible framework for Python programming, with special focus on event-based network programming and multiprotocol integration. It is expected that one day the project will expanded to the point that the framework will seamlessly integrate with mail, web, DNS, netnews, IRC, RDBMSs, desktop environments, and your toaster. Twisted Core is used by most of the servers, clients and protocols that are part of other Twisted projects.

python-twisted-conch-12.0.0-1.fc18.armv6hl: Twisted is an event-based framework for internet applications. Conch is an SSHv2 implementation written in Python. SSH is a protocol designed to allow remote access to shells and commands, but it is generic enough to allow everything from TCP forwarding to generic filesystem access. Since conch is written in Python, it interfaces well with other Python projects, such as Imagination. Conch also includes a implementations of the telnet and vt102 protocols, as well as support for rudamentary line editing behaviors. A new implementation of Twisted's Manhole application is also included, featuring server-side input history and interactive syntax coloring.

python-twisted-conch-11.0.0-1.lbn13.x86_64: Twisted is an event-based framework for internet applications. Conch is an SSHv2 implementation written in Python. SSH is a protocol designed to allow remote access to shells and commands, but it is generic enough to allow everything from TCP forwarding to generic filesystem access. Since conch is written in Python, it interfaces well with other Python projects, such as Imagination. Conch also includes a implementations of the telnet and vt102 protocols, as well as support for rudamentary line editing behaviors. A new implementation of Twisted's Manhole application is also included, featuring server-side input history and interactive syntax coloring.

python-twisted-11.0.0-1.lbn13.noarch: Twisted is an event-based framework for internet applications. It includes a web server, a telnet server, a chat server, a news server, a generic client and server for remote object access, and APIs for creating new protocols and services. Twisted supports integration of the Tk, GTK+, Qt or wxPython event loop with its main event loop. The Win32 event loop is also supported, as is basic support for running servers on top of Jython. Installing this package brings all Twisted sub-packages into your system.

python-suds-0.4-2.lbn13.noarch: Lightweight SOAP client

python-six-1.2.0-1.lbn13.noarch: python-six provides simple utilities for wrapping over differences between Python 2 and Python 3. This is the Python 2 build of the module.

python-pyip-0.7-1.lbn13.noarch

python-pyasn1-0.0.12a-2.lbn13.noarch: This project is dedicated to implementation of ASN.1 types (concrete syntax) and codecs (transfer syntaxes) for Python programming environment. ASN.1 compiler is planned for implementation in the future.

python-poster-0.8.1-3.lbn13.noarch: The modules in the Python standard library don't provide a way to upload large files via HTTP without having to load the entire file into memory first. poster provides support for both streaming POST requests as well as multipart/form-data encoding of string or file parameters.

python-novaclient-2.15.0-1.lbn13.noarch: This is a client for the OpenStack Nova API. There's a Python API (the novaclient module), and a command-line script (nova). Each implements 100% of the OpenStack Nova API.

python-networkx-1.6-1.lbn13.noarch: NetworkX is a Python package for the creation, manipulation, and study of the structure, dynamics, and functions of complex networks.

python-munin.zope-1.3.2-2.lbn13.noarch: Introduction ------------ This package provides munin plugins for monitoring various aspects of a Zope instance. It uses `gocept.munin`_ for plugin registration. Please refer to its documentation if you want to write new plugins. Bits of the code is based on plugins found at `munin exchange`_ (many thanks to Gaute Amundsen and Arthur Lutz). Plugins ------- Currently there are 4 plugins available: * "zopethreads" - reports free Zope threads * "zopecache" - reports database cache parameters * "zodbactivity" - reports ZODB activity * "zopememory" - reports Zope memory usage (only works on Linux) How to use it ------------- * First include the package in your buildout `instance` slot:: [instance] ... eggs = ... munin.zope zcml = ... munin.zope * To create the pluging helper script you'll also need to include the following, additional section and extend your `parts` definition:: [buildout] parts = ... munin [munin] recipe = zc.recipe.egg eggs = munin.zope arguments = http_address='${instance:http-address}', user='${instance:user}' The `arguments` option is used to pass configuration values to the generated helper script, which is then used as the actual munin plugin (see below). Any settings for `ip-address`, `http-address`, `port-base` and `user` given in the `instance` section should be repeated here, separated by commas. .. |---| unicode:: U+2014 .. em dash Please be aware, that the variable names use underscores instead of dashes here |---| the following list shows all supported settings and their respective default values: * ip_address='<ip-address>' ['localhost'] * http_address=<http-address> [8080] * port_base=<port-base> [0] * user=<user-credentials> [n.a.] Either literal values or references to the `instance` part can be used here, i.e. "http_address='${instance:http-address}', user='${instance:user}'". Please note that the resulting line will be verbosely copied into the generated `bin/munin` script, so the extra quoting is required. * When monitoring more than one Zope instance, i.e. in a ZEO setup, separate helper scripts need to be generated. In order to do so the `scripts` option of `zc.recipe.egg` can be used like so:: [buildout] parts = ... munin1 munin2 [munin1] recipe = zc.recipe.egg eggs = munin.zope scripts = munin=munin1 arguments = http_address='${instance1:http-address}', user='${instance1:user}' [munin2] recipe = zc.recipe.egg eggs = munin.zope scripts = munin=munin2 arguments = http_address='${instance2:http-address}', user='${instance2:user}' The necessary symlinks can then be created with each of the scripts in turn (see below). Please note, that in this case you should explicitly provide at least a differing `prefix` argument. * Now you should be able to call the plugins as follow:: http://localhost:8080/@@munin.zope.plugins/zopethreads Where `zopethreads` is you plugin name. Please note that for security reasons the view requires the `View management screens` permission. * Next you need to make symlinks from the helper script inside your buildout's `bin/` to the munin plugin directory. The helper script itself can assist you with this:: $ bin/munin install /opt/munin/etc/plugins [<prefix>] [<suffix>] This will install the necessary symlinks in the given directory using either the provided prefix and suffix or else the hostname and current directory to assemble their names (see below). Alternatively, you may also install the desired symlinks yourself:: $ cd /opt/munin/etc/plugins $ ln -s ~/zope/bin/munin company_zodbactivity_site1 Here `/opt/munin/etc/plugins` is your munin directory, `~/zope/` is the root directory of your buildout, `zodb_activity` the name of the plugin you want to enable, `company` a placeholder for an arbitrary prefix and `site1` the name which will be shown in munin. * Finally configure the plugin in munin (this step can be skipped if you have correctly set up the `arguments` option as described in step 2 above):: $ cd /opt/munin/etc/plugin-conf.d/ $ vi munin.zope.conf ... [company_*_site1] ... env.AUTH myuser:myuser ... env.URL http://localhost:8080/@@munin.zope.plugins/%s Here `myuser:myuser` are your Zope user credentials and `localhost:8080` your site url. Please check `munin`_ for more information about plugin configuration.

« Previous 20 items Next 20 items » 1 ... 2314 2315 2316 2317 2318 2319 2320 ... 2425


	Copyright © 2000-2025 Corporation of Balclutha Inc. All rights reserved.

Sections

Modified items