semvec/pypi-packages huggingface dataset:
fa.jquery 0.9.5
jQuery widgets for formalchemy
License: MIT
Keywords: jquery ajax widgets

This module provide a set of ajax widgets for FormAlchemy_ using `jQuery.ui <http://jqueryui.com/>`_

.. _formalchemy: http://docs.formalchemy.org/formalchemy.html

Have a look at the `Online demo
<http://docs.formalchemy.org/fa.jquery/demo.html>`_

Bug and feature request must be reported on the `github tracker
<https://github.com/FormAlchemy/fa.jquery/issues>`_


CHANGES
==========
0.9.5 - 2011-09-15
------------------

Add Pyramid 1.1 compatibility [amleczko]

Use `fanstatic <http://www.fanstatic.org/>`_ to serve resource


0.9.2
-----

Small change to work with pyramid_formalchemy 0.2
add italian translations [amleczko]

0.9.1
-----

Add some improvements to avoid failures with FF4


0.9
---

Add pyramid view and templates

Switch to latest jQuery.ui

0.7
---

Improve ModelController using jqGrid

Add relation(s) widgets for pylons

0.6.2
-----

IE do not support indexOf. Fix Array prototype.

0.6.1
-----

Add Flash message

0.6
---

Switch to jquery.ui 1.8. Autocomplete should now return a json array of {"value": "v"}.

Better implementation of RichTextFieldRenderer allowing to use TinyMCE and MarkitUp!

0.4
---

- Add TemplateEngine with jquery.ui css classes

0.3
---

- fix MANIFEST.in to include mako templates in distribution.

- Add fa.jquery.forms.Accordion
speccer 0.7.5
Specification based test runner.
License: MIT

Speccer - Specification based test runner for Python
====================================================

Speccer provides simple means to test individual modules. It uses a
minimal, assert-free syntax. This syntax is compiled to actual code
utilizing Python's unittest. Henceforth Speccer may be seen as an
alternative to it in various situations.

Run "setup.py install" to start rocking. See "demo" folder for an actual
example. Once you have installed the tool just invoke "run\_specs" at
that directory. You should see some test results. Feel free to tweak the
files to give it a proper go.

Basic Specification Syntax
--------------------------

A module specification could look something like this:

myclass.spec: (tests myclass.py)

::

    set up
        c = myclass.MyClass()

    adds two and two
        c.add(2,2) == 4

    adds negatives
        c.add(10, -10) == 0

    fails adding int and string
        c.add(10, 'foo') raises TypeError

It looks pretty much like any other test you may have seen before. The
syntax may be a bit lighter, though. As a test author you can focus on
the essential while writing the assertions. In addition it's a bit nicer
to read this way.

Note that it's possible to mix regular Python code within the tests.
This might not work in all cases, though, and should be reported.

"set up" is a predefined test method that is run before each
specification. This way you can set up some objects that are available
for each test.

Each specification contains a name and some actual code asserting
something. I have listed available assertions below:

-  ==, is equal
-  !=, is not equal
-  ~=, is almost equal
-  !~=, is not almost equal
-  >, bigger than
-  >=, bigger than or equal
-  <, smaller than
-  <=, smaller than or equal
-  x < y < z, multiple inequalities (mix with equality as you want)

These assertions map directly to ones available in Python's unittest
module. If some of those seem weird to you, see
http://docs.python.org/library/unittest.html .

Changelog
---------

-  0.7.5 - Made it possible to define functions between test definitions
   and made the runner more robust altogether. Now it's possible to
   separate tests to another directory. In addition it's possible to run
   tests simply by passing this directory to the runner (ie. run\_specs
   tests).

License
-------

Speccer is available under MIT license. See LICENSE for more details.