semvec/pypi-packages huggingface dataset:
django-memcached 0.1.2
django-memcached is a very simple reusable app which does one simple thing: shows you statistics about your currently running memcached instances
License: BSD
Keywords: memcached,django

django-memcached
=================

This is a very simple reusable app which does one thing: shows you statistics
about your currently running memcached instances.  There are no database models
and not much configuration.

Installing django-memcached
----------------------------

1. Either download the tarball and run ``python setup.py install``, or simply
   use easy install or pip like so ``easy_install django-memcached``.


2. Add django_memcached to your ``INSTALLED_APPS`` setting::

       INSTALLED_APPS = (
           # ...
           'django_memcached',
       )


3. Add the urls to your url configuration::

       urlpatterns = patterns('',
           # ...
           (r'^cache/', include('django_memcached.urls')),
       )


4. If you want to restrict these urls to only staff members, just add this
   setting to your settings file::
   
       DJANGO_MEMCACHED_REQUIRE_STAFF = True


That's it.  Hopefully this app gives you a little insight into how your
memcached servers are being utilized.
django-freeperms 0.1
Django middleware for enabling anonymous permissions
License: BSD
Keywords: django middleware permissions auth

django-freeperms
================

* Bugs_

.. _Bugs: http://bugs.launchpad.net/django-freeperms

.. contents::


Overview
--------

``freeperms`` provides a simple and generic way to expose an
application's permissions to anonymous users. Take a wiki app or an
issue tracker for example. In one deployment it might be appropriate
to require a user login to edit pages or submit tickets for bugs, but
in another deployment you might want to allow anonymous editing.

Applications that take advantage of the ``django.contrib.auth``
permissions framework (outside of ``django.contrib.admin``) can be
used with ``freeperms`` so that they don't directly need to handle
delegating features to anonymous users.

Usage
-----

Add the middleware to your settings, at the end::

    MIDDLEWARE_CLASSES = (
        'freeperms.middleware.AnonymousPermissionsMiddleware'
    )

Then expose the permissions you want to grant to anonymous users::

    ANONYMOUS_PERMISSIONS = (
        'wiki.add_page',
        'wiki.change_page',
        'wiki.delete_page',
        'tickets.add_ticket',
        'tickets.change_ticket',
    )

You can also register or unregister permissions from anywhere in your
Python code::

    >>> import freeperms
    >>> freeperms.register('wiki.add_page')
    >>> freeperms.unregister('wiki.add_page')

Settings
--------

``ANONYMOUS_USERNAME``
~~~~~~~~~~~~~~~~~~~~~~

The username to use for anonymous users.

``ANONYMOUS_PERMISSIONS``
~~~~~~~~~~~~~~~~~~~~~~~~~

A sequence of permissions in the form 'app_label.code_name'.

Changelog
---------

0.1
~~~

* Initial release.
django-viewssi 0.1.1
Template tag for requesting views in templates (Django)
License: BSD
Keywords: django utilities templatetag

* Bugs_

.. _Bugs: http://bugs.launchpad.net/django-viewssi

A template tag for making simulated GET requests to Django application view
functions. The HTTP response can be displayed in the given template.

Variations of usage of ``viewssi``::

    {% viewssi path.to.view %}
    {% viewssi path.to.view arg,arg2,kwarg=val %}
    {% viewssi path.to.view arg,arg2,kwarg=val as var %}
    {% viewssi path.to.view arg,arg2,kwarg=val get p1=v1,p2=v2 as var %}

The first argument is the path to a view function to call. If the
view requires ``args`` and/or ``kwargs``, pass them as the second
token in the tag. ``args`` and the values of ``kwargs`` are
resolved to template variables unless they are quoted.

The view doesn't have to be exposed in a URL
configuration. Essentially any function can be called that accepts
one argument (the request) and returns a
``django.http.HttpResponse`` object.

You can pass a GET query string by including a ``get`` token in
the tag followed by ``key=value`` pairs. Parameter values are also
resolved to template variables unless they are quoted.

If the ``as <template-variable-name`` token of the tag is
provided, the view's response is assigned to the given template
variable. Otherwise, the response content is returned in place.

When the response is assigned to a template variable, the http
response is represented as a ``HttpResponseProxy`` object which
contains a template-useable interface for fetching the response
code, headers, and content. Examples::

    {% ifequal response.status_code "200" %}
    {{ response }}
    {% endifequal %}

``HttpResponseProxy`` behaves is a dict-like object. The http
response headers are set as the dict items and their names are
transposed for use in templates, i.e. 'Content-type' becomes
'content_type'. For example::

    {% ifequal response.content_type "text/html" %}
    {% endifequal %}
fez.atcsv 0.2
Simple AT CSV processing
License: BSD
Keywords: plone zope archetypes csv import

Introduction
        ============
        
        This is alpha software, and not considered suitable for production use. In
        particular, there are few tests. Caveat emptor!
        
        This package was sponsored by `Jon Hadley <http://www.jon-hadley.com/>`_.
        Changelog
        =========
        
        0.2 - UI and architecture
        -------------------------
        
        * Change to z3c.form-based forms
        * Use CA to look up importer
        * Allow specification of delimiter
        
        0.1 - Alpha
        -----------
        
        * Initial release
        * Basic import features
        
        Introduction
        ============
        
        fez.atcsv is a lightweight product for importing CSV files into Plone sites.
        Unlike other implementations, it leaves no persistent data in the database
        aside from imported content.
        
        To use, install the product onto your pythonpath using easy_install or pip:
        
        easy_install fez.atcsv
        
        or
        
        pip install fez.atcsv
        
        
        You should then add 'fez.atcsv' to your eggs = and zcml = sections in your buildout.
        Restart Zope, and you should see AT CSV in your quickinstaller page. Install it,
        and you should see a 'CSV Import' tab on all folder-like content objects.
        
        The CSV you upload *must* have a first line of titles, and these titles *must* correspond
        to the Archetype field names of the type you're importing. So, if you had an Archtype content
        type that had a schema like this:
        
        atapi.TextField(
        'Title',
        searchable = 1,
        required = 0,
        storage = atapi.AnnotationStorage(),
        widget = atapi.StringWidget(label='Title'),
        ),
        
        atapi.TextField(
        'Colour',
        searchable = 1,
        required = 0,
        storage = atapi.AnnotationStorage(),
        widget = atapi.StringWidget(label='Colour'),
        ),
        
        Then a valid CSV might look like this:
        
        "Title","Colour","Size"
        "Apple", "Green", "small"
        "Banana", "Red", "Medium"
        
        Note that in this case, the 'size' column won't be imported as it's not in the AT schema.
        
        Further, notice that no validation is run on the imported data. It is assumed that
        the data will be clean. (Validation may be added at a later point.)
        
        Be aware that large file uploads may take some time.
        
        
        
        Dan Fairs (Fez Consulting Ltd.), dan@fezconsulting.com, Author