site-packages versus site-python

[Steve Holden]

msoulier wrote:
>>Well, broadly, the reason is that it allows version-specific code to
> 
> be
> 
>>included in libraries.
> 
> 
> I've actually found this to be a bit of a pain. I build packages
> against say, python2.2, and if you upgrade python to 2.3 the package
> breaks. The code works fine so saying it requires python >= 2.2 should
> be valid, but the version-specific path prevents that. 
> 
> Mike
> 
Well, if you can invent a reliable mechanism for managing 
version-independent extensions I'm sure the developers will be happy to 
hear about it :-)

regards
  Steve
-- 
Meet the Python developers and your c.l.py favorites March 23-25
Come to PyCon DC 2005                      http://www.pycon.org/
Steve Holden                           http://www.holdenweb.com/