semvec/pypi-packages huggingface dataset:
jslex 0.2.1
JsLex makes JavaScript more edible by xgettext (in C mode).
License: BSD

JsLex
=====

A Javascript lexer in Python

Ned Batchelder, http://nedbatchelder.com

JsLex is part of an effort to improve Django's support of localized strings in
Javascript code. It splits Javascript source into a list of tokens.

This makes it more palatable by xgettext in C mode. 

This is a release to PyPI created by Martijn Faassen to make it usable
outside of Django as well.

To run the tests, run "python tests.py".

CHANGES
*******

0.2.1 (2012-01-13)
==================

- Added a MANIFEST.in, as otherwise CHANGES.txt isn't picked up.

0.2 (2012-01-13)
================

- Added a ``jslex_prepare`` script (using setuptools entry points)
  that can be used to run this code from the command line.

0.1 (2012-01-13)
================

- make it work with setuptools and zest.releaser.

- Initial release to PyPI.
sqlamp 0.6
sqlamp is an implementation of Materialized Path for SQLAlchemy.
License: BSD

`sqlamp` -- Materialized Path for SQLAlchemy
============================================

`sqlamp` is an implementation of an efficient algorithm for working
with hierarchical data structures -- `Materialized Path`. `sqlamp`
uses (and depends of) `SQLAlchemy <http://sqlalchemy.org>`_.

`Materialized Path` is a way to store (and fetch) a trees in a relational
databases. It is the compromise between `Nested Sets` and `Adjacency
Relations` in respect to simplicity and efficiency. Method was promoted
by `Vadim Tropashko`_ in his book `SQL Design Patterns`_. Vadim's
description of the method can be read in his article `Trees in SQL:
Nested Sets and Materialized Path (by Vadim Tropashko)`_.

Implemented features:

    * Setting up with ``declarative.ext`` or without it.
    * Saving node roots -- if no parent set for node.
    * Saving child nodes -- if node has some parent. The whole dirty job
      of setting values in utility fields is done by `sqlamp`.
    * Fetching node's descendants, ancestors and children using the most
      efficient way available.
    * Autochecking exhaustion of tree size limits (maximum number of
      children and maximum nesting level) is done during session flush.
    * Rebuilding all trees and any subtree on the basis of Adjacency
      Relations.
    * Collapsing flat tree returned from query to recursive structure.
    * Node classes may use polymorphic inheritance.
    * Nodes and whole trees/subtrees can be moved around or removed
      entirely.

Known-to-work supported DBMS include `sqlite`_ (tested with 3.6.14),
`MySQL`_ (tested using both MyISAM and InnoDB with server version 5.1.34)
and `PostgreSQL`_ (tested with 8.3.7), but sqlamp should work with any
other DBMS supported by SQLAlchemy.

Supported versions of SQLAlchemy include current minor versions
of branches 0.5 and 0.6 as well as 0.7 since 0.7.2.

.. _`Vadim Tropashko`: http://vadimtropashko.wordpress.com
.. _`Sql Design Patterns`:
   http://www.rampant-books.com/book_2006_1_sql_coding_styles.htm
.. _`Trees in SQL: Nested Sets and Materialized Path (by Vadim Tropashko)`:
   https://communities.bmc.com/communities/docs/DOC-9902
.. _`sqlite`: http://sqlite.org
.. _`MySQL`: http://mysql.com
.. _`PostgreSQL`: http://postgresql.org
darcsver 1.7.4
generate a version number from darcs history
License: BSD
Keywords: distutils setuptools plugin setup darcs

========================================================================
darcsver - generate version numbers from darcs revision control history
========================================================================

I need a new maintainer!
------------------------

Darcsver needs a new maintainer. The original author, Zooko Wilcox-O'Hearn,
is not planning to make further changes to it unless there is some unexpected
need to do so.

What Does It Do
---------------

Create files containing version numbers, based upon the latest darcs
release tag.

If your source tree is coming from darcs (i.e. it is in a darcs
repository), this tool will determine the most recent release tag,
count the patches that have been applied since then, and compute a
version number to be written into _version.py (and optionally other
version files). This version number will be available by doing:

 from your_package_name import __version__

Source trees that do not come from darcs (e.g. release tarballs, nightly
tarballs) and are not within a darcs repository should instead, come with a
_version.py that was generated before the tarball was produced. In this case,
this tool will quietly exit without modifying the existing _version.py .

'release tags' are tags in the source repository that match the following
regexp:

 ^your_package_name-(\d+)(\.(\d+)(\.(\d+))?)?((a|b|c|rc)(\d+))?


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

With easy_install:

  easy_install darcsver

Alternative manual installation:

  tar -zxvf darcsver-X.Y.Z.tar.gz
  cd darcsver-X.Y.Z
  python setup.py install

Where X.Y.Z is a version number.

Alternative to make a specific package use darcsver without installing
darcsver into the system:

  Put "setup_requires=['darcsver']" in the call to setup() in the
  package's setup.py file.


Usage
-----

There are two ways to use this: the command-line tool and the
setuptools plugin.

To use the command-line tool, execute it as:

darcsver $PACKAGE_NAME $PATH_TO_VERSION_PY


To use the setuptools plugin (which enables you to write "./setup.py
darcsver" and which cleverly figures out where the _version.py file
ought to go), you must first package your python module with
`setup.py` and use setuptools.

The former is well documented in the distutils manual:

  http://docs.python.org/dist/dist.html

To use setuptools instead of distutils, just edit `setup.py` and
change

  from distutils.core import setup

to

  from setuptools import setup


References
----------

How to distribute Python modules with Distutils:

  http://docs.python.org/dist/dist.html


Setuptools complete manual:

  http://peak.telecommunity.com/DevCenter/setuptools


Thanks to Yannick Gingras for providing the prototype for this
README.rst.
clinical_trials 1.1
Python wrapper for the Clincal Trials API.
License: BSD
Keywords: clinical trials,clinicaltrials,clinical_trials

Clincal Trials Python API
=========================

A Python API wrapper for the
[ClincalTrials.gov API](http://clinicaltrials.gov/ct2/info/linking).

Documentation for [ClinicalTrials.gov can be found
here.](http://clinicaltrials.gov/ct2/info/linking)


Usage
-----

The `Trials` class only has two methods -- `search` and `download`. The
same information from `search` is returned to the `download` method in
ZIP file format.

    >>> from clinical_trials import Trials
    >>> t = Trials()
    >>> t.search("alzheimer's disease")

    >>> t.search('diabetes', 'cond')
    >>> t.search('diabetes', 'condition')
    >>> t.search(condition='diabetes')

    >>> # Specify the number of trials turned.
    ... t.search(intervention='Fluoxetine', count=200)

    >>> # Find trials no longer recruiting.
    ... t.search('lyme disease', recruiting='closed')

    >>> # If you want plain XML returned back.
    ... t.search(sponsor='NHLBI', output_format=None)

    >>> # You can also find trials by location -- up to 3 states or countries.
    ... t.search('cancer', state='TX')

    >>> t.search('diabetes', state1='TX', state2='NY', state3='CA')
    >>> t.search(condition='lyme disease', country1='US', country2='CA')

    >>> # And you can download a ZIP file with the data.
    ... zip_file = t.download('cancer', count=500)


Copyright
---------

Copyright (c) 2011 Code for America Laboratories.

See LICENSE for details.