Rafi, If you are spinning another RC please include [1] ? It's done to ensure we close tcp connections. Please see [2] for details.
[1] http://svn.apache.org/viewvc?rev=1425124&view=rev [2] https://reviews.apache.org/r/7934/diff/3/?file=236677#file236677line108 Rajith On Fri, Dec 21, 2012 at 2:28 PM, Ken Giusti <[email protected]> wrote: > I hit a python problem on Centos-5 - which uses python 2.4: > > > [kgiusti@localhost tests]$ ./proton-test > Traceback (most recent call last): > File "./proton-test", line 553, in ? > m = __import__(name, None, None, ["dummy"]) > File > "/home/kgiusti/work/proton/RC3/qpid-proton-c-0.3/tests/proton_tests/__init__.py", > line 20, in ? > import proton_tests.codec > File > "/home/kgiusti/work/proton/RC3/qpid-proton-c-0.3/tests/proton_tests/codec.py", > line 21, in ? > from proton import * > File > "/home/kgiusti/work/proton/RC3/install/usr/local/lib/python2.4/site-packages/proton.py", > line 857, in ? > class Data: > File > "/home/kgiusti/work/proton/RC3/install/usr/local/lib/python2.4/site-packages/proton.py", > line 1615, in Data > put_mappings = { > NameError: name 'bytes' is not defined > > The bytes type was added in 2.6 > > -K > > ----- Original Message ----- >> On Fri, Dec 21, 2012 at 9:32 AM, Ken Giusti <[email protected]> >> wrote: >> >> > Ok, thanks Darryl - I'll give it a try. >> > >> > In any case, the README file in the release candidate needs to be >> > updated >> > - I imagine most folks just starting out with proton want to be >> > able to >> > evaluate it without needing root privs. >> > >> >> I'll update the README for RC2. >> >> FWIW, I think there are two pretty distinct scenarios for make >> install as >> non root. The one proton developers keep running into is doing a non >> root >> make install as a way to test what would have gotten installed had a >> normal >> make install been done. For this purpose 'make install >> DESTDIR=test-root' >> is a much more accurate and robust way to do this because it gives >> you >> sub-tree with *exactly* what would have been installed based on the >> particular cmake configuration. Doing a cmake >> -DCMAKE_INSTALL_PREFIX=$HOME/blah is actually testing how a non-root >> configuration would get installed which isn't necessarily the same at >> all. >> >> The second scenario is as Ken points out when a user that wants to >> evaluate >> proton without doing a full system install. Right now we don't really >> cater >> to this case as an install scenario per/se, however it is quite easy >> to do >> from an svn checkout via the config.sh that is in the proton root. >> Going >> forward (e.g. for 0.4) we could probably have make install set up >> something >> similar for non root installs if we want to cater to that scenario >> more >> directly. >> >> --Rafael >>
