On Sun, Apr 21, 2013 at 12:24:40AM +0530, Rohit Yadav wrote: > On Sat, Apr 20, 2013 at 11:13 PM, David Nalley <da...@gnsa.us> wrote: > > > On Thu, Apr 18, 2013 at 6:45 PM, Ron Young <r...@nscee.edu> wrote: > > > Your message dated: Thu, 18 Apr 2013 16:30:56 -0600 > > > -------- > > > > > > Hi: > > > > > > I ran across this same problem this morning... > > > > > > I stumbled on the solution: pip install requests > > > > > > -ron > > > > > > Sounds like a bug (lack of proper dependencies). Can one of you file this? > > > > I think Prasanna already followed this one? Prasanna? One way to solve this > is to put the deps in setup.py and publish snapshots (perhaps daily) on a > pypi channel, this way a user/developer upgrades/installs which gets 'em > any new deps.
That's right. It is fixed in marvin and the dependency has been added. Even if you publish the snapshots there's that extra step of manually updating marvin with a $pip install --upgrade. Alternatively, if and when marvin does change you can simply run the marvin.sync target in mvn as explained [1] and it will update marvin on your system with the latest dependencies [1] http://s.apache.org/5Iv (cf. Sync latest APIs) -- Prasanna., ------------------------ Powered by BigRock.com
