root: INFO: Ferris 3: endpoints library not available.

9 views
Skip to first unread message

Dewey Gaedcke

unread,
Apr 9, 2016, 11:55:42 PM4/9/16
to Ferris Framework
So my F3 endpoints project has been working pretty well but my testing has been very manual....I'd like to fix that:

I ran:   pip install ferrisnose

I'm on a Mac & used Homebrew to install my Python ;  Homebrew pip has a bug which means I can't tell pip to put the dependency into the app/lib/ directory inside my project

So I have to drag each dependency into app/lib/ and I'm a bit concerned over having packages in both places....
Has anyone tried this approach ----  he puts symlinks (to his venv packages) in his /lib directory so he can retain the benefits of pip & requirements.txt
And if you've tried it, or read that post, do you have any feedback on the benefits or dangers going that route??

Back to my issue ---  my endpoints api works fine when I'm running the dev-server

But when I run:

nosetests  common/tests2

I'm getting this output:

from ferris3 import auto_service, auto_method, Service, hvild, caching

ImportError: cannot import name auto_service

-------------------- >> begin captured logging << --------------------

root: DEBUG: Using threading.local

root: INFO: Ferris 3: endpoints library not available.

--------------------- >> end captured logging << ---------------------


I'm guessing 1 of 3 causes:

  • my vendored "lib" dir is not getting added to the path   (how do I get nosetest to do that??)
  • ferris3 is picking up the endpoints module from the app-engine SDK instead of it's own endpoints  
  • something else wrong with my path


All feedback appreciated!

Thx
D


Jonathan Parrott

unread,
Apr 23, 2016, 4:08:37 AM4/23/16
to Dewey Gaedcke, Ferris Framework
1. the ext.vendor library can be pointed at a virtualenv. No symlinks required.
2. Just installing ferrisnose isn't enough, you have to actually tell nose to use it with nosetests --with-ferris
Reply all
Reply to author
Forward
0 new messages