Skip to main content
This is a pre-production deployment of Warehouse. Changes made here affect the production instance of PyPI (
Help us improve Python packaging - Donate today!

A python package for working with the BriteCore ETL.

Project Description

A python package for working with the BriteCore ETL.

PLEASE NOTE: brite_etl follows Semantic Versioning, and is currently in the initial development phase (0.x.x). Use with caution.


This is all broken down on the introduction page.

import brite_etl
from import CsvSource

# Create a "set" of frames to work with...
contoso = brite_etl.lib.FrameSet('contoso')

#Set the source of our csvs (can also pass BriteDataFrame/PreparedDataFrame)...
contoso.set_data_sources(source=CsvSource(DF_ROOT), prepared_source=CsvSource(DF_PREP))

# Easy handling of dataframes, works same for both csv and britedataframe sources.
# Essentially a wrapper around the pandas DataFrame. Dates parsed automatically.
contoso.frames.get('agencies').df # original dataframe

# Import BriteCore reports. Don't have to open/change/save columns in excel, hyperlinks and other
# formatting issues are handled. Don't even have to rename the file to take out the dates.
from import import_report
adv_prem = import_report('/tmp/input', 'Advance Premium', sheet='Advance Premium List', skip_rows=2) # Pandas DataFrame
contoso.frames.set('ap', df=adv_prem) # Make custom frames in your frame set

# Define frame-specific operations...

# Or use universal operations, chain across multiple frames...
_contoso = contoso.chain
    .filter_dates('date filter for multiple frames actually isn\'t done yet (soon, though)')
    .hash_cols(['policyId']) # MD5 hashed dataframes
    ) # Every frame is put into it's own sheet during export

# Computations make use of multiple frames within a frame set (also chainable)...
trans = _contoso.get_item_transactions().value()

# Create multiple, isolated sets of frames...
wrk = brite_etl.lib.FrameSet('working', from_set=contoso)


pip install brite_etl


To run the all tests run:


Test just your desired python version with tox -e py27 or tox -e py35. Much faster than running all test envirornments.

Note about testing: some of the tests require real df_cache data to run. The locations for the df_cache directories is defined in the setup.cfg file. When running, the tests will check to make sure the directories exist and contain files. If they don’t those tests will be skipped, the rest of the tests should function like normal.


0.1.0 (2016-10-03)

  • Update docs
  • Femove pypy env
  • Use semantic versioning

0.0.1 (2016-10-02)

  • First release on PyPI.
Release History

Release History

This version
History Node


History Node


Download Files

Download Files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

File Name & Checksum SHA256 Checksum Help Version File Type Upload Date
brite_etl-0.1.1-py2.py3-none-any.whl (53.9 kB) Copy SHA256 Checksum SHA256 py2.py3 Wheel Oct 3, 2016
brite_etl-0.1.1.tar.gz (40.9 kB) Copy SHA256 Checksum SHA256 Source Oct 3, 2016

Supported By

WebFaction WebFaction Technical Writing Elastic Elastic Search Pingdom Pingdom Monitoring Dyn Dyn DNS Sentry Sentry Error Logging CloudAMQP CloudAMQP RabbitMQ Heroku Heroku PaaS Kabu Creative Kabu Creative UX & Design Fastly Fastly CDN DigiCert DigiCert EV Certificate Rackspace Rackspace Cloud Servers DreamHost DreamHost Log Hosting