Nits

Rebase

Rebase

Rootdir

Lint

Rebase

blk

black

up

Fix batching

Update migration scripts

Add comments on test

undebug

Rebase

blk

rmtodo

Rebase

Rebase

Up

hooray, but how is this configurable? don't we also need to change the gcs_system_storage?

Rebase

Rebase

i defer to your judgment @nate

fml

Nits

Nits

Tests

Reorg

Add test data

Rebase

Rebase

requesting changes because i think we should drop the diagram

i think i've said my piece on this being useful in the edge case / for introspection -- let's not foreground use of this resource in ordinary examples / usage patterns, we want people to be able to slice config space independently of writing solid logic

this seems a straightforward usability win. we should update the docstrings to be accurate (thus requesting changes). take a look at the docs for Field which are accurate (for the status quo ante). also, do we need to make tutorial changes?

cf https://great-expectations.readthedocs.io/en/latest/module_docs/dataset_module.html#great_expectations.dataset.pandas_dataset.PandasDataset

coveragerc

Rebase

py35

Up

Up

Fix tests

debug

undebug

Debug

py23

Skip tests on buildkite

Skip CLI tests on buildkite

Rebase

Rebase

Changelog

Arggh

Nits

blk

Nits

Nits

Drop clever checks

Add ping tasks

Fix

Test fixes

Up

Up

Undebug

Try Buildkite networking

Up

Undebug

debug5

Celery test setup 4

Debug test setup 3

Debug test setup2

love love lurve <3

debug test setup

Up

Up

Up

CLI

ok

thrilling!!

it is also possible that serialization strategy is the wrong place to deal with this (compare https://github.com/dagster-io/dagster/blob/master/examples/dagster_examples/airline_demo/unzip_file_handle.py)

i also think that changing the callsites will make this look like less of a win. I also don't like a world where we have a parameter called writable that is a string, i.e., specifically not something you can write to using the file APIs.