ojas

#!/usr/bin/env python

import sys
import json

CHUNK_SIZE = 500

def chunks(l, n):
    """ Yield successive n-sized chunks from array l
    """

ojas

suds==0.4
wsgiref==0.1.2

ojas

#!/usr/bin/python

"""
Usage:
    python bir.py <duns_number>
"""

import sys
import requests
import traceback

ojas

class MyClass():
    def __init__(self, *args, **kwargs):
        print '>> init'
        self.label = kwargs.get('label')

    def __enter__(self):
        print '  >> enter'
        return self

    def __exit__(self, type, value, traceback):

ojas

csvsql --db sqlite+pysqlite:///test.db -e iso-8859-1 --insert ./test-file-209.csv 

ojas

<sharmaskarma> how can we build before we know the requirement
<sharmaskarma> KNOW THE REQUIREMENT
<ojas> how can you really know the requirement? it's like reverse zeno's
paradox.... you know you must end up at a requirement (at t1), but when you
start (t0) you have no requirement. there must be some point between t0 and t1
where half of the requirement is known, and between t0 and that point where one
half of one half of the requirement is known, and so on...
<ojas> but not matter how far you go back, you can never start w/ zero
requirement. hence, it's impossible to even get a single requirment defined.
QED

ojas

test