You are here: Home

Modified items

All recently modified items, latest first.
RPMPackage python2-matplotlib-qt4-2.2.3-3.lbn25.x86_64
Qt4 backend for python-matplotlib
RPMPackage python2-matplotlib-gtk3-2.2.3-3.lbn25.x86_64
GTK3 backend for python-matplotlib
RPMPackage python2-matplotlib-gtk-2.2.3-3.lbn25.x86_64
GTK backend for python-matplotlib
RPMPackage python2-matplotlib-2.2.3-3.lbn25.x86_64
Matplotlib is a python 2D plotting library which produces publication quality figures in a variety of hardcopy formats and interactive environments across platforms. matplotlib can be used in python scripts, the python and ipython shell, web application servers, and six graphical user interface toolkits. Matplotlib tries to make easy things easy and hard things possible. You can generate plots, histograms, power spectra, bar charts, errorcharts, scatterplots, etc, with just a few lines of code.
RPMPackage python2-ipaddress-1.0.23-1.lbn25.noarch
ipaddress provides the capabilities to create, manipulate and operate on IPv4 and IPv6 addresses and networks. The functions and classes in this module make it straightforward to handle various tasks related to IP addresses, including checking whether or not two hosts are on the same subnet, iterating over all hosts in a particular subnet, checking whether or not a string represents a valid IP address or network definition, and so on.
RPMPackage python2-inflection-0.3.1-1.lbn25.noarch
Inflection |build status|_.. |build statu .. _build status: is a string transformation library. It singularizes and pluralizes English words, and transforms strings from CamelCase to underscored string. Inflection is a port of Ruby on Rails_' inflector_ to Python... _Ruby on Rails: .. _inflector: - Documentation < - Issue Tracker <
RPMPackage python2-idna-2.8-1.lbn25.noarch
A library to support the Internationalised Domain Names in Applications (IDNA) protocol as specified in RFC 5891 <http://tools.ietf.org/html/rfc5891>. This version of the protocol is often referred to as "IDNA2008" and can produce different results from the earlier standard from 2003. The library is also intended to act as a suitable drop-in replacement for the "encodings.idna" module that comes with the Python standard library but currently only supports the older 2003 specification.
RPMPackage python2-future-0.18.2-1.lbn25.noarch
future: Easy, safe support for Python 2/3 compatibility future is the missing compatibility layer between Python 2 and Python 3. It allows you to use a single, clean Python 3.x-compatible codebase to support both Python 2 and Python 3 with minimal overhead.It is designed to be used as follows:: from __future__ import (absolute_import, division, print_function, unicode_literals) from builtins...
RPMPackage python2-cryptography-vectors-2.8-1.lbn25.noarch
Test vectors for the cryptography package. The only purpose of this package is to be a building requirement for python-cryptography, otherwise it has no use. Don’t install it unless you really know what you are doing.
RPMPackage python2-cryptography-2.8-1.lbn25.x86_64
cryptography is a package designed to expose cryptographic primitives and recipes to Python developers.
RPMPackage python2-cmarkgfm-0.4.2-1.lbn25.py37.x86_64
cmarkgfm - Bindings to GitHub's cmark Minimalist bindings to GitHub's fork of cmark.Installation This package is published as cmarkgfm < and can be installed with pip or pipenv:: pip install --user cmarkgfm pipenv install cmarkgfmWheels are provided for macOS, Linux, and Windows for Python 2.7, 3.4, 3.5, and 3.6.Usage High-level usage is really straightforward. To render normal CommonMark...
RPMPackage python-tarjan-0.2.3.2-2.lbn25.noarch
Tarjan’s algorithm takes as input a directed (possibly cyclic!) graph and returns as output its strongly connected components in a topological order.
RPMPackage zope.contenttype-4.2.0-1.lbn25.noarch
A utility module for content-type handling.
RPMPackage zope.contentprovider-4.0.0-1.lbn25.noarch
This package provides a framework to develop componentized Web GUI applications. Instead of describing the content of a page using a single template or static system of templates and METAL macros, content provider objects are dynamically looked up based on the setup/configuration of the application.
RPMPackage zope.componentvocabulary-2.2.0-1.lbn25.noarch
This package contains various vocabularies.
RPMPackage zope.catalog-3.8.2-2.lbn25.noarch
Catalogs provide management of collections of related indexes with a basic search algorithm.
RPMPackage zope.cachedescriptors-4.2.0-1.lbn25.noarch
Cached descriptors cache their output. They take into account instance attributes that they depend on, so when the instance attributes change, the descriptors will change the values they return. Cached descriptors cache their data in _v_ attributes, so they are also useful for managing the computation of volatile attributes for persistent objects. Persistent descriptors: property A simple computed property. See property.txt. method Idempotent method. The return values are cached based on method arguments and on any instance attributes that the methods are defined to depend on. **Note**, only a cache based on arguments has been implemented so far. See method.txt. Cached Properties ----------------- Cached properties are computed properties that cache their computed values. They take into account instance attributes that they depend on, so when the instance attributes change, the properties will change the values they return.
RPMPackage zope.browserresource-4.1.0-1.lbn25.noarch
This package is at present not reusable without depending on a large chunk of the Zope Toolkit and its assumptions. It is maintained by the Zope Toolkit project. This package provides an implementation of browser resources. It also provides directives for defining those resources using ZCML. Resources are static files and directories that are served to the browser directly from the filesystem. The most common example are images, CSS style sheets, or JavaScript files. Resources are be registered under a symbolic name and can later be referred to by that name, so their usage is independent from their physical location. You can register a single file with the <browser:resource> directive, and a whole directory with the <browser:resourceDirectory> directive, for example <browser:resource file=”/path/to/static.file” name=”myfile” /> <browser:resourceDirectory directory=”/path/to/images” name=”main-images” /> This causes a named adapter to be registered that adapts the request to zope.interface.Interface (XXX why do we not use an explicit interface?), so to later retrieve a resource, use zope.component.getAdapter(request, name=’myfile’). There are two ways to traverse to a resource, with the ‘empty’ view on a site, e. g. http://localhost/@@/myfile (This is declared by zope.browserresource) with the ++resource++ namespace, e. g. http://localhost/++resource++myfile (This is declared by zope.traversing.namespace) In case of resource-directories traversal simply continues through its contents, e. g. http://localhost/@@/main-images/subdir/sample.jpg Rather than putting together the URL to a resource manually, you should use zope.traversing.browser.interfaces.IAbsoluteURL to get the URL, or for a shorthand, call the resource object. This has an additional benefit: If you want to serve resources from a different URL, for example because you want to use a web server specialized in serving static files instead of the appserver, you can register an IAbsoluteURL adapter for the site under the name ‘resource’ that will be used to compute the base URLs for resources. For example, if you register ‘http://static.example.com/’ as the base ‘resource’ URL, the resources from the above example would yield the following absolute URLs: http://static.example.com/@@/myfile and http://static.example.com/@@/main-images
RPMPackage zope.browserpage-4.1.0-2.lbn25.noarch
This package is at present not reusable without depending on a large chunk of the Zope Toolkit and its assumptions. It is maintained by the Zope Toolkit project. This package provides ZCML directives for configuring browser views. More specifically it defines the following ZCML directives: browser:page browser:pages browser:view These directives also support menu item registration for pages, when zope.browsermenu package is installed. Otherwise, they simply ignore the menu attribute.
RPMPackage zope.browsermenu-4.3.0-1.lbn25.noarch
This package provides shared browser components for the Zope Toolkit.