[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] [PATCH] Make non-native python path handling a fallback


  • To: "Jeremy Katz" <katzj@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
  • Date: Fri, 15 Apr 2005 21:58:52 +0100
  • Delivery-date: Fri, 15 Apr 2005 20:58:45 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcVB+vxej/x/Bo3RS6aCCU0cCYSiDwAAOZNA
  • Thread-topic: [Xen-devel] [PATCH] Make non-native python path handling a fallback

 
> Although I don't really agree with the installing of the 
> python bits to the non-native paths, I can see where it's 
> useful as long as the module ABI doesn't change if you're 
> trying to distribute binary tarballs.  But with the current 
> handling it adds module lookup costs for the native path case 
> (which would be the norm) as well as prevents using 
> PYTHONPATH to look to a different location for the modules.
> 
> The attached patch changes things so that at first, the xen 
> module is attempted to be imported from the stock paths.  If 
> we get an ImportError exception, then it adds /usr/lib/python 
> to the end of the python path and imports again.

Do you prefer this to just unconditionally addding /usr/lib/python to
the end of the path rather than the front?

Ian 

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.