On Jun 26, 2010, at 10:45 PM, Matthias Klose wrote:
>Having non-conflicting extension names is a schema which already is used on
>some platforms (debug builds on Windows). The question for me is, if just a
>renaming of the .so files is acceptable for upstream, or if distributors
>should implement this on their own, as something like:
>
> if ext_path.startswith('/usr/') and not ext_path.startswith('/usr/local/'):
> load_ext('foo.2.6.so')
> else:
> load_ext('foo.so')
>
>I fear this will cause issues when e.g. virtualenv environments start copying
>parts from the system installation instead of symlinking it.
I concur. I think my patch will have much less impact on virtualenv and
similar tools because there's nothing much magical about it. It just says "oh
there's another file suffix you should consider when looking for a shared
library", which as you point out is already done on Windows.
-Barry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/python-dev/attachments/20100630/1f2ea9ed/attachment.pgp>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4