On 26-Jun-2002 Florent Rougon wrote: > "Sean 'Shaleh' Perry" <[EMAIL PROTECTED]> wrote: > >> The problem is we now have a piece of a fairly common package using >> script(s) in a language few understand. So if you get hit by a bus >> someone WILL have to reverse engineer that script. This is the same > > Well, I guess you mean "py2texi.el's upstream maintainer" instead of > "you". Has someone had problems contacting him? Does his script often > break? The home page, <http://www.zamazal.org/software/python/py2texi/>, > is mentioned at the beginning of py2texi.el. >
hmm, sorry, was going on other people's comments here. I was not aware you inherited this from the upstream. Please allow me to eat my foot (-: > > These are the implementation quirks. Now: > - is it the only .el file used in the whole Python build? > - are you sure the locally-and-not-installed python binary would be > able to use modules like re, StringIO, etc.? > - does someone actually use these info files, which are not supported > by upstream and may be incorrect: > > "The result code is ugly and need not contain complete information > from Python manuals. I apologize for my ignorance, especially > ignorance to python.sty" > > due to the difficult nature of such a conversion? I use the python info docs nearly every time I code in python and would miss them a lot. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
