Refactor to use a Cells-like forward/backward propagation system. Separated thread-specific "current observer" state from trellis state. Tests still pass, but are far from sufficient and the docs are crap; you're better off not reading them yet. Effectively this is just a checkpoint to have a jumping-off point for more extensive changes, like making values know what trellis they belong to, and redoing the docs/tests to maximize both line and scenario coverages.
#!/usr/bin/env python """Distutils setup file""" #import ez_setup #ez_setup.use_setuptools() from setuptools import setup # Metadata PACKAGE_NAME = "Trellis" PACKAGE_VERSION = "0.0.1" PACKAGES = ['peak', 'peak.events'] def get_description(): # Get our long description from the documentation f = file('README.txt') lines = [] for line in f: if not line.strip(): break # skip to first blank line for line in f: if line.startswith('.. contents::'): break # read to table of contents lines.append(line) f.close() return ''.join(lines) setup( name=PACKAGE_NAME, version=PACKAGE_VERSION, url = "http://peak.telecommunity.com/DevCenter/Trellis", description='A simple "untwisted" approach to event-driven programming', long_description = get_description(), author="Phillip J. Eby", author_email="peak@eby-sarna.com", license="PSF or ZPL", test_suite = 'test_trellis', packages = PACKAGES, namespace_packages = PACKAGES, )
cvs-admin@eby-sarna.com Powered by ViewCVS 1.0-dev |
ViewCVS and CVS Help |