On Mon, 2006-04-24 at 14:06 +0200, Morten Werner Olsen wrote: > On Mon, Apr 24, 2006 at 02:00:20PM +0200, Jan Lübbe wrote: > > > 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 > > > > Perhaps it would be possible to use something like "import pysnmp.v2 as > > pysnmp"? > > That would mean that software packaged for Debian which uses pysnmp > will have to be patched to be able to use pysnmp, and do we really > want that?
Its now good, but i dont see any other good way :/ The default (if you don't change os.environ) would be the most recent installed version. But if we don't have a way to select one of the installed version, it would be impossible to install programs that depend on different versions. That would be a severe restriction. What do you think about using the module names pysnmp for pysnmp4 and pysnmp[23] for the older versions? -- Jan Lübbe <[EMAIL PROTECTED]> http://sicherheitsschwankung.de gpg-key 1024D/D8480F2E 2002-03-20 fingerprint 1B25 F91F 9E7B 5D4F 1282 02D6 8A83 8BE4 D848 0F2E
