setup.py: third_party should install under libnamebench to avoid conflicts
GoogleCodeExporter opened this issue · comments
Right now third_party gets installed in the python library path. It is possible
that other utilities
(most likely Google ones) may use this same path and conflict with these
libraries. setup.py should
be altered so that third_party is installed under libnamebench.
Original issue reported on code.google.com by helixblue on 16 Nov 2009 at 9:52
Original comment by tstromb...@google.com on 8 Dec 2009 at 7:42
- Added labels: Priority-Low
This issue was closed by revision r900.
Original comment by thomas.r...@gmail.com on 29 May 2010 at 5:10
- Changed state: Fixed
Fixed in revision 900. Installs under nb_third_party
Original comment by helixblue on 29 May 2010 at 5:10