semvec/pypi-packages huggingface dataset:
khufu_siteview 0.9.1
Easy template-to-view support
License: BSD
Keywords: pyramid khufu

==============
khufu_siteview
==============

Overview
========

*khufu_siteview* is an addon for Pyramid hows the registration of a
view that can be used to serve all ``.jinja2`` files out of a directory
as subviews without the need to map them directly.

Usage
=====

Standard setup is to ``Configurator.include`` the *khufu_siteview*
package and then add new views as necessary.

Example::

  from pyramid.config import Configurator
  
  def app(global_conf, **settings):
      config = Configurator(settings=settings)
      config.include('khufu_siteview')
      config.add_templateview_route('/some/path/to/site', '/')
      return config.make_wsgi_app()

The previous example mounts the view at the root of the new Pyramid
application.  The following example url's would work::

  http://127.0.0.1:8080/favicon.ico   ->  /some/path/to/site/favicon.ico
  http://127.0.0.1:8080/somepage.jinja2   ->  /some/path/to/site/somepage.jinja2

Static assets such as gif's and ico's will be looked up as if the view was static.

Credits
=======

Created and maintained by Rocky Burt <rocky AT serverzen DOT com>.


Changes
=======

0.9.1 - Apr 26, 2011
--------------------

  * fixed bug where standard global renderer vars were being removed

0.9 - Apr 18, 2011
------------------

  * first release
pitz 1.2.4
Python to-do tracker inspired by ditz (ditz.rubyforge.org)
License: BSD
Keywords: ditz

.. vim: set filetype=rst sw=4 ts=4 tw=72 :

Pitz is a little like ditz_ except with a few changes here and there.

.. _ditz: http://ditz.rubyforge.org

Read pitz/docs for more background.
js.jquery_utils 0.8.5
Fanstatic packaging of jQuery Utils
License: BSD

js.jquery_utils
***************

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

This library packages `jQuery Utils`_ for `fanstatic`_.

.. _`fanstatic`: http://fanstatic.org
.. _`jQuery Utils`: http://code.google.com/p/jquery-utils/

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


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


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

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


CHANGES
*******

0.8.5 (2011-04-25)
==================

- Initial release.
js.jquery_qunit 0.5
Fanstatic packaging of jQuery QUnit
License: BSD

js.jquery_qunit
***************

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

This library packages `jQuery QUnit`_ for `fanstatic`_.

.. _`fanstatic`: http://fanstatic.org
.. _`jQuery QUnit`: http://docs.jquery.com/Qunit

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


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


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

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


CHANGES
*******

0.5 (2011-04-25)
================

- Initial release.
js.jquery_jstree 1.0rc2
Fanstatic packaging of jQuery JsTree
License: BSD

js.jquery_jstree
****************

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

This library packages `jQuery JsTree`_ for `fanstatic`_.

.. _`fanstatic`: http://fanstatic.org
.. _`jQuery JsTree`: http://www.jstree.com/

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


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


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

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


CHANGES
*******

1.0rc2 (2011-04-25)
===================

- Initial release.
sphinxcontrib-bitbucket 1.0
Sphinx/BitBucket integration
License: BSD

########################
sphinxcontrib.bitbucket
########################

This module adds custom roles for linking to resources on BitBucket
projects.

Basic Usage
===========

To use this extension, add it to the ``extensions`` list in your
Sphinx configuration file and set the variable
``bitbucket_project_url`` to the base URL for the project.  

For example::

    extensions = [ 'sphinxcontrib.bitbucket' ]

    bitbucket_project_url = 'http://bitbucket.org/birkenfeld/sphinx-contrib'

Then in your rst documents, use the roles ``bbissue`` and
``bbchangeset`` to create links to tickets and changesets.

This::

    :bbissue:`3`

is equivalent to::

    `issue 3 <http://bitbucket.org/birkenfeld/sphinx-contrib/issue/3/>`__

and::

    :bbchangeset:`some-long-hash-value`

is equivalent to::

    `changeset some-long-hash-value <http://bitbucket.org/birkenfeld/sphinx-contrib/changeset/some-long-hash-value/>`__

Configuration Parameters
========================

bitbucket_project_url
  The base URL for the project on BitBucket.org.


History
=======

1.0
---

First public release.
clue_sqlaloader 0.1.1
Data loader for SQLAlchemy
License: BSD
Keywords: sqlalchemy clue yaml sql

===============
clue_sqlaloader
===============

Overview
========

*clue_sqlaloader* provides a mechanism for populating a sql database
using `SQLAlchemy <http://www.sqlalchemy.org/>`_ and
`YAML <http://www.yaml.org/>`_.

Usage
=====

*clue_sqlaloader* was primarily meant to run from inside other
applications as a framework piece but can be run from the command-line
as follows::

  $ python -m clue_sqlaloader.__init__ sqlite:///somefile.db data.yaml

The typical way to use the loader from within Python is as follows::

  from clue_sqlaloader import Loader
  loader = Loader(sqlalchemy_session)
  loader.load_from_yamlf('somefile.yaml')

The format of the YAML should be similar to the following::

  - model: mymodule.Group
    refname: !!refname "admingroup"
    fields:
      name: admin
  - model: mymodule.User
    fields:
      username: testuser1
      email: user@hisplace.com
      groups: [!!ref "admingroup"]
    execute:
      set_password: testuser1

The *model* and *fields* arguments are straightforward.  The *execute*
argument will call the given function name on the newly created object
with the given value.

Credits
=======

Written and maintained by Rocky Burt <rocky AT serverzen DOT com>


Changes
=======

0.1.1 (Apr-21-2011)
-------------------

  * Made Reference lookup a little more robust

  * Added missing dep for zope.dottedname

0.1 (Apr-12-2011)
-----------------

  * first release
django-bylaws 1.0.2
Manages bylaws for a website built on Django.
License: BSD

django-bylaws
================

This project gives you a pluggable application for adding bylaws to a
project. It takes advantage of django_simple_history to provide
rudimentary version control of your bylaw documents and can also handle
whether users must sign them before doing various deeds on your website.

Installation
-------------

1. Place 'bylaws' in your installed apps.
2. Add something like the following to your urls:

        url(r'^bylaws/', include('bylaws.urls')),

3. Sync your DB:

        python manage.py syncdb

Overview
----------

Bylaws are simple documents that allow you to:

1. use markup to structure a bylaws document
2. keep track of any changes anyone makes
3. gives you easy access to the latest adopted bylaw document