semvec/pypi-packages huggingface dataset:
hurry.datatables 1.7.6
hurry.resource style resources for jQuery datatables.
License: BSD
Keywords: hurry.resource jquery

hurry.datatables
****************

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

This library packages the `DataTables`_ jquery extension for
`hurry.resource`_. It is aware of jQuery datatables' different modes
(normal, minified).

.. _`hurry.resource`: http://pypi.python.org/pypi/hurry.resource
.. _`DataTables`: http://www.datatables.net

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

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

  from hurry.datatables import datatables

  .. in your page or widget rendering code, somewhere ..

  datatables.need()

This requires integration between your web framework and
``hurry.resource``, and making sure that the original resources
(shipped in the ``datatables-build`` directory in
``hurry.datatables``) are published to some URL. The
``hurry.datatables.datatables_lib`` library, exposed as an entry point
to ``hurry.resource``, knows where the data is in its ``path``
argument.

The package has already been integrated for Grok_ and the Zope
Toolkit. If you depend on the `hurry.zoperesource`_ package in your
``setup.py``, the above example should work out of the box. Make sure
to depend on the `hurry.zoperesource`_ package in your ``setup.py``.

.. _`hurry.zoperesource`: http://pypi.python.org/pypi/hurry.zoperesource

.. _Grok: http://grok.zope.org

CHANGES
*******

1.7.6 (2011-03-23)
==================

* Updated to datatables 1.7.6.

1.7b6.1 (2010-07-28)
====================

* Initial public release, using datatables 1.7b6

* Only compatible with hurry.resource >= 0.10


Download
********
dm.zopepatches.fix_responsewrite_conflict 1.0
Zope[2] patch to alleviate the effect of https://bugs.launchpad.net/zope2/+bug/740831.
License: BSD
Keywords: patch wrong response Zope2

This package patches the web application server Zope to work around
https://bugs.launchpad.net/zope2/+bug/740831.

The bug causes Zope to deliver wrong responses after a request using
``Response.write`` has suffered a ``ConflictError``. The patch
prevents Zope from retrying such requests and logs an error message when it
tries. The bug effect is thus limited to a single request.

Note that even with this patch Zope does not behave fully correctly: in
case of a ``ConflictError``, it may
deliver a (maybe partial) response even though the transaction has
been aborted. The client does not get feedback for the transaction rollback.
The only indication is the log record written.

``Response.write`` is inherently unsafe in the face of ``ConflictError``.
The only reliable fix is not to use it at all.


The (monkey) patch gets installed when this package is imported.