Greetings, Boy, do I feel silly. I've had to deal with CR-LF versus LF line- endings in text files for more years than I care to think about. But I've also been using 'vi' (later 'vim' ) before PCs were made famous by Bill Gates. However, somebody has 'improved' vi/vim now such that when I edited jallib.py and typed '1l' it didn't display the ^M like it should have (IMHO), and like it always has for years-- until recently?
Thankfully, no one has 'improved' the trusty 'od -c jallib.py' command, so I was able to see what you all suspected, and a quick 'dos2unix jallib.py' took care of the issue. Thanks for listening, and sorry to have wasted your time. William On Oct 6, 5:14 pm, Wayne Topa <[email protected]> wrote: > Sebastien Lelong wrote: > > Hi, > > > I don't think this is related to python version... Shebang won't work > > because of a extra "\r": > > > #!/usr/bin/python\r\n > > > give as interpreter "/usr/bin/python\r". Whatever the version used, you > > won't get a path to an executable program. > > > Specify "python jallib.py" bypasses shebang, it's not processed anymore. > > Using your jallib script or the export JALLIB_PYTHON=python2.5 without > the wrapper works here. I prefer the wrapper :-) > > BTW you have a typo in the jallib.py script > jallib -help jalapt > > Look for HMLT > > I had never looked or used jallib.py. You are quite the python > programmer. Just one of the many languages you do very well. I am > impressed! > > Thanks again > > Wayne > > -- Give a man a fish - feed him for a day > Teach a man to fish - feed him for life --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jallib?hl=en -~----------~----~----~----~------~----~------~--~---
