Guenter Milde
Mon, 21 Sep 2009 03:01:41 -0700
On 2009-09-19, Alex Fernandez wrote: > ... it looks for > eLyXer installed as a Python module (called "elyxer", not > "elyxerconv"); if not found it searches for the usual elyxer.py, > elyxer executables. Hopefully this solves all reasonable issues and > concerns of LyX developers and integrators. ... > I wanted to get early feedback.
To sum up the feedback: The approach (testing for a python module) is fine. Putting the detection routine into a checkModule() function would be even better: * provide a re-usable means of module detection, * hide the "ugly" try-except clause from "production code". (even if it will be used just one time (for now)) Could you modify you patch by "outsourcing" the module detection to a function? > Now that business is out of the way, let's have fun with some Q&A! Is it really fun to behave like a divorced couple or stubborn child? Why bring up this again after we all calmed down and tried to keep constructive? It will not help anyone and neither LyX, nor elyxer nor elyxer users if you call a LyX core developer a troll. Günter