from postgres.orm import Model fails: ImportError: No module named orm

[bruceadams]

I do not understand our dependency handling.

Changing requirements.txt to pick postgres-2.1.0 just failed to find that package in /vendor/. Grabbing postgres-2.1.1 from the cheese shop, dropping that into /vendor/ and updating requirements.txt allows me to run.

How is this thing running with broken dependencies?

$ make run
    ...
pid-12052 thread-46912496319040 (MainThread)   File "/home/ba/Downloads/git/www.gittip.com/gittip/models/community.py", line 4, in <module>
pid-12052 thread-46912496319040 (MainThread)     from postgres.orm import Model
pid-12052 thread-46912496319040 (MainThread) ImportError: No module named orm

[zbynekwinkler]

All required packages are predownloaded into vendor. When you change requirements.txt you need to predownload the new package.

[bruceadams]

I started with a clean checkout of master. Its requirements.txt matched its vendor with postgres-2.0.0. And that's what gave me the "ImportError: No module named orm" error. As far as I can tell, this means the master branch is inconsistent with itself, trying to use something newer than its dependency setups call for. How is this running for other people? How is this running in production?

[zbynekwinkler]

Hmm. Looking at https://github.com/gittip/postgres.py/tree/2.0.0 I see orm.py in postgres. Travis and heroku both do clean checkouts for each commit/release. I have no idea why it has not worked for you.

Was there postgres-2.0.0.tar.gz in vendor in your checkout? Did pip fail to install it properly? Do you get any error message when you do `make clean; make env'?

[bruceadams]

OK. Going back to a clean checkout and doing a "make clean" got it to work.

So our dependency mechanisms don't notice out of date dependencies? Wow. That's awfully primitive.

[zbynekwinkler]

Well, it does work in #1548 :-P

[chadwhitacre]

So our dependency mechanisms don't notice out of date dependencies? Wow. That's awfully primitive.

Ticket! Infrastructure! :-)