#pyramid

ccarrara: are your models imported?

ccarrara: if they are not imported then they won't be attached to the metadata and thus migrations will not see them

there is a comment about this in the alchemy cookiecutter's output in the model/__init__.py file

as far as the flask-migrate trolling earlier, that library just uses alembic so I don't know what the point of bringing that up was

raydeo: hmm, it makes sense. I just created the models in a models.py module and didn't use them anywhere.

ccarrara: you can add a breakpoint to your env script and inspect the metadata

if db.metadata.tables doesn't show your tables then that's a good clue

I'm kinda used with django style of things. Sorry be raising those simple questions here.

raydeo, it was EXACTLY that. :) Thank you so much.

great!

And here I thought flask-migrate existed to migrate from flask to something more sane :P

x58: do you have an opinion on the commit_veto stuff?

I approved the PR

I haven't ever used the commit veto stuff though.

sure but there was a whole separate paragraph in there ;-)

So I am not the best person to comment on it's use cases.

There was?

Wait, what did I miss?

I can look at it tonight, I really need to get what I am working on done for work.

no worries... I'm just trying to decide if the bw-incompat change is enough for 3.x or if I should also go one step further with the incompat

I will put the change in a separate pr

meh nevermind, just going to ship it as is

[pyramid_tm] mmerickel pushed 2 new commits to master: https://git.io/vQuPb

pyramid_tm/master d0702d6 Michael Merickel: allow the commit_veto to handle squashed exceptions

pyramid_tm/master 83c169d Michael Merickel: Merge pull request #65 from mmerickel/commit-veto-overrides-squashed-exception...

Pylons/pyramid_tm#174 (master - 83c169d : Michael Merickel): The build passed.

Change view : https://github.com/Pylons/pyramid_tm/compare/a7...

Build details : https://travis-ci.org/Pylons/pyramid_tm/builds/...