RE: Need Help! qpid-cofig: No module named qpid.messaging! Working!

["Flores, Paul A." <PA...@SAIC.COM>]

Setting PYTHONPATH prior to install really does help!

Thanks for your help. 

Paul

________________________________________
From: Justin Ross [justin.ross@gmail.com]
Sent: Monday, February 22, 2016 11:05 AM
To: proton@qpid.apache.org
Subject: Re: Need Help! qpid-cofig: No module named qpid.messaging

This is controlled via the standard python search paths.  IOW, set
PYTHONPATH to the location of the libraries you want to see used.

On Mon, Feb 22, 2016 at 8:39 AM, Flores, Paul A. <PA...@saic.com>
wrote:

> I have found one culprit that is contributing to this issue.
>
> My development environment is a VirtualBox Centos 5.11 environment
> (clients choice) that has Python2.4 installed as the primary Python version
> . I am using an alternative install of Python 2.6.8.
>
> The install of the Python has seemed to place critical elements into
> Python 2.4 related folders not in my PATH.
>
> Is it possible to setup the QPID Python version so that it points at an
> alternative Python install?
>
> ________________________________________
> From: Jakub Scholz [jakub@scholz.cz]
> Sent: Monday, February 22, 2016 10:22 AM
> To: proton@qpid.apache.org
> Subject: Re: Need Help! qpid-cofig: No module named qpid.messaging
>
> I think you need to download and install the Python version of the Qpid
> Messaging API. You can download it for example here
> http://qpid.apache.org/components/messaging-api/index.html or on
> http://qpid.apache.org/download.html. If you don't want to install it into
> the system directories, it should be enough if you copy the mllib and qpid
> directories next to your qpid-config.
>
> On Mon, Feb 22, 2016 at 4:40 PM, Flores, Paul A. <PA...@saic.com>
> wrote:
>
> > Help!
> >
> >
> >
> > All the I can find when I Google on this messaging I am getting is dated
> > 2010.  It references a QMF extras folder that does not exist.
> >
> >
> >
> > Surely there has to be some updated guidance to this issue?
> >
> >
> >
> > This is "blocking" my current sprint progress!
> >
>