semvec/pypi-packages huggingface dataset:
js.jquery_tinyscrollbar 1.67
Fanstatic packaging of jQuery Tiny Scrollbar
License: BSD

js.jquery_tinyscrollbar
***********************

Introduction
============

This library packages `jQuery Tiny Scrollbar`_ for `fanstatic`_.

.. _`fanstatic`: http://fanstatic.org
.. _`jQuery Tiny Scrollbar`: http://baijs.nl/tinyscrollbar/

This requires integration between your web framework and ``fanstatic``,
and making sure that the original resources (shipped in the ``resources``
directory in ``js.jquery_tinyscrollbar``) are published to some URL.


How to use?
===========


You can import ``jquery_tinyscrollbar`` from ``js.jquery_tinyscrollbar`` and
``need`` it where you want these resources to be included on a page::

  >>> from js.jquery_tinyscrollbar import jquery_tinyscrollbar
  >>> jquery_tinyscrollbar.need()


CHANGES
*******

1.67 (2012-08-03)
=================

- Initial release.
hgallpaths 0.1
A mercurial extension to allow pushing and pulling from all paths.
License: BSD

============
 hgallpaths
============

A mercurial extension to allow pushing and pulling from all paths specified in
the configuration.

Installation
============

Add hgallpaths extension to your ~/.hgrc::

  [extensions]
  hgallpaths = /path/to/hgallpaths.py

The list of all paths is available from the ``paths`` command::

  $ hg paths


Alternatively you can install hgallpaths with ``pip``::

  $ pip install hgallpaths

or with ``setuptools``::

  $ python setup.py install

With either of those methods you don't need to specify the path to hgallpaths
in your hgrc configuration::

  [extensions]
  hgallpaths =


Configuration
-------------

You can exclude certain paths in the configuration. For example to always
exclude the path ``foo`` and ``bar``, as well as exclude ``baz`` when pushing
you add this to your ~/.hgrc (or repo hgrc)::

  [hgallpaths]
  exclude = foo bar
  exclude_push = baz

Usage
=====

The two commands supported at the moment are ``pushall`` and ``pullall``. For
example to push to all paths run::

  $ hg pushall
django-setuptest-recipe 0.1
Recipe to prevent django-setuptest from polluting module being tested with downloaded eggs
License: BSD

Django Setuptest Recipe
=======================
**Recipe to prevent django-setuptest from polluting module being tested with
downloaded eggs.**

.. contents:: Contents
    :depth: 5

Motivation
----------

django-setuptest downloads eggs required for a test run and places them in the
module directory. For example, if the module to be tested is called ``foo``
then the command ``python setup.py test`` causes ``src/foo`` to be polluted
with many eggs. There is currently no way to instruct setuptools to store these
eggs in another location.

``django-setuptest-recipe`` addresses this shortcoming by wrapping the Python
interpreter to be aware of egg locations.

Usage
-----

Add the following to your ``buildout.cfg``::

    parts=
        ...
        setuptest-runner

    [setuptest-runner]
    recipe = django-setuptest-recipe
    eggs = ${buildout:eggs}

An executable file called ``setuptest-runner`` is created in the ``bin``
directory. You can now do ``/path/to/instance/bin/setuptest-runner setup.py
test`` from within the ``src/foo`` directory.

Authors
=======

Praekelt Foundation
-------------------

* Hedley Roos

Changelog
=========

0.1
---
#. First release.
RosterUserTools 0.17
RosterUserTools are a set of command line tools for Roster
License: BSD

Roster is DNS management software for use with Bind 9. Roster is written in Python and uses a MySQL database with an XML-RPC front-end. It contains a set of command line user tools that connect to the XML-RPC front-end. The config files for Bind are generated from the MySQL database so a live MySQL database is not needed.
RosterServer 0.17
RosterServer is a XML/RPC Server for Roster.
License: BSD

Roster is DNS management software for use with Bind 9. Roster is written in Python and uses a MySQL database with an XML-RPC front-end. It contains a set of command line user tools that connect to the XML-RPC front-end. The config files for Bind are generated from the MySQL database so a live MySQL database is not needed.
RosterConfigManager 0.17
RosterConfigManager is a Bind9 config importer/exporter for Roster
License: BSD

Roster is DNS management software for use with Bind 9. Roster is written in Python and uses a MySQL database with an XML-RPC front-end. It contains a set of command line user tools that connect to the XML-RPC front-end. The config files for Bind are generated from the MySQL database so a live MySQL database is not needed.
RosterCore 0.17
RosterCore contains the Core and  DB libraries for Roster
License: BSD

Roster is DNS management software for use with Bind 9. Roster is written in Python and uses a MySQL database with an XML-RPC front-end. It contains a set of command line user tools that connect to the XML-RPC front-end. The config files for Bind are generated from the MySQL database so a live MySQL database is not needed.