semvec/pypi-packages huggingface dataset:
Pizco 0.1
Python remote objects with ZMQ
License: BSD

Pizco: a Python library to communicate with remote objects
==========================================================

Pizco is Python module/package that allows python objects to communicate.
Objects can be exposed to other process in the same computer or over the network,
allowing clear separation of concerns, resources and permissions.

Pizco not only support calling methods from remote objects but also
accessing their attributes, dictionary attributes and properties. Most importantly,
using a Qt-like (and Qt compatible!) signal and slot mechanism you can easily
register notifications.

As ZMQ is used as the transport layer, communication is fast and efficient,
and different protocols are supported. It has a complete test coverage.
It runs in Python 3.2+ and requires PyZMQ_. It is licensed under BSD.


Design principles
-----------------

- Reusable Agent class as communicating object for both Proxy and Server.

- ZMQ REP/REQ to handle sync access to objects.

- ZMQ PUB/SUB for notifications and async operations.

- PyQt-like signal and slots callbacks, compatible with PyQt.

- Transparent handling of methods that return concurrent.Futures.

- *Soon*: Asynchronous and batched operation on remote objects.

- Small codebase: small and easy to maintain codebase with a flat hierarchy.
  It is a single stand-alone module that can be installed as a package or added
  side by side to your project.

- *Soon*: Python 2 and 3: A single codebase that runs unchanged in Python 2.6+ and Python 3.0+.


.. _PyZMQ: https://github.com/zeromq/pyzmq
.. _Pyro: http://packages.python.org/Pyro4/
django-autohide-help 0.0.1
jQuery plugin that auto-hides form field help blocks as pluggable Django app
License: BSD

====================
django-autohide-help
====================

django-autohide-help is a jQuery_ plugin packaged as a Django_ app for easy
installation. It's a plugin that allows frontend developers to hide help blocks
generated by `crispy forms`_.

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

Install using pip::

    pip install django-autohide-help

After adding ``autohide_help`` to ``INSTALLED_APPS``, ``autohide-help.js`` will
be avalable at ``{{ STATIC_URL }}js/autohide-help.js``.

If you are using RequireJS_, you can add ``autohide-help`` to dependencies, as
it is packages with RequireJS support.

If you want to use it via a simple script tag, you can add the script tag as
usual::

    <script src="{{ STATIC_URL}}js/autohide-help.js``"></script>

This plugin requires jQuery (obviously).

Basic usage
===========

Select a form (or forms), and call ``autohideHelp`` on it::

    $('form').autohideHelp()

As user enters the fields the help block is slid out, and slid back in as user
leaves the field.

Using without crispy forms
==========================

Crispy forms are not absolutely required. It is just convenient to use them
since they automatically generate the help blocks.

If you want to use django-autohide-help without the crispy forms, make sure
that your help blocks have an id in the following format: ``help_FIELD_ID``
where ``FIELD_ID`` is the id of the field to which the help block belongs. For
example, if you field has an id of ``id_name``, the help block must have the
id of ``help_id_name``. Future releases of ``django-authide-help`` may make
this configurable.

Reporting bugs
==============

Please report bugs to Bitbucket `issue tracker`_.

.. _jQuery: http://jquery.com/
.. _Django: http://www.djangoproject.com/
.. _crispy forms: http://django-crispy-forms.readthedocs.org/en/d-0/
.. _issue tracker: https://bitbucket.org/brankovukelic/django-autohide-help/issues
scrapy-heroku 0.7.1
Utilities for running scrapy on heroku
License: BSD
Keywords: scrapy,heroku

Scrapy-Heroku
=============

A package to assist with running scrapy on heroku. This is accomplished by providing
a custom application configuration at ``scrapy_heroku.app.application`` that launches
the scrapyd web service using the PORT environment variable and a multi-process work
queue implemented on a Postgres database specified by the DATABASE_URL environment
variable.

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

Create a git repo that has a scrapy project at the root (scrapy.cfg should be at the
top level). Edit your scrapy.cfg to include the following::

    [scrapyd]
    application = scrapy_heroku.app.application

    [deploy]
    url = http://<YOUR_HEROKU_APP_NAME>.herokuapp.com:80/
    project = <YOUR_PROJECT_NAME>
    username = <A_USER_NAME>
    password = <A_PASSWORD>

Add a requirements.txt file that includes ``scrapy-heroku`` in it. It is strongly
recommended that you version pin scrapy-heroku as well as the version of scrapy that
your project is developed against (pip freeze > requirements.txt). Finally create a
Procfile that consists of::

    web: scrapy server

Make sure you have a postgres database that has been promoted to DATABASE_URL


* Project page: <http://github.com/dmclain/scrapy-heroku>