> We could do it like this: > > - pysnmp2 is patched to install to pysnmp/v2 > - pysnmp3 is patched to install to pysnmp/v3 > - pysnmp4 already installs to pysnmp/v4 > - the version switch-module from v4 is packaged as pysnmp-common and the > other version depend on it > - Programs need to specify what the need via os.envrion
Sounds good to me. In terms of the lesser of evils. > Perhaps it would be possible to use something like "import pysnmp.v2 as > pysnmp"? Perhaps it depends of how version-switch module works. Even if possible, I'd not suggest this way of version switching (e.g. an API) as it may create another dependency in the future. The os.environ-based method looks functionally the same but it can also be used without source code modifications (e.g. from startup script). -ilya -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
