"Maciej (Matchek) Bliziński" <[email protected]> writes: > 2013/8/1 Peter FELECAN <[email protected]>: >> "Maciej (Matchek) Bliziński" <[email protected]> writes: >> >>> CSWpython - install or not install as you wish >>> CSWpython27 - install or not install as you wish >>> CSWpy-foo - when you install it, it will work fine with CSWpython (if >>> installed) and / or CSWpython27 (if installed). If you install both, >>> it will work with both. >>> >>> That's all. Everything works as expected. I don't see what's wrong >>> with this setup. >> >> One thing that I think of: by default, 2.6 is /opt/csw/bin/python. If >> a module doesn't use a shebang or other wizardry it will fail because it >> needs 2.7 but gets 2.6 > > Modules generally do not and should not have hashbang lines. Only > executables do. By the time you're loading a module, you've already > started the interpreter, so the hashbang line doesn't have any > feasible way of influencing the course of action. > > If there's a module which needs the 2.7 interpreter, it will not > provide any files in the /opt/csw/lib/python/site-packages or > /opt/csw/lib/python2.6/site-packages directories.
Agreed. BTW, have you seen my proposal in http://lists.opencsw.org/pipermail/maintainers/2013-August/018346.html ? -- Peter _______________________________________________ maintainers mailing list [email protected] https://lists.opencsw.org/mailman/listinfo/maintainers .:: This mailing list's archive is public. ::.
