semvec/pypi-packages huggingface dataset:
django-infinite-memcached 0.1
A Django memcached backend to handle 'infinite' timeouts
License: BSD

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

A Django memcached backend to handle "infinite" timeouts (i.e., never
expire an item).

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

1) ``$ pip install django-infinite-memcached``

2) Set ``infinite_memcached.cache.MemcachedCache`` as your cache backend::

    CACHES = {
        "default": {
            "BACKEND": "infinite_memcached.cache.MemcachedCache",
            "LOCATION": "127.0.0.1:11211",
        },
    }

How to use
----------

Either set the ``TIMEOUT`` option to 0::

    CACHES = {
        "default": {
            "BACKEND": "infinite_memcached.cache.MemcachedCache",
            "LOCATION": "127.0.0.1:11211",
            "TIMEOUT": 0,
        },
    }

Or pass ``timeout=0`` to the `low-level cache commands
<https://docs.djangoproject.com/en/1.4/topics/cache/#the-low-level-cache-api>`_
(e.g., set, add, etc.) to keep things from expiring.

Why?
----

Django's default memcached backend doesn't accept timeout values of
zero, instead using the default timeout (five minutes) when zero is passed.

This cache backend overrides how timeouts are calculated so any
timeout of zero is passed directly to memcached, telling memcached to
never expire an item.

This has been an `known issue
<https://code.djangoproject.com/ticket/9595>`_ for awhile, but
concerns over backwards compatibility have prevented any fixes from
taking place.

License
-------

BSD. See LICENSE.txt.
formgear 0.3.5
Formgear framework base package
License: BSD

Formgear
#########

.. image:: https://secure.travis-ci.org/xen/formgear.png
    :target: https://travis-ci.org/#!/xen/formgear

Main idea behind ``formgear`` allow iteratively create data models in easy 
readeable form and use them as part of your websites. At this moment only 
MongoDB is allowed. 

Imagine what happends when you plan to create new site (for yourself or 
client). You doing several steps and one important is make row draft of what
content you will publish and retation between different types of content. 
Usually it implies you bootstrap your framework, step over several stages of
creating scaffold and only then write models code. In the worst case you write 
SQL. 

But we are living in 21 century, have decoded DNA, pushing frontier into 
space, diging into core of the atoms and listening dubstep! Why we must to 
write all that crap? Why computers cann't just do all this stuff?

So that is why we invent ``formgear``. Because we want computers to do that they
supposed to do. 

`formgear` is only part of this effort, but here is already some results. So,
example how to make simple model. We use `YAML` because it is very human 
readeable. Minimal file::

    # user.yaml
    title: User
    description: >
      This is user model. 

    fields:
      - name: name
      - name: email
      - name: site
      - name: about

This file is enough to use it as model in your python code::

    # models.py
    from formgear.models import Model
    class User(Model):
        __yaml__ = 'user.yaml'

``formgear`` is only a library for bigger framework, if you deside to use whole 
stack then you will get site with admin section including list, edit, add, 
search, delete sections for each models.

Changes
========

0.3.5:

- added independed data sources, but atm still have only mongodb datasource

0.3.4: 

- Started this log.

More
======

Links:

* ``formgear`` page on PyPI: `http://pypi.python.org/pypi/formgear/ 
  <http://pypi.python.org/pypi/formgear/>`_
* Github page: `https://github.com/xen/formgear 
  <https://github.com/xen/formgear>`_

More documentation is approaching.
vimmock 0.1.1
vim mock object for easier testing of vim plugins written in Python.
License: BSD

vimmock
=======

.. image:: https://secure.travis-ci.org/lukaszb/vimmock.png?branch=master
  :target: http://travis-ci.org/lukaszb/vimmock

vimmock is a module that makes testing Python code using *vim* module much
easier.


Usage
=====

At the test environment initialization one should prepare ``vim`` object that
would normaly be used within vim's plugin. We have added convenient function for
that::

    import vimmock
    vimmock.patch_vim()

This is equivalent to::

    import sys
    from vimmock import VimMock

    sys.modules['vim'] = VimMock()

Once this is done one can start importing *vim* module which would be instance
of *VimMock* class. From now on we can write our tests (and import ``vim``
module)::

    import vim
    import unittest
    import myplugin

    class TestPlugin(unittest.TestCase):
        
        def setUp(self):
            vim.setup_text('\n'.join(('foo', 'bar')))

        def test_simple(self):
            vim.current.window.cursor = 2, 0 # rows starts from 1, column from 0
            # ... let's assume our plugin swaps lines
            self.assertEqual(vim.current.buffer[0], 'bar')
            self.assertEqual(vim.current.buffer[1], 'foo')


Development
===========

Please use github's issue tracker for filing new issues. Preferred way of
attaching patches is via *pull requests*.


Work in progress
----------------

Please note that ``vimmock`` is a work-in-progress module. Only basic mocks are
actually completed. If you want to use this module for now it is best if you
fork it, link to your ``PYTHONPATH`` environment variable and modify on the fly.
Pull requests are welcome!
django-scanredirect 0.0.1
Django app thats adds URL rules to redirect scripts looking for webapps exploits to their own IP
License: BSD

django-scanredirect
===================

A little Django app thats adds URL rules to redirect scripts looking for webapps exploits to their own IP

Add `scanredirect` (with an underscore) to INSTALLED_APPS in your django project settings.

Add the following line at the top of your project's urls.py file::
        (r'^', include('scanredirect.urls')),
mekk.feeds 1.4.3
RSS scripting
License: BSD
Keywords: org

===========
mekk.feeds
===========

Helper scripts for heavy RSS user.

Content
=========

Currently the following script is available:

greader2org

  Manage Google Reader subscribtions editing the text file (org-mode
  compatible syntax). You can use it to export the list of subscribed
  feeds to readable text file, edit this file and save changes
  back. See `more elaborate description on the blog`_ and 
  `doc/greader2org.txt`_ within the sources.


Sources
=========

The project is `hosted on bitbucket`_.



.. _more elaborate description on the blog: http://blog.mekk.waw.pl/archives/31-Editing-Google-Reader-subscriptions-with-a-text-editor.html

.. _doc/greader2org.txt: http://bitbucket.org/Mekk/mekk.feeds/src/tip/doc/greader2org.txt

.. _hosted on bitbucket: http://bitbucket.org/Mekk/mekk.feeds
mekk.greader 1.2.3
Simple wrapper for Google Reader API.
License: BSD
Keywords: google reader client

============
mekk.greader
============

Simple Google Reader access API. The module implements a couple of
feed management functions, making it possible to manage Google Reader
subscriptions (subscribe, unsubscribe, rename, (re)tag feeds) from
Python scripts and programs.

Warning
=======

No official documentation was used, I partially reverse-engineered
the API and partially used unofficial descriptions found on the web.
So there are absolutely no guarantees!

Still, I regularly use this module to subscribe, unsubscribe and
rename feeds, especially via greader2org_.

.. _greader2org: http://blog.mekk.waw.pl/archives/31-Editing-Google-Reader-subscriptions-with-a-text-editor.html


Sources, patches, bug reports
=============================

Source code is available on `BitBucket`_. The same page can be used
for bug reporting and for patch submission.

.. _BitBucket: http://bitbucket.org/Mekk/mekk.greader