On 27 November 2012 15:12, kcrisman <kcris...@gmail.com> wrote: > How hard would it be to "import contrib.foo as modular.foo" > without causing problems? Because of course one wouldn't want one's > research stuff to have to live in a different namespace if it was for Sage > proper stuff.
This reminds me of a situation that existed between National Instruments and Sun. I have a National Instruments GPIB board, which worked fine in Solaris 9. When I upgraded to Solaris 10, it would not work. Eventually the problem was found by a Sun employee. National Instruments had for many years had a Solaris driver for the GPIB board, which they called "ib". Years later, Sun introduced Infiniband support in Solaris 10, and so added a driver for Infiniband . No prizes for guessing what Sun called the driver - yes "ib". Needless to say, the National Instruments card would not work in Solaris 10. A solution which worked for me was to remove the Infiniband support from Solaris as I had no use for it. Then the National Instruments driver "ib" would work properly. Ideally, one would want a solution which stopped this sort of thing happening in Sage, but with user contributed code, it might be quite difficult to prevent. Dave -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en.
