Scott Sanderson

> but I haven't though of a way that ends up being better than what already works right now: a one-line default generator that reads a given env. What about...

@minrk, speaking as someone who's done a fair amount of work building things on top of the Contents API, I think building sharing on top of / as an extension...

For the record, I'm not seeing a meaningful startup time improvement with this, but I'm also not seeing much time being spent in this code to begin with: ``` (IPython)...

hey @jcrist! My first instinct is that I'm not super excited about splitting this up into multiple repositories. This repo is generally pretty stable, and as you can see from...

> My one concern would be that having multiple packages per repo can make it a bit confusing where to file bugs (harder to google search), I buy this concern,...

Hi @nsshah1288, The tables used by pgcontents are created by the `pgcontents init` command noted in the README's installation steps. That command uses [`alembic`](https://alembic.sqlalchemy.org/en/latest/) to run a migration that should...

hey @nsshah1288 . You only need to run `pgcontents init` once. It will create all the tables that will be used. It's usually done manually from the command line. For...

> I was under the assumption that the select and insert/update would happen in a single transaction, because of the db.begin_nested() in the with statement. This is true. These will...

> On the upsert: very interesting. My initial attempt at using the on_conflict_do_update fails with Insert does not have an attribute on_conflict_do_update. This is the code fragment: I think the...

@jorisgillis these changes look good to me! Unfortunately, it appears that I no longer have permission to merge PRs to this repo. Quantopian, the company for whom I originally wrote...